[
https://issues.apache.org/jira/browse/OOZIE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405960#comment-13405960
]
Robert Kanter commented on OOZIE-748:
-------------------------------------
There's a related bug with the lib path that I'll be uploading soon.
> Add support for oozie.libpath to be set on a per-action basis in workflow.xml
> -----------------------------------------------------------------------------
>
> Key: OOZIE-748
> URL: https://issues.apache.org/jira/browse/OOZIE-748
> Project: Oozie
> Issue Type: Improvement
> Components: workflow
> Affects Versions: 3.2.0
> Reporter: J. McConnell
> Assignee: Robert Kanter
> Attachments: OOZIE-748-v2.patch, OOZIE-748-v3.patch, OOZIE-748.patch
>
>
> Currently, the oozie.libpath setting is allowed in job.properties when
> submitting a job to run in order to add a second directory to load jars from.
> It would be useful if the value of this setting set in the configuration of
> workflow actions were honored and the jars loaded.
> The use case is that I have three existing Java apps each with their
> dependencies managed by Maven. To avoid dependency conflicts, I have to
> deploy their dependencies to three separate directories. What I would like to
> do is create a single workflow with three Java actions to execute the three
> jobs, but they each need their own setting for oozie.libpath.
> Note: It may actually be oozie.launcher.oozie.libpath that should be
> configured within a workflow action. Either way, support for this
> functionality would be welcome.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
