[ 
https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shwetha G S updated OOZIE-1876:
-------------------------------
    Attachment: OOZIE-1876-v7.patch

Finally, here is a working patch. [~rkanter], can you please take a look? (even 
others can review:))

Here are the changes:
1. All the versions are configurable - hadoop, hive, distcp, auth
2. oozie.war bundles all the required jars - required hadoop and hcat 
dependencies. (Reasoning: Currently, we need to add hadoop and hcat jars at 
runtime in libext. Since we won't know which are the exact jars required, we 
end up adding everything in hadoop and hcat classpath. In newer versions of 
hadoop and hive, there are so many jars that the final oozie application has 
multiple versions of the same jar and creates conflicts)
3. ooze-start without ooze-setup does setup automatically
4. Removed packaging jars in lib and libtools. Instead, picks up the jars by 
exploding oozie.war

Testing:
1. Compiled using different combinations of hadoop profile and version
2. Verified few workflows with oozie setup with hadoop-2.5.0

> use pom properties rather than specific version numbers in the pom files of 
> hbaselibs, hcataloglibs, sharelib, etc 
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1876
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1876
>             Project: Oozie
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 4.0.1
>            Reporter: John
>            Assignee: Shwetha G S
>             Fix For: trunk
>
>         Attachments: OOZIE-1876-v2.patch, OOZIE-1876-v3.patch, 
> OOZIE-1876-v4.patch, OOZIE-1876-v5.patch, OOZIE-1876-v5.patch, 
> OOZIE-1876-v6.patch, OOZIE-1876-v7.patch, OOZIE-1876.patch
>
>
> version numbers (hbase, hive, hcatalog, sqoop, etc) are hard coded in the pom 
> files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to