[ https://issues.apache.org/jira/browse/OOZIE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011930#comment-14011930 ]
Purshotam Shah commented on OOZIE-1789: --------------------------------------- {quote} Later if user runs setup.sh to install newer style sharelib, the command should still retain older one since it gives user a chance to move over any jars from older to new location. {quote} Do you want to keep older sharelib for forever, i think we should purge them. > 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)