[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398481#comment-16398481 ] Peter Cseh commented on OOZIE-2814: --- +1 for patch-07 > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Fix For: 5.0.0 > > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397145#comment-16397145 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 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:orange}0{color} There are [1] new bugs found in total that would be nice to have fixed. . {color:green}+1{color} There are no new bugs found in [webapp]. . {color:orange}0{color} There are [1] new bugs found in [core] that would be nice to have fixed. . You can find the FindBugs diff here: core/findbugs-new.html . {color:green}+1{color} There are no new bugs found in [tools]. . {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/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/streaming]. . {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/pig]. . {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 [client]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [docs]. . {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:green}+1 TESTS{color} .Tests run: 2097 .{color:orange}Tests failed at first run:{color} TestJavaActionExecutor#testCredentialsSkip TestHiveActionExecutor#testHiveAction .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:green}*+1 Overall result, good!, no -1s*{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/446/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Fix For: 5.0.0 > > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396990#comment-16396990 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Fix For: 5.0.0 > > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395612#comment-16395612 ] Attila Sasvari commented on OOZIE-2814: --- [~gezapeti], [~andras.piros] can you review the latest patch? Thanks. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367624#comment-16367624 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 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:orange}0{color} There are [1] new bugs found in total that would be nice to have fixed. . {color:orange}0{color} There are [1] new bugs found in [core] that would be nice to have fixed. . You can find the FindBugs diff here: core/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 [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/streaming]. . {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/sqoop]. . {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/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [examples]. {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: 2097 .Tests failed: 1 .Tests errors: 1 .The patch failed the following testcases: testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService) .Tests failing with errors: testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService) {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/405/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367511#comment-16367511 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366901#comment-16366901 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 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:orange}0{color} There are [1] new bugs found in total that would be nice to have fixed. . {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:orange}0{color} There are [1] new bugs found in [core] that would be nice to have fixed. . You can find the FindBugs diff here: core/findbugs-new.html . {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: 2097 .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/404/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do th
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366821#comment-16366821 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365983#comment-16365983 ] Attila Sasvari commented on OOZIE-2814: --- {{mvn test -Dtest=TestHCatMessageHandler,TestDefaultConnectionContext,TestJMSSLAEventListener,TestJMSJobEventListener,TestPartitionDependencyManagerEhcache,TestRecoveryService -DtargetJavaVersion=1.8 -DjavaVersion=1.8}} pass locally. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365862#comment-16365862 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 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:orange}0{color} There are [1] new bugs found in total that would be nice to have fixed. . {color:orange}0{color} There are [1] new bugs found in [core] that would be nice to have fixed. . You can find the FindBugs diff here: core/findbugs-new.html . {color:green}+1{color} There are no new bugs found in [server]. . {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 [examples]. . {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/distcp]. . {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/spark]. . {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/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 [webapp]. . {color:green}+1{color} There are no new bugs found in [tools]. {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: 2097 .Tests failed: 17 .Tests errors: 12 .The patch failed the following testcases: testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener) testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener) testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener) testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener) testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener) testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener) testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener) testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener) testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener) testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener) testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener) testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener) testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener) testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener) testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener) testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache) testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService) .Tests failing with errors: testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler) testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler) testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext) testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService) testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener) testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener) testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener) testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener) testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListene
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365682#comment-16365682 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch, OOZIE-2814-07.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364256#comment-16364256 ] Attila Sasvari commented on OOZIE-2814: --- [~gezapeti] thanks - new schema for the distcp action was missing, - example workflows also need additional modifications. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364174#comment-16364174 ] Peter Cseh commented on OOZIE-2814: --- The patch looks good overall. Have you tried running the old examples after the code changes to check on backwards compatibility?https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=16363929# > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363929#comment-16363929 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 line(s) longer than 132 characters .{color:green}+1{color} the patch adds/modifies 2 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:orange}0{color} There are [1] new bugs found in total that would be nice to have fixed. . {color:green}+1{color} There are no new bugs found in [webapp]. . {color:orange}0{color} There are [1] new bugs found in [core] that would be nice to have fixed. . You can find the FindBugs diff here: core/findbugs-new.html . {color:green}+1{color} There are no new bugs found in [tools]. . {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/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/streaming]. . {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/pig]. . {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 [client]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [docs]. . {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: 2097 .Tests failed: 1 .Tests errors: 0 .The patch failed the following testcases: testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor) .Tests failing with errors: .{color:orange}Tests failed at first run:{color} TestJavaActionExecutor#testCredentialsSkip TestCoordActionsKillXCommand#testActionKillCommandDate .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/399/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363822#comment-16363822 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch, OOZIE-2814-06.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363090#comment-16363090 ] Andras Piros commented on OOZIE-2814: - [~asasvari] thanks for the contribution, +1 > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363064#comment-16363064 ] Attila Sasvari commented on OOZIE-2814: --- Can someone review this please? > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362775#comment-16362775 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 line(s) longer than 132 characters .{color:green}+1{color} the patch adds/modifies 2 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 [client]. . {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/sqoop]. . {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/streaming]. . {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/hcatalog]. . {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/distcp]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [core]. . {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{color} There are no new bugs found in [tools]. {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: 2097 {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/394/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362604#comment-16362604 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, > OOZIE-2814-05.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362419#comment-16362419 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361254#comment-16361254 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 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:green}+1 TESTS{color} .Tests run: 1241 {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}*+1 Overall result, good!, no -1s*{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/389/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361150#comment-16361150 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch, OOZIE-2814-03.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360766#comment-16360766 ] Andras Piros commented on OOZIE-2814: - [~asasvari] the failing tests within {{TestLiteWorkflowAppParser}} seem to be related. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360733#comment-16360733 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 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: 2095 .Tests failed: 11 .Tests errors: 2 .The patch failed the following testcases: testParserDefaultJobTrackerFail(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobalExtensionActions(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserDefaultJobTrackerWithGlobal(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobalLocalAlreadyExists(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserDefaultJobTracker(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobalJobXML(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobal(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService) testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService) testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener) testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache) .Tests failing with errors: testConfigDefaultPropsToAction(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) 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/386/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-0
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360640#comment-16360640 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, > OOZIE-2814-02.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349614#comment-16349614 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 2 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 [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: 2091 .Tests failed: 25 .Tests errors: 98 .The patch failed the following testcases: testMapReduceWithUberJarDisabled(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) testParserDefaultJobTrackerFail(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobalExtensionActions(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserDefaultJobTrackerWithGlobal(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobalLocalAlreadyExists(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserDefaultJobTracker(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobalJobXML(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testParserGlobal(org.apache.oozie.workflow.lite.TestLiteWorkflowAppParser) testRerun(org.apache.oozie.action.hadoop.TestRerun) testSubmitFailsWithInvalidLauncherEnvVars(org.apache.oozie.action.hadoop.TestJavaActionExecutor) testSubmitFailsWithNegativeMemory(org.apache.oozie.action.hadoop.TestJavaActionExecutor) testSubmitFailsWithNegativeVcores(org.apache.oozie.action.hadoop.TestJavaActionExecutor) testActionStartWithEscapeStrings(org.apache.oozie.command.coord.TestCoordActionStartXCommand) testWorkflowActionEvent(org.apache.oozie.event.TestEventGeneration) testWorkflowActionRecoveryUserRetry(org.apache.oozie.service.TestRecoveryService) testRerunFork(org.apache.oozie.command.wf.TestReRunXCommand) testSubWorkflowSuspend(org.apache.oozie.action.oozie.TestSubWorkflowActionExecutor) testSubWorkflowRerun(org.apache.oozie.action.oozie.TestSubWorkflowActionExecutor) testWfActionKillChildJob(org.apache.oozie.command.wf.TestWorkflowActionKillXCommand) testWfActionKillSuccess(org.apache.oozie.command.wf.TestWorkflowActionKillXCommand) testActionReuseWfJobAppPath(org.apache.oozie.command.wf.TestActionStartXCommand) testActionStart(org.apache.oozie.command.wf.TestActionStartXCommand) testActionWithEscapedStringAndCDATA(org.apache.oozie.command.wf.TestActionStartXCommand) testParallelFsAndShellWorkflowCompletesSuccessfully(org.apache.oozie.test.TestWorkflowRetries) testParallelFsAndShellWorkflowCompletesSuccessfully(org.apache.oozie.test.TestWorkflow) .Tests failing with errors: testActionConfLoadDefaultResources(org.apache.oozie.action.hadoop.TestHiveAc
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349472#comment-16349472 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349303#comment-16349303 ] Robert Kanter commented on OOZIE-2814: -- Good thing we're trying to use the new schemas ;) I'd also say we should change {{jobTracker}} to {{resourceManager}} as well: {code:xml} ${resourceManager} {code} > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349221#comment-16349221 ] Attila Sasvari commented on OOZIE-2814: --- [~rkanter] thanks a lot. I changed the java-main example workflow to use {{resource-manager}} instead of {{job-tracker}} {code:java} ${jobTracker}{code} Result of job submission: {code:java} Error: E0701 : E0701: XML schema error, No job-tracker defined{code} Workflow can be validated against the schema just fine, but {{LiteWorkflowAppParser}} needs to be adjusted as it only tries to fetch the child of the {{job-tracker}} element: https://github.com/apache/oozie/blob/ef6d0af5edeb18fbc0259d1962ac70f8ad7c2a0c/core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java#L424 TestLiteWorkflowAppParser is to be extended too. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
That was my pet peeve for a long time, it'd be a welcome change to replace jobTracker nomenclature. On Jan 31, 2018 4:05 PM, "Robert Kanter (JIRA)" wrote: > > [ https://issues.apache.org/jira/browse/OOZIE-2814?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16347605#comment-16347605 ] > > Robert Kanter commented on OOZIE-2814: > -- > > I think we should also update {{}} to {{}} > to encourage users to start using it. > > > OYA: Update example workflows to newest schemas > > --- > > > > Key: OOZIE-2814 > > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > > Project: Oozie > > Issue Type: Sub-task > >Affects Versions: 5.0.0 > >Reporter: Robert Kanter > >Assignee: Attila Sasvari > >Priority: Blocker > > Attachments: OOZIE-2814-00.patch > > > > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > > It may make sense to keep the older schemas too, to show that older > workflows still work. We have some examples where we have two workflow XML > files that do the same thing in different ways. > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) >
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347605#comment-16347605 ] Robert Kanter commented on OOZIE-2814: -- I think we should also update {{}} to {{}} to encourage users to start using it. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346275#comment-16346275 ] Hadoop QA commented on OOZIE-2814: -- Testing JIRA OOZIE-2814 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 line longer than 132 .{color:red}-1{color} the patch does not add/modify any testcase {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 [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:green}+1 TESTS{color} .Tests run: 2088 .{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/364/ > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346219#comment-16346219 ] Hadoop QA commented on OOZIE-2814: -- PreCommit-OOZIE-Build started > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345236#comment-16345236 ] Attila Sasvari commented on OOZIE-2814: --- I am not sure if it makes sense to keep older workflow schemas. Those are there in earlier releases and also under version control. Patch 00 only changes example workflows, but I guess we want to also update documentation and unit tests. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Assignee: Attila Sasvari >Priority: Blocker > Attachments: OOZIE-2814-00.patch > > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas
[ https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306578#comment-16306578 ] Robert Kanter commented on OOZIE-2814: -- Making this a blocker. It'll help get users to start using the newer schema with all of the OYA changes. > OYA: Update example workflows to newest schemas > --- > > Key: OOZIE-2814 > URL: https://issues.apache.org/jira/browse/OOZIE-2814 > Project: Oozie > Issue Type: Sub-task >Affects Versions: 5.0.0 >Reporter: Robert Kanter >Priority: Blocker > > OOZIE-2687 will add in a whole set of newer schemas that are more > Yarn-centric. Most, if not all, examples currently use pretty old versions > of the schemas. We should take this opportunity to update the examples to > the newest schemas added by OOZIE-2687, which should help demonstrate them. > It may make sense to keep the older schemas too, to show that older workflows > still work. We have some examples where we have two workflow XML files that > do the same thing in different ways. -- This message was sent by Atlassian JIRA (v6.4.14#64029)