[
https://issues.apache.org/jira/browse/DRILL-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984752#comment-14984752
]
ASF GitHub Bot commented on DRILL-2288:
---------------------------------------
Github user jacques-n commented on a diff in the pull request:
https://github.com/apache/drill/pull/228#discussion_r43597587
--- Diff:
contrib/storage-hbase/src/main/java/org/apache/drill/exec/store/hbase/HBaseRecordReader.java
---
@@ -142,10 +148,12 @@ public void setup(OperatorContext context,
OutputMutator output) throws Executio
getOrCreateFamilyVector(column.getRootSegment().getPath(),
false);
}
}
- logger.debug("Opening scanner for HBase table '{}', Zookeeper quorum
'{}', port '{}', znode '{}'.",
- hbaseTableName, hbaseConf.get(HConstants.ZOOKEEPER_QUORUM),
- hbaseConf.get(HBASE_ZOOKEEPER_PORT),
hbaseConf.get(HConstants.ZOOKEEPER_ZNODE_PARENT));
- hTable = new HTable(hbaseConf, hbaseTableName);
+ // Add vector for any column families not mentioned yet (in order to
avoid
+ // creation of dummy NullableIntVectors for them).
+ for (HColumnDescriptor columnFamily :
--- End diff --
This also needs to be done for any requested column vectors.
> ScanBatch violates IterOutcome protocol for zero-row sources [was: missing
> JDBC metadata (schema) for 0-row results...]
> -----------------------------------------------------------------------------------------------------------------------
>
> 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.3.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)
