[
https://issues.apache.org/jira/browse/CALCITE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-507.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: next)
1.3.0-incubating
Fixed in
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/ca871d37.
> 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: 1.3.0-incubating
>
>
> 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)
