You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/09/20 11:59:00 UTC
[jira] [Commented] (OOZIE-3179) Adding a configurable
config-default.xml location to a workflow
[ https://issues.apache.org/jira/browse/OOZIE-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934326#comment-16934326 ]
ASF subversion and git services commented on OOZIE-3179:
--------------------------------------------------------
Commit 6bdca1d1c043d6ad688f53602667ca5201af5a28 in oozie's branch refs/heads/master from Andras Salamon
[ https://gitbox.apache.org/repos/asf?p=oozie.git;h=6bdca1d ]
OOZIE-3179 Adding a configurable config-default.xml location to a workflow (jphelps via asalamon74)
> Adding a configurable config-default.xml location to a workflow
> ---------------------------------------------------------------
>
> Key: OOZIE-3179
> URL: https://issues.apache.org/jira/browse/OOZIE-3179
> Project: Oozie
> Issue Type: Improvement
> Reporter: Jason Phelps
> Assignee: Jason Phelps
> Priority: Major
> Attachments: OOZIE-3179-1.patch, OOZIE-3179-2.patch, OOZIE-3179-3.patch, OOZIE-3179-4.patch, OOZIE-3179-5.patch
>
>
> Recently a customer requested a way to include several job.properties variables to every workflow in their cluster.
> Normally the config-default.xml file would be the best way to include a set of variables, but it does not scale very well if that file needs to be updated, as it would require it to be updated in every workflow application path.
> What I am requesting is another job.properties variable that can point to a config-default.xml file, or a comma separated list of config-default.xml files that will all be applied to the workflow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)