You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Parth Chandra (JIRA)" <ji...@apache.org> on 2015/04/08 01:47:14 UTC
[jira] [Updated] (DRILL-2472) JDBC : ResultSet.wasNull should give
proper error message when a user tries to call it before calling getXXX
method
[ https://issues.apache.org/jira/browse/DRILL-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parth Chandra updated DRILL-2472:
---------------------------------
Fix Version/s: (was: 0.9.0)
1.0.0
> JDBC : ResultSet.wasNull should give proper error message when a user tries to call it before calling getXXX method
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DRILL-2472
> URL: https://issues.apache.org/jira/browse/DRILL-2472
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - JDBC
> Reporter: Rahul Challapalli
> Assignee: Daniel Barclay (Drill)
> Priority: Minor
> Fix For: 1.0.0
>
>
> git.commit.id.abbrev=7b4c887
> Drill currently throws the below error when we call wasNull before calling getXXX method
> {code}
> Exception in thread "main" 17:15:07.935 [Client-1] DEBUG o.a.drill.exec.rpc.user.UserClient - Sending response with Sender 557575560
> java.lang.ArrayIndexOutOfBoundsException: 1
> at org.apache.drill.jdbc.DrillAccessorList.wasNull(DrillAccessorList.java:53)
> at org.apache.drill.jdbc.DrillCursor.wasNull(DrillCursor.java:138)
> at net.hydromatic.avatica.AvaticaResultSet.wasNull(AvaticaResultSet.java:201)
> {code}
> Drill should instead give the appropriate error message
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)