[
https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715933#comment-13715933
]
Rohini Palaniswamy commented on OOZIE-1461:
-------------------------------------------
Really would like to get away from doing anything manual or that is prone to
human errors. Moreover the launcher jars are system code that do not change for
a version of oozie unlike new versions of pig or hive which can change
irrespective of the oozie version.
Is there any problems with the approach we are trying to take? It only builds
upon and enhances the sharelib work you had done. If there is a better
approach, that does not involve educating admins or debugging failures because
they forgot to deploy a new sharelib and point oozie to it, would be glad to
implement that. Also most of our users don't have oozie.use.system.libpath
configured to true in their job. properties. And so if it is just in sharelib,
it will not be picked up. It is not possible and we don't want to ask all our
users to change their job configuration.
> provide an option to auto-deploy launcher jar onto HDFS system libpath
> ----------------------------------------------------------------------
>
> Key: OOZIE-1461
> URL: https://issues.apache.org/jira/browse/OOZIE-1461
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Ryota Egashira
> Assignee: Ryota Egashira
> Fix For: trunk
>
>
> after OOZIE-1311, 1315, when oozie.action.ship.launcher.jar is false,
> launcher jar is shipped from sharelib, but it requires manual process for
> admin people to upload jar files onto the sharelib at server-start time,
> before actually starting running workflow actions. This JIRA to provide an
> option to remove the manual process, and make oozie server (ActionService) to
> automatically create and upload launcher jar files onto HDFS (tmp directory
> under oozie.service.WorkflowAppService.system.libpath), and allow workflow
> actions to consume from there. every time oozie server starts, it
> automatically creates a new directory to upload launcher jars to, and also
> purges stale directories previously created (older than 7 days,
> configurable).
> if false (which is current default). the behavior is the same with previous,
> launcher jars provided from sharelib (when
> oozie.action.ship.launcher.jar=false) or each workflow action creates and
> ships launcher jar (when oozie.action.ship.launcher.jar=true)
--
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
