[
https://issues.apache.org/jira/browse/OOZIE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002452#comment-14002452
]
Purshotam Shah commented on OOZIE-1789:
---------------------------------------
{quote}
Would it make sense for the oozie-setup.sh sharelib command to delete the old
sharelib when installing the lib_<timestamp> one?
{quote}
We need to be careful with deleting sharelib. If I have a long running pig job
( which might run for a day) and if i decide to upgrade sharelib and if we are
deleting old sharelib as part of {{oozie-setup.sh sharelib}}, then running jobs
will start failing.
{quote}
On the other hand, we don't want to delete their old sharelib directories in
case they put some custom jar in there.
{quote}
As a part of sharelibservice we are not deleting any older sharelib.
There are few other way to make sharelib upgrade smooth.
While upgrading sharelib, user can change the sharelib path to new dir and use
{{oozie-setup.sh sharelib}} to upgrade sharelib.
In this way both old and new sharelib will in DFS and removing old sharelib
will be easy.
After few days (or week) once user knows that no running jobs is using old
sharelib, he can delete old sharelib.
Deleting old sharelib should be easy, we may not need any script to do that, it
will be -rmr command on old sharelib directory.
> Support backward compatibility of oozie share lib
> -------------------------------------------------
>
> Key: OOZIE-1789
> URL: https://issues.apache.org/jira/browse/OOZIE-1789
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.1.3, 3.2.0, 3.3.0, 3.3.1, 3.3.2, 4.0.0, 4.0.1
> Reporter: Satish Mittal
> Assignee: Purshotam Shah
> Priority: Critical
>
> The current oozie trunk is not backward compatible with the way oozie share
> lib is configured. Till now, user would manually upload sharelib to HDFS at
> the system libpath, typically
> {noformat}
> "/user/${user.name}/share/lib/"
> {noformat}
> Whereas with latest oozie, one has to use "oozie-setup.sh sharelib create"
> command to first upload sharelib.
> As a result, no one can run any actions if directly upgrading from 4.0 or
> before to the new version. There should be a way to support the older
> sharelib format in addition to the new format. This is needed for smooth
> upgrade to latest oozie.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
