[
https://issues.apache.org/jira/browse/FLINK-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895833#comment-16895833
]
Jingsong Lee commented on FLINK-13490:
--------------------------------------
Thanks [~TsReaper], maybe the bug is explained in comment of ResultSet.wasNull:
{code:java}
/**
* Reports whether
* the last column read had a value of SQL <code>NULL</code>.
* Note that you must first call one of the getter methods
* on a column to try to read its value and then call
* the method <code>wasNull</code> to see if the value read was
* SQL <code>NULL</code>.
*
* @return <code>true</code> if the last column value read was SQL
* <code>NULL</code> and <code>false</code> otherwise
* @exception SQLException if a database access error occurs or this method is
* called on a closed result set
*/
boolean wasNull() throws SQLException;
{code}
> Fix return null in JDBCUtils::getFieldFromResultSet
> ---------------------------------------------------
>
> Key: FLINK-13490
> URL: https://issues.apache.org/jira/browse/FLINK-13490
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / JDBC
> Reporter: Caizhi Weng
> Priority: Critical
> Fix For: 1.9.0, 1.10.0
>
>
> The null checking in `JDBCUtils::getFieldFromResultSet` is incorrect. Under
> the current implementation, if one column is null in the result set, the
> following calls to this method using the same result set will always return
> null, no matter what the content of the column is.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
