[
https://issues.apache.org/jira/browse/HCATALOG-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080770#comment-13080770
]
Andreas Neumann commented on HCATALOG-76:
-----------------------------------------
+1 on the separate build targets.
Dmitriy,
What would you consider "contrib"? All of the storage drivers? What will
distinguish an "out-of-the-box" driver from a "contrib" driver?
My experience with putting stuff into a separate repo is that it tends to
diverge with trunk and and some point will not work any more, and it is
difficult to do continuous integration across repos, especially in different
infrastructures. I would prefer to have separate build targets but a shared
repo. However, I am not sure what the problems were in Pig, so please help me
understand.
-Andreas.
> Storage driver deployment
> -------------------------
>
> Key: HCATALOG-76
> URL: https://issues.apache.org/jira/browse/HCATALOG-76
> Project: HCatalog
> Issue Type: Improvement
> Reporter: Olga Natkovich
>
> We need to have a way to add new drivers to the system. This raises a few
> questions:
> (1) Where the drivers stored in SVN
> (2) What is the structure of deployed drivers (packages, directory structure,
> config, etc.)
> (3) How drivers get deployed
> We are working on the Hbase driver for HCat and starting to look at (1). Our
> proposal is to keep things simple and to create a driver directory in
> HCatalog source tree with a directory for each driver. Each driver would then
> have its own build process, dependencies etc. At the end of the build process
> it will produce whatever we decide is required for (2) but at least one or
> more jar files. We think all core drivers including the current default ones
> should follow the same structure (though we do not have to jump right away
> and re-factor the code). The core drivers would be the ones that the project
> agrees to maintain long term. We can also have similar structure under
> contrib for those that not initial considered to be core ones. Comments?
> We have some suggestions for (2) and (3) as well but want to discuss (1) first
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
