[ https://issues.apache.org/jira/browse/CALCITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191456#comment-15191456 ]
Julian Hyde commented on CALCITE-1147: -------------------------------------- [~maryannxue], I get other errors from Hbase (and the usual heaps of useless trace output) but no NPE. Should I be initializing HBase in some way or should it be sufficient to just run the test case method? > Exceptions caused by CALCITE-604 > -------------------------------- > > Key: CALCITE-1147 > URL: https://issues.apache.org/jira/browse/CALCITE-1147 > Project: Calcite > Issue Type: Bug > Reporter: Maryann Xue > Assignee: Julian Hyde > Fix For: 1.7.0 > > > The first exception I got while using PhoenixMetadataProvider was: > "java.lang.IllegalArgumentException: duplicate key" in > ChainedMetadataProvider.handlers(), which was caused by the use of > ImmutableMap.Builder. > According to > https://groups.google.com/forum/#!topic/sakai-kernel/Kj1WRBg9pi8, in such > scenarios, we should use HashMap instead. > After fixing the above issue, I got NPE at > ReflectiveRelMetadataProvider.java:278 {{if > (RelNode.class.isAssignableFrom(relClass.getSuperclass())) {}}, for which I > didn't know why it hadn't caused any trouble before. Since this logic wasn't > really changed in CALCITE-604, I assume it went through the wrong code path. > Looks like we should add more test cases for custom metadata in Calcite. -- This message was sent by Atlassian JIRA (v6.3.4#6332)