[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[
https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041745#comment-17041745
]
Hadoop QA commented on OOZIE-3266:
--
Testing JIRA OOZIE-3266
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 4 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 [22] 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:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{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: 3208
{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/1304/
> Coord action rerun
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041677#comment-17041677 ] Hadoop QA commented on OOZIE-3266: -- PreCommit-OOZIE-Build started > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.3.0 > > Attachments: OOZIE-3266-v1.txt, OOZIE-3266-v2.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877740#comment-16877740 ] Julia Kinga Marton commented on OOZIE-3266: --- [~zuston], please upload the new patch here as well, to trigger the precommit job. Also please cover the new feature with test cases and update the documentation as well (DG_CoordinatorRerun.md) > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt, OOZIE-3266-v2.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875971#comment-16875971 ] Julia Kinga Marton commented on OOZIE-3266: --- Thank you [~zuston]! I have left some comments on the RB. > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt, OOZIE-3266-v2.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870783#comment-16870783 ] Junfan Zhang commented on OOZIE-3266: - Thanks [~kmarton]. The ReviewBoard link is [https://reviews.apache.org/r/70931/diff/1/] > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt, OOZIE-3266-v2.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867415#comment-16867415 ] Julia Kinga Marton commented on OOZIE-3266: --- [~zuston], can you please upload your patch to ReviewBoard? > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt, OOZIE-3266-v2.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861042#comment-16861042 ] Junfan Zhang commented on OOZIE-3266: - [~asalamon74] Please review it . The failing pre-commit issues looks unrelated. > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt, OOZIE-3266-v2.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[
https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860975#comment-16860975
]
Hadoop QA commented on OOZIE-3266:
--
Testing JIRA OOZIE-3266
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 4 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 [17] 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:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{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:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{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 [webapp].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:red}-1{color} There are [2] 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 CoordJobGetActionsSubsetJPAExecutor.java:[line 111]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At CoordJobGetActionsSubsetJPAExecutor.java:[line 77]: At
CoordJobGetActionsSubsetJPAExecutor.java:[line 76]
.At CoordJobGetActionsSubsetJPAExecutor.java:[line 86]: At
CoordJobGetActionsSubsetJPAExecutor.java:[line 85]
.At CoordJobGetActionsSubsetJPAExecutor.java:[line 111]: At
CoordJobGetActionsSubsetJPAExecutor.java:[line 108]
.At ShareLibService.java:[line 695]: Unsafe comparison of hash that are
susceptible to timing attack
{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: 3168
.{color:orange}Tests failed at first run:{color}
TestIntegrationGitActionExecutor#testWhenRepoIsClonedThenGitIndexContentIsReadSuccessfully
.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
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860787#comment-16860787 ] Hadoop QA commented on OOZIE-3266: -- PreCommit-OOZIE-Build started > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt, OOZIE-3266-v2.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[
https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834599#comment-16834599
]
Hadoop QA commented on OOZIE-3266:
--
Testing JIRA OOZIE-3266
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:green}+1{color} the patch does not introduce any star imports
.{color:red}-1{color} the patch contains 1 line(s) longer than 132
characters
.{color:green}+1{color} the patch adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:red}-1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:red}-1{color} the patch seems to introduce 3 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 [15] 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:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{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:red}-1{color} There are [8] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 529]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 526]: At OozieDBCLI.java:[line 525]
.At OozieDBCLI.java:[line 528]: At OozieDBCLI.java:[line 527]
.This use of java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be
vulnerable to SQL injection: At OozieDBCLI.java:[line 529]
.At OozieDBCLI.java:[line 525]: At OozieDBCLI.java:[line 554]
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{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 [webapp].
.{color:green}+1{color} There are no new bugs found in [examples].
.{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:
.Redundant null check at CoordActionStartXCommand.java:[line 219]:
Redundant nullcheck of runConf, which is known to be non-null in
org.apache.oozie.command.coord.CoordActionStartXCommand.execute()
.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]
{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
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834476#comment-16834476 ] Hadoop QA commented on OOZIE-3266: -- PreCommit-OOZIE-Build started > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: Junfan Zhang >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834472#comment-16834472 ] Junfan Zhang commented on OOZIE-3266: - [~txsing], do you have any plans to continue this issue? I would take it over if you have other priorities. > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: TIAN XING >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591766#comment-16591766 ] Andras Piros commented on OOZIE-3266: - [~txsing] any chance you've time to finish this fix? > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: TIAN XING >Priority: Major > Fix For: 5.2.0 > > Attachments: OOZIE-3266-v1.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[
https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561923#comment-16561923
]
Andras Piros commented on OOZIE-3266:
-
Thanks for the contribution [~txsing]! Seems like a valuable addition to the
rerun functionality.
Can you please address failing pre-commit issues in {{RAW_PATCH_ANALYSIS}},
{{JAVADOC}}, and {{FINDBUGS_DIFF}} sections? Thanks!
> Coord action rerun support RERUN_SKIP_NODES option
> --
>
> Key: OOZIE-3266
> URL: https://issues.apache.org/jira/browse/OOZIE-3266
> Project: Oozie
> Issue Type: New Feature
>Affects Versions: 5.1.0
>Reporter: TIAN XING
>Assignee: TIAN XING
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3266-v1.txt
>
>
> currently, when you re-run a workflow job, you have 3 options
> # re-run all of its action nodes
> # re-run failed nodes only
> # re-run with specified nodes skipped
> if this workflow job is generated by a coord action. you can re-run this
> coord action with 2 options
> # re-run all of the workflow action nodes (generate a new workflow job id)
> # re-run failed workflow action nodes only (workflow job id not changed)
> now we want to add a another option
> - re-run with specified workflow nodes skipped (workflow job id not changed)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[
https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551206#comment-16551206
]
Hadoop QA commented on OOZIE-3266:
--
Testing JIRA OOZIE-3266
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 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:red}-1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:red}-1{color} the patch seems to introduce 1 new Javadoc warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
error(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 [1] 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 [webapp].
. {color:red}-1{color} There are [1] new bugs found below threshold in [core]
that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones):
core/findbugs-new.html
. The most important FindBugs errors are:
. Redundant null check at CoordActionStartXCommand.java:[line 210]: Redundant
nullcheck of runConf, which is known to be non-null in
org.apache.oozie.command.coord.CoordActionStartXCommand.execute()
. {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 [docs].
. {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/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/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/oozie].
. {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/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{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: 2908
.{color:orange}Tests failed at first run:{color}
TestJMSAccessorService#testConnectionRetryExceptionListener
.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/678/
> Coord action rerun support RERUN_SKIP_NODES option
> --
>
> Key: OOZIE-3266
> URL: https://issues.apache.org/jira/browse/OOZIE-3266
> Project: Oozie
> Issue Type: New Feature
>Affects Versions: 5.1.0
>Reporter: TIAN XING
>Assignee: TIAN XING
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3266-v1.txt
>
>
> currently, when you re-run a workflow job, you have 3 options
> # re-run all of its action nodes
> # re-run failed nodes only
> # re-run with specified nodes skipped
> if this workflow job is generated by a coord action. you can re-run this
> coord action with 2 options
> # re-run all of the workflow action nodes (generate a new workflow job id)
> # re-run failed workflow action nodes only (workflow job id not changed)
> now we want to add a another option
> - re-run with specified workflow nodes skipped (workflow job id not changed)
--
This message was sent by Atlassian JIRA
[jira] [Commented] (OOZIE-3266) Coord action rerun support RERUN_SKIP_NODES option
[ https://issues.apache.org/jira/browse/OOZIE-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551119#comment-16551119 ] Hadoop QA commented on OOZIE-3266: -- PreCommit-OOZIE-Build started > Coord action rerun support RERUN_SKIP_NODES option > -- > > Key: OOZIE-3266 > URL: https://issues.apache.org/jira/browse/OOZIE-3266 > Project: Oozie > Issue Type: New Feature >Affects Versions: 5.1.0 >Reporter: TIAN XING >Assignee: TIAN XING >Priority: Major > Fix For: 5.1.0 > > Attachments: OOZIE-3266-v1.txt > > > currently, when you re-run a workflow job, you have 3 options > # re-run all of its action nodes > # re-run failed nodes only > # re-run with specified nodes skipped > if this workflow job is generated by a coord action. you can re-run this > coord action with 2 options > # re-run all of the workflow action nodes (generate a new workflow job id) > # re-run failed workflow action nodes only (workflow job id not changed) > now we want to add a another option > - re-run with specified workflow nodes skipped (workflow job id not changed) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
