[
https://issues.apache.org/jira/browse/CALCITE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313937#comment-14313937
]
Vladimir Sitnikov commented on CALCITE-507:
-------------------------------------------
PR is updated:
Mongo -- FAIL (recent changes to traits broke it somehow)
MySQL -- pass
PostgresSQL -- pass
H2 -- pass
Here's how Mongo fails:
{noformat}
testSelectWhere(org.apache.calcite.test.MongoAdapterIT) Time elapsed: 1.322
sec <<< FAILURE!
java.lang.AssertionError: Internal error: Error while applying rule
MongoProjectRule, args
[rel#226:LogicalProject.NONE.[](input=rel#218:Subset#2.NONE.[],warehouse_id=$0,warehouse_state_province=$1)]
at org.apache.calcite.plan.volcano.RelSubset.<init>(RelSubset.java:108)
at
org.apache.calcite.plan.volcano.RelSet.getOrCreateSubset(RelSet.java:154)
at
org.apache.calcite.plan.volcano.VolcanoPlanner.changeTraits(VolcanoPlanner.java:694)
at org.apache.calcite.plan.RelOptRule.convert(RelOptRule.java:510)
at
org.apache.calcite.adapter.mongodb.MongoRules$MongoProjectRule.convert(MongoRules.java:263)
at
org.apache.calcite.rel.convert.ConverterRule.onMatch(ConverterRule.java:116)
at
org.apache.calcite.plan.volcano.VolcanoRuleCall.onMatch(VolcanoRuleCall.java:228)
at
org.apache.calcite.plan.volcano.VolcanoPlanner.findBestExp(VolcanoPlanner.java:795)
at org.apache.calcite.tools.Programs$5.run(Programs.java:272)
at
org.apache.calcite.tools.Programs$SequenceProgram.run(Programs.java:320)
at org.apache.calcite.prepare.Prepare.optimize(Prepare.java:142)
at org.apache.calcite.prepare.Prepare.prepareSql(Prepare.java:274)
at org.apache.calcite.prepare.Prepare.prepareSql(Prepare.java:188)
at
org.apache.calcite.prepare.CalcitePrepareImpl.prepare2_(CalcitePrepareImpl.java:507)
at
org.apache.calcite.prepare.CalcitePrepareImpl.prepare_(CalcitePrepareImpl.java:403)
at
org.apache.calcite.prepare.CalcitePrepareImpl.prepareSql(CalcitePrepareImpl.java:372)
at
org.apache.calcite.jdbc.CalciteConnectionImpl.parseQuery(CalciteConnectionImpl.java:174)
at
org.apache.calcite.jdbc.CalciteMetaImpl.prepareAndExecute(CalciteMetaImpl.java:471)
at
org.apache.calcite.avatica.AvaticaConnection.prepareAndExecuteInternal(AvaticaConnection.java:434)
at
org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:117)
at
org.apache.calcite.test.CalciteAssert.assertQuery(CalciteAssert.java:448)
at
org.apache.calcite.test.CalciteAssert$AssertQuery.returns(CalciteAssert.java:1145)
at
org.apache.calcite.test.CalciteAssert$AssertQuery.explainMatches(CalciteAssert.java:1227)
at
org.apache.calcite.test.CalciteAssert$AssertQuery.explainContains(CalciteAssert.java:1222)
at
org.apache.calcite.test.MongoAdapterIT.testSelectWhere(MongoAdapterIT.java:331)
{noformat}
> Add Vagrant files to enable testing of data storages: mysql, postgresql,
> mongo, etc
> -----------------------------------------------------------------------------------
>
> Key: CALCITE-507
> URL: https://issues.apache.org/jira/browse/CALCITE-507
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Reporter: Vladimir Sitnikov
> Assignee: Julian Hyde
> Labels: newbie
> Fix For: next
>
>
> As discussed in email list, it makes sense to implement Vagrant (or similar)
> VM machines to simplify testing of the downstream executors.
> Currently it is not clear how to configure mysql/mongo/etc.
> Not sure if it should be a set of separate configurations or a single
> configuration with all the batteries included.
> For instance, Vagrant allows to configure a [set of
> machines|https://docs.vagrantup.com/v2/multi-machine/index.html], while still
> providing a way to start just a subset.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
