[ https://issues.apache.org/jira/browse/CALCITE-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978170#comment-16978170 ]
Stamatis Zampetakis commented on CALCITE-3514: ---------------------------------------------- OK, I thought that the test was performing table equality but in the end it is the actual code related with materialization, thanks for the clarification. > LatticeTest fails when JdbcSchema re-computes JdbcTables > -------------------------------------------------------- > > Key: CALCITE-3514 > URL: https://issues.apache.org/jira/browse/CALCITE-3514 > Project: Calcite > Issue Type: Bug > Components: core > Affects Versions: 1.21.0 > Reporter: Feng Zhu > Assignee: Feng Zhu > Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > In our production environment, we find that when we disable the cache for > _JdbcTable_ in *_JdbcSchema_*, some tests (e.g., _testTwoLattices, > testTileAlgorithm2_) in LatticeTest will fail. > The problem can be reproduced by rewriting the _getTable_ method in > JdbcSchema, i.e., setting _force=true_. > {code:java} > public Table getTable(String name) { > return getTableMap(true).get(name); > }{code} > We need to implement JdbcTable's _equals()_ and _hashCode()_ methods. -- This message was sent by Atlassian Jira (v8.3.4#803005)