[
https://issues.apache.org/jira/browse/OOZIE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758562#comment-13758562
]
Rohini Palaniswamy commented on OOZIE-1518:
-------------------------------------------
[~tucu00]/[~rkanter],
Only thing we are thinking of doing different here after our last discussion
is to have the sharedlib staging copy in hdfs instead of oozie local
filesystem. This simplifies HA case and don't have to update multiple oozie
servers or have entries in zookeeper to decide who manages sharedlib. Also if
admin is updating pig or hive, they can just update that in hdfs and issue
oozie command to update sharedlib instead of logging into oozie server.
> Copy action sharelib jars from hdfs
> ------------------------------------
>
> Key: OOZIE-1518
> URL: https://issues.apache.org/jira/browse/OOZIE-1518
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
>
> OOZIE-1461 will copy the launcher related sharelib jars from Oozie's
> classpath to hdfs.
> This JIRA aims to copy the jars from an hdfs staging dir. This staging dir
> will typically contain action related jars.
> OOZIE-1461 always creates a sharelib with new timestamp. This JIRA will make
> sure that only if either the action jars or launcher jars are modified, then
> a new sharelib is created.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
