[
https://issues.apache.org/jira/browse/CALCITE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941736#comment-14941736
]
Julian Hyde commented on CALCITE-905:
-------------------------------------
I'm testing in
https://github.com/julianhyde/incubator-calcite/tree/905-get-tables; looks good
so far.
I've fixed the doc issue in the same patch (but won't re-generate the site for
now).
[getUDTs|http://docs.oracle.com/javase/8/docs/api/java/sql/DatabaseMetaData.html#getUDTs-java.lang.String-java.lang.String-java.lang.String-int:A-]
has the same issue as getTables. (It has a field 'int[] types')
If you would like me to hold so you can fix getUDTs and add a protobuf test,
let me know.
> getTables returns empty result in JdbcMeta
> ------------------------------------------
>
> Key: CALCITE-905
> URL: https://issues.apache.org/jira/browse/CALCITE-905
> Project: Calcite
> Issue Type: Bug
> Reporter: Jan Van Besien
> Assignee: Julian Hyde
> Attachments: CALCITE-905.patch, CALCITE-905.patch
>
>
> getTables on the metadata of a connection does not work (returns empty
> ResultSet) with avatica remoting using a JdbcMeta.
> {code}
> connection.getMetaData().getTables(null, null, null, null);
> {code}
> The problem seems to be related to the String[] types argument of the
> getTables method, this works as expected:
> {code}
> connection.getMetaData().getTables(null, null, null, new String[]{"TABLE"});
> {code}
> I think it boils down to the JdbcMeta#toArray(List<String> typeList) method
> which returns an empty array in stead of null, resulting in the creation of
> an incorrect typeFilter in CalciteMetaImpl#getTables (line 254).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
