[
https://issues.apache.org/jira/browse/CALCITE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486339#comment-14486339
]
Julian Hyde commented on CALCITE-507:
-------------------------------------
I've made some fixes, and I think this is ready to go in. [~vlsi], can you
please:
1. Accept my pull request https://github.com/vlsi/calcite-test-dataset/pull/1
up to and including
https://github.com/julianhyde/calcite-test-dataset/commit/78507bf41fd9ff60b6aa120b98112004ed4ed0ae.
2. Review my branch https://github.com/julianhyde/incubator-calcite/tree/507
(which is a rebased version of
https://github.com/vlsi/incubator-calcite/tree/mongo_tests_fixup with fixes).
3. When master branch is open following the 1.2 release, rebase and commit to
master.
> 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)
