You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Rahul Challapalli (JIRA)" <ji...@apache.org> on 2015/03/16 01:21:38 UTC
[jira] [Created] (DRILL-2472) JDBC : ResultSet.wasNull should give
proper error message when a user tries to call it before calling getXXX
method
Rahul Challapalli created DRILL-2472:
----------------------------------------
Summary: 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
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)