[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=16934328#comment-16934328 ] Andras Salamon commented on OOZIE-3179: --- Thanks [~jphelps], +1, committed to master. > 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)
[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)
[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=16919943#comment-16919943
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any star imports
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [5] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:red}-1{color} There are [5] new bugs found below threshold in
[core] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:orange}0{color} There are [4] new bugs found in [server] that would
be nice to have fixed.
.You can find the SpotBugs diff here: server/findbugs-new.html
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3176
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/1213/
> 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-d
[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=16919882#comment-16919882 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > 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.2#803003)
[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=16918821#comment-16918821
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any star imports
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [7] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:red}-1{color} There are [7] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:orange}0{color} There are [4] new bugs found in [server] that would
be nice to have fixed.
.You can find the SpotBugs diff here: server/findbugs-new.html
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [webapp].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3176
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/1209/
> 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
>
>
> Recently a customer requested a way to include several job.properties
> variables to every workflow in their cluster.
>
[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=16918739#comment-16918739 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > 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 > > > 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.2#803003)
[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=16806520#comment-16806520 ] Andras Salamon commented on OOZIE-3179: --- [~jphelps] I left a few comments in the ReviewBoard. Mostly small code cleanups. > 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 > > > 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 (v7.6.3#76005)
[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=16805068#comment-16805068
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any star imports
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [4] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:red}-1{color} There are [4] new bugs found below threshold in
[core] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 207]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176]
.At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207]
.At BulkJPAExecutor.java:[line 112]: At BulkJPAExecutor.java:[line 128]
.{color:orange}0{color} There are [4] new bugs found in [server] that would
be nice to have fixed.
.You can find the SpotBugs diff here: server/findbugs-new.html
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3170
.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommand#testNone
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/1068/
> 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
>
>
> Recently a customer requeste
[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=16804945#comment-16804945 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > 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 > > > 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 (v7.6.3#76005)
[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=16804930#comment-16804930 ] Jason Phelps commented on OOZIE-3179: - Review board diff had a few extra changes I made (been a while since then) from Peter's review, which I just added back into patch #4. Will upload the same diff to Reviewboard [~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 > > > 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 (v7.6.3#76005)
[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=16804735#comment-16804735 ] Andras Salamon commented on OOZIE-3179: --- Thanks for the rebase [~jphelps]. Yes, it's very important that we handle the OOZIE-3370 changes here. Can you upload the patch to the [ReviewBoard|https://reviews.apache.org/dashboard/]? It's much easier to review the code there. > 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 > > > 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 (v7.6.3#76005)
[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=16801868#comment-16801868
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any star imports
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [5] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 92]: This usage of
java/lang/ProcessBuilder.(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 90]: At ShellMain.java:[line 89]
.At ShellMain.java:[line 91]
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:red}-1{color} There are [4] new bugs found below threshold in
[core] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 207]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176]
.At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207]
.At BulkJPAExecutor.java:[line 112]: At BulkJPAExecutor.java:[line 128]
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3170
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/1060/
> 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
>
[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=16801745#comment-16801745 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > 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 > > > 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 (v7.6.3#76005)
[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=16801736#comment-16801736 ] Jason Phelps commented on OOZIE-3179: - Adding rebased patch updated for the code changes in OOZIE-3370 as well > 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 > > > 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 (v7.6.3#76005)
[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=16801715#comment-16801715
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> 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
>
>
> 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
(v7.6.3#76005)
[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=16801700#comment-16801700 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > 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 > > > 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 (v7.6.3#76005)
[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=16801681#comment-16801681 ] Andras Salamon commented on OOZIE-3179: --- [~jphelps] Can you please rebase the patch? > 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 > > > 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 (v7.6.3#76005)
[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=16362596#comment-16362596
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2093
.Tests failed: 3
.Tests errors: 1
.The patch failed the following testcases:
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
.Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/393/
> 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
>
>
> 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
(v7.6.3#76005)
[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=16362444#comment-16362444 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > 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 > > > 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 (v7.6.3#76005)
[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=16362440#comment-16362440 ] Jason Phelps commented on OOZIE-3179: - Attached another patch to fix the "longer than 132 characters" warning. > 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 > > > 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 (v7.6.3#76005)
[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=16362382#comment-16362382 ] Andras Piros commented on OOZIE-3179: - Thanks for the contribution [~jphelps]! Can you please add a [*ReviewBoard review request*|https://reviews.apache.org/dashboard/] as well? Thanks! > 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 > > > 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 (v7.6.3#76005)
[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=16361638#comment-16361638
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 1 line(s) longer than 132
characters
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2093
.Tests failed: 3
.Tests errors: 1
.The patch failed the following testcases:
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
.Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/390/
> 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
>Priority: Major
> Attachments: OOZIE-3179-1.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
(v7.6.3#76005)
[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=16361559#comment-16361559 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > 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 >Priority: Major > Attachments: OOZIE-3179-1.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 (v7.6.3#76005)
[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=16358863#comment-16358863 ] Jason Phelps commented on OOZIE-3179: - This was basically asked on Stack Overflow a few months ago as well [https://stackoverflow.com/questions/46220293/is-there-a-way-to-use-config-default-xml-globally-in-oozie] > 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 >Priority: Major > > 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 (v7.6.3#76005)
