[
https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715563#comment-13715563
]
Robert Kanter commented on OOZIE-1461:
--------------------------------------
I'm not clear on the "auto-deploy option"; isn't that what happens now?
Or do you mean that Oozie would create/maintain a dir in HDFS that has all of
the launcher jars in it, and would just include them with the appropriate
action? Instead of that, wouldn't it be simpler to just keep the necessary
classes in the sharelib (like when oozie.action.ship.launcher = false) and not
add this new behavior?
If the issue is to have Oozie automatically maintain the launcher jars and/or
sharelib (so that an admin doesn't have to manually copy them), what if we had
it so that Oozie would upload the sharelib when it starts up? We could even
re-use the code from OOZIE-1054. Though if we did this, it should probably
have a config to turn enable/disable it.
> 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
