[
https://issues.apache.org/jira/browse/S2GRAPH-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DOYUNG YOON updated S2GRAPH-75:
-------------------------------
Fix Version/s: 0.1.0
> Use an embedded database as the default metadata storage
> --------------------------------------------------------
>
> Key: S2GRAPH-75
> URL: https://issues.apache.org/jira/browse/S2GRAPH-75
> Project: S2Graph
> Issue Type: Sub-task
> Reporter: Jong Wook Kim
> Fix For: 0.1.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The current choice of the metadata storage - MySQL - served well for the
> production usage, but running the DBMS, creating database and tables,
> configuring the JDBC, etc. has not been transparent to the users, and most
> importantly, is not documented anywhere.
> In order for the users to be able to just download and run s2graph, it is
> desirable to use the metadata storage without setting up a separate MySQL
> server, at least for the first run. We should then recommend MySQL or similar
> for production usage.
> Derby, H2 and HSQL are popular choices for an embedded database in JVM, and
> we should figure out the most appropriate choice for us.
> As a side note, currently the only way to get the schema is to hack on the
> Vagrant image. This should also be made transparent and manageable somehow.
> For example, [Hive metastore's schema is being managed using a schema and
> upgrade
> SQLs|https://github.com/apache/hive/tree/master/metastore/scripts/upgrade/mysql]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
