You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jing Zhang (JIRA)" <ji...@apache.org> on 2019/07/31 06:16:00 UTC

[jira] [Commented] (FLINK-13503) Correct the behavior of `JDBCLookupFunction` when input data has null

    [ https://issues.apache.org/jira/browse/FLINK-13503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896807#comment-16896807 ] 

Jing Zhang commented on FLINK-13503:
------------------------------------

cc [~jark][~lzljs3620320]

> Correct the behavior of `JDBCLookupFunction` when input data has null 
> ----------------------------------------------------------------------
>
>                 Key: FLINK-13503
>                 URL: https://issues.apache.org/jira/browse/FLINK-13503
>             Project: Flink
>          Issue Type: Task
>          Components: Connectors / JDBC
>    Affects Versions: 1.9.0, 1.10
>            Reporter: Jing Zhang
>            Priority: Minor
>
> The query template in `JdbcLookUpFunction` like:
> SELECT c, d, e, f from T where a = ? and b = ?
> If pass (null, 1) to `eval` method, it will generate the following query:
> SELECT c, d, e, f from T where a = null and b = ?
> Which always outputs empty records.
> Is this behavior reasonable?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)