[
https://issues.apache.org/jira/browse/OOZIE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769951#comment-13769951
]
Robert Kanter commented on OOZIE-1518:
--------------------------------------
My concern with this approach is that the sharelib is already one of the more
confusing things for users and they're going to look at this and wonder why
they now have more than one sharelib. Or they'll try to upload the sharelib to
the old location instead of {{lib-staging}} etc (which reminds me, we'd also
need a way to "upgrade" from the old way {{share/lib/}} to the new way
{{share/lib-staging/}}).
The nice thing about having the staging dir in the local filesystem was that it
completely hides HDFS from them and we can have a "default installation" of the
sharelib without the user having to do anything.
However, I agree that doing it on the local fs is more complicated/difficult
for us. If we do it in HDFS, is there some way we can make it less confusing
for users?
> 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
