[
https://issues.apache.org/jira/browse/DRILL-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362600#comment-14362600
]
Rahul Challapalli commented on DRILL-2464:
------------------------------------------
I tried your example and found out that drill is actually replacing null values
with some random long value. This could be the root cause of the problem as to
why "wasNull" always returns false.
I can raise a different jira to track that issue
> JDBC : ResultSet.wasNull always returns false for all datatypes
> ---------------------------------------------------------------
>
> Key: DRILL-2464
> URL: https://issues.apache.org/jira/browse/DRILL-2464
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - JDBC
> Reporter: Rahul Challapalli
> Assignee: Daniel Barclay (Drill)
> Attachments: fewtypes_null.parquet
>
>
> git.commit.id.abbrev=7b4c887
> I attached a parquet file which has nulls in it.
> {code}
> while (rs.next()) {
> rs.getLong(1);
> if (rs.wasNull()) {
> // DRILL does not come here even when the column value is null
> }
> }
> {code}
> I am not entirely sure if this is a duplicate to DRILL-2136. But here I have
> seen this happen for all data types.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
