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

Chesnay Schepler commented on FLINK-3471:
-----------------------------------------

that is specifically for columns that are always NULL. that may not make a lot 
of sense in the real world, but back then i just went down the list of SQL 
types and created a reasonable mapping.

you can't throw a NullValue into a tuple field whose type is not NullValue. 
even assuming a compiler would let that through, it would fail the moment a 
serializer touches the tuple.

> JDBCInputFormat cannot handle null fields of certain types
> ----------------------------------------------------------
>
>                 Key: FLINK-3471
>                 URL: https://issues.apache.org/jira/browse/FLINK-3471
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: 0.10.2
>            Reporter: Ken Geis
>
> JDBCInputFormat.addValue(..) is not safe against NULL values for types 
> DECIMAL, NUMERIC, DATE, TIME, TIMESTAMP, and SQLXML. This makes it so that I 
> cannot input data using any queries that will result in NULL values for any 
> of these types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to