[
https://issues.apache.org/jira/browse/S2GRAPH-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320638#comment-15320638
]
ASF GitHub Bot commented on S2GRAPH-70:
---------------------------------------
Github user jongwook commented on the issue:
https://github.com/apache/incubator-s2graph/pull/57
If that's the cause, I guess we should exclude mysql-connector-java and
document it that way ..
> Automate the process of building a distribution package
> -------------------------------------------------------
>
> Key: S2GRAPH-70
> URL: https://issues.apache.org/jira/browse/S2GRAPH-70
> Project: S2Graph
> Issue Type: Improvement
> Reporter: Jong Wook Kim
>
> Since the Vagrant image (which is the only documented way to trying out
> S2Graph) is outdated, and also as a prerequisite of making a release, it is
> desirable to be able to readily make a distribution package. The goal is to
> be able for an end-user to download & untar the package, and run a shell
> script to start off s2graph and all its dependencies.
> AFAIK S2graph requires mysql for storing the metadata and HBase for the
> actual data. Both could be contained in the package if:
> - we run HBase server that is in the hbase-server jar, running without HDFS,
> saving data in the local filesystem instead, and
> - instead of the full MySQL server, use an embedded database like derby or h2
> to store the metadata.
> It would also require some technical consideration about how exactly we
> should layout the files and what toolchain we should use to build the
> package, so I think adding child issues for each subtask would be appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
