[
https://issues.apache.org/jira/browse/DRILL-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632614#comment-14632614
]
Daniel Barclay (Drill) commented on DRILL-2288:
-----------------------------------------------
Investigation notes:
- Is not a JDBC problem--is an INFORMATION_SCHEMA/ischema problem.
- Has something to do with ischema filtering--whether metadata is missing or
not depends on whether having zero rows was caused by mismatching one of the
specially filtered (pushed-down?) fields (e.g., TABLE_SCHEMA and TABLE_NAME for
COLUMNS) or not, respectively.
> result set metadata not set for zero-row result
> (DatabaseMetaData.getColumns(...))
> -----------------------------------------------------------------------------------
>
> Key: DRILL-2288
> URL: https://issues.apache.org/jira/browse/DRILL-2288
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Information Schema
> Reporter: Daniel Barclay (Drill)
> Assignee: Daniel Barclay (Drill)
> Fix For: 1.2.0
>
> Attachments: Drill2288NoResultSetMetadataWhenZeroRowsTest.java
>
>
> The ResultSetMetaData object from getMetadata() of a ResultSet is not set up
> (getColumnCount() returns zero, and trying to access any other metadata
> throws IndexOutOfBoundsException) for a result set with zero rows, at least
> for one from DatabaseMetaData.getColumns(...).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
