[
https://issues.apache.org/jira/browse/OOZIE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohini Palaniswamy resolved OOZIE-1518.
---------------------------------------
Resolution: Won't Fix
Closing this jira as the approach finalized is
1) Admin runs sharelib create command which copies the sharelib contents into a
new timestamped version of the sharelib directory (lib_<timestamp>) under the
system lib path directory.
2) Oozie on startup picks up the latest directory.
3) Admin can run sharelib create command again if there are new version of jar
available which will create a new timestamped version of the sharelib
directory. Then "oozie admin -sharelibupdate" command can be issued to the
server to make it pick up the latest sharelib. "oozie admin -shareliblist" will
be used to list the available directories in the sharelib.
4) Optionally instead of a sharelib directory, a sharelib meta file can be used
to specify different sharelib directory locations.
> Copy action sharelib jars from hdfs
> ------------------------------------
>
> Key: OOZIE-1518
> URL: https://issues.apache.org/jira/browse/OOZIE-1518
> Project: Oozie
> Issue Type: Sub-task
> 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 was sent by Atlassian JIRA
(v6.1#6144)
