[
https://issues.apache.org/jira/browse/TAJO-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaeHwa Jung updated TAJO-336:
-----------------------------
Attachment: TAJO-336_2.patch
Thanks guys!
I moved '/tajo-hive' to '/tajo-catalog/tajo-catalog-drivers/tajo-hcatalog'. If
catalog store modules located on root directory, it may make many directories
and it may look like inefficient. And if we want to add more catalog store, we
just need to add catalog store module on 'tajo-catalog-drivers'.
And I separated catalog drives module from main module. If we execute 'mvn
clean install' or 'mvn pacakage -Pdist', tajo doesn't build hcatalog module. If
we want to build hcatalog module, we must specify hcatalog version and hadoop
version as follows:
{code:xml}
mvn clean package -Pdist -Phcatalog-0.12.0 -Phadoop20 (hive-0.12.0 and
hadoop-1.x.x)
mvn clean package -Pdist -Phcatalog-0.12.0 -Phadoop26 (hive-0.12.0 and
hadoop-2.0.6-alpha)
{code}
Finally, If users want to use HCatalogStore, users must set HIVE_HOME at
tajo-env.sh. If users set HIVE_HOME, tajo shell add hcatalog dependencies to
classpath.
P.S I'll write a wiki document which describe how to integrate with hive this
week. :)
> Separate catalog stores into separate modules
> ---------------------------------------------
>
> Key: TAJO-336
> URL: https://issues.apache.org/jira/browse/TAJO-336
> Project: Tajo
> Issue Type: Improvement
> Components: build, catalog
> Affects Versions: 0.8-incubating
> Reporter: Hyunsik Choi
> Assignee: JaeHwa Jung
> Priority: Blocker
> Fix For: 0.8-incubating
>
> Attachments: TAJO-336.patch, TAJO-336_2.patch
>
>
> Catalog stores, such as HCatalogStore, involves dependencies to other
> systems. Their dependencies may be conflict from Tajo's dependencies because
> the dependent library versions can be varied in many cases.
> As to this problem, separating catalog stores from catalog-server module
> would be a good solution.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
