You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2012/06/29 02:15:45 UTC
[jira] [Updated] (OOZIE-748) Add support for oozie.libpath to be
set on a per-action basis in workflow.xml
[ https://issues.apache.org/jira/browse/OOZIE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Kanter updated OOZIE-748:
--------------------------------
Attachment: OOZIE-748.patch
I used oozie.launcher.oozie.libpath and you can give it either a directory or a file. I created a test and also modified one of the examples to verify that it works.
> 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
> Attachments: 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