[jira] [Commented] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619386#comment-16619386
 ] 

Hadoop QA commented on OOZIE-3343:
--


Testing JIRA OOZIE-3343

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: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:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [core].
. {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 
[fluent-job/fluent-job-api].
. {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/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/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/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/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 [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: 2983
{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/834/



> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3343 PreCommit Build #834

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3343
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/834/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 9.47 MB...]
[DEBUG] There are no new bugs found in [sharelib/git].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive2].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2588 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3343

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 2 line(s) longer than 132 characters
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [webapp].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2983
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/834/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13184593/comment/16619386","id":"16619386","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 

[jira] [Commented] (OOZIE-3342) Missing examples archive from fluentjob examples

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619366#comment-16619366
 ] 

Hadoop QA commented on OOZIE-3342:
--


Testing JIRA OOZIE-3342

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:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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 
[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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [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:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
.{color:orange}Tests failed at first run:{color}
TestMetricsInstrumentation#testJMXInstrumentation
.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/833/



> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch, 
> OOZIE-3342-3.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: 

Failed: OOZIE-3342 PreCommit Build #833

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3342
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/833/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 6.57 MB...]
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/git].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2588 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3342

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
There were errors during execution. Check console output for details.
Tests failed at first run:
TestMetricsInstrumentation#testJMXInstrumentation
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/833/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  35330 0  100  3533  0   4043 --:--:-- --:--:-- --:--:--  
4042{"self":"https://issues.apache.org/jira/rest/api/2/issue/13184073/comment/16619366","id":"16619366","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting 

[jira] [Commented] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619294#comment-16619294
 ] 

Hadoop QA commented on OOZIE-3307:
--


Testing JIRA OOZIE-3307

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 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
.{color:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [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/git].
. {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 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {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 [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:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{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/832/



> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch, 
> OOZIE-3307.003.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties 

[jira] [Commented] (OOZIE-2734) [docs] Switch from TWiki to Markdown

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619239#comment-16619239
 ] 

Hadoop QA commented on OOZIE-2734:
--


Testing JIRA OOZIE-2734

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:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [webapp].
. {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 
[fluent-job/fluent-job-api].
. {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/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/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}
There were errors during execution. Check console output for details.
{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/831/



> [docs] Switch from TWiki to Markdown
> 
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-10.patch, 
> OOZIE-2734-2.patch, OOZIE-2734-3.patch, OOZIE-2734-4.patch, 
> OOZIE-2734-5.patch, OOZIE-2734-6.patch, OOZIE-2734-7.patch, 
> OOZIE-2734-8.patch, OOZIE-2734-9.patch, OOZIE-2734-amend-11.patch, 
> OOZIE-2734.amend.002.patch, oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, 
> oozie_generated_html_markdown_20180912.zip, 
> oozie_generated_html_markdown_20180913.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> 

Failed: OOZIE-2734 PreCommit Build #831

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-2734
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/831/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 4.85 MB...]
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2588 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-2734

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
There were errors during execution. Check console output for details.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/831/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 

[jira] [Commented] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619231#comment-16619231
 ] 

Hadoop QA commented on OOZIE-3343:
--

PreCommit-OOZIE-Build started


> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619187#comment-16619187
 ] 

Hadoop QA commented on OOZIE-3343:
--


Testing JIRA OOZIE-3343

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: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:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [webapp].
. {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 
[fluent-job/fluent-job-api].
. {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/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/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: 2983
.Tests failed : 0
.Tests errors : 0
.Tests timeouts   : 1

Check console output for the full list of errors/failures
{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/830/



> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3343 PreCommit Build #830

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3343
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/830/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 3.31 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2588 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3343

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 2 line(s) longer than 132 characters
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2983
Tests failed : 0
Tests errors : 0
Tests timeouts   : 1

Check console output for the full list of errors/failures
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/830/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13184593/comment/16619187","id":"16619187","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3343\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 

[jira] [Commented] (OOZIE-3342) Missing examples archive from fluentjob examples

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619182#comment-16619182
 ] 

Hadoop QA commented on OOZIE-3342:
--

PreCommit-OOZIE-Build started


> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch, 
> OOZIE-3342-3.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
> not found
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
> org.apache.oozie.example.DemoJavaMain not found{noformat}
>  
> The examples should be modified to allow the user to specify the path of an 
> archive which contains the necessary files.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3342) Missing examples archive from fluentjob examples

[Andras Salamon (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619175#comment-16619175
 ] 

Andras Salamon commented on OOZIE-3342:
---

Patch3 fixes the long line

> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch, 
> OOZIE-3342-3.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
> not found
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
> org.apache.oozie.example.DemoJavaMain not found{noformat}
>  
> The examples should be modified to allow the user to specify the path of an 
> archive which contains the necessary files.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3342) Missing examples archive from fluentjob examples

[Andras Salamon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Salamon updated OOZIE-3342:
--
Attachment: OOZIE-3342-3.patch

> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch, 
> OOZIE-3342-3.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
> not found
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
> org.apache.oozie.example.DemoJavaMain not found{noformat}
>  
> The examples should be modified to allow the user to specify the path of an 
> archive which contains the necessary files.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3346) fix git example

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619173#comment-16619173
 ] 

Hadoop QA commented on OOZIE-3346:
--


Testing JIRA OOZIE-3346

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:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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 
[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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [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:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{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/829/



> fix git example
> ---
>
> Key: OOZIE-3346
> URL: https://issues.apache.org/jira/browse/OOZIE-3346
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3346-1.patch
>
>
> The git action example is not working, it gives E0701 error code:
> {noformat}
> $ bin/oozie job -oozie http://localhost:11000/oozie -config 
> examples/src/main/apps/git/job.properties -run 
> -DnameNode=hdfs://localhost:9000 -D jobTracker=localhost:8032
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.c: The matching 
> wildcard is strict, but no declaration can be found for element 'git'.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3346 PreCommit Build #829

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3346
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/829/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 6.57 MB...]
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/git].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2588 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3346

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
There were errors during execution. Check console output for details.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/829/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 

[jira] [Commented] (OOZIE-3342) Missing examples archive from fluentjob examples

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619164#comment-16619164
 ] 

Hadoop QA commented on OOZIE-3342:
--


Testing JIRA OOZIE-3342

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: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:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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 
[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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [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:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{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/828/



> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
> not found
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
> org.apache.oozie.example.DemoJavaMain not found{noformat}
>  
> The 

Failed: OOZIE-3342 PreCommit Build #828

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3342
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/828/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 6.56 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/git].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2588 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3342

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 1 line(s) longer than 132 characters
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
There were errors during execution. Check console output for details.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/828/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 

Re: Review Request 68737: OOZIE-3307 [core][oya] Limit heap usage of LauncherAM

[Peter Bacsko via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68737/#review208705
---




core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
Lines 1301 (patched)


What about "checkAndSetMaxHeapOption" ?



core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
Lines 1305 (patched)


Nit: extract magic number to constant



core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
Lines 1322-1340 (patched)


What does this loop do? Not easy to figure out at a cursory look.

Variable naming: can't we just call the loop variable "i" instead of 
"ixArg" ?



core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
Lines 2146-2153 (patched)


Consider extracting these numbers to final fields, would look better IMO. 

Any reason to define them as floating point literals?



core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java
Lines 160-162 (patched)


Nit:

what about

final int oneKB = 1 << 10;
final int oneMB = 1 << 20;
final int oneGB = 1 << 30;

or 

final int oneKB = 1024;
final int oneMB = 1024 * 1024;
final int oneGB = 1024 * 1024 * 1024;



core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java
Lines 175 (patched)


Does this really work?

ByteBuffer.allocate() returns a HeapByteBuffer instance. However, you don't 
save its reference, so when it's GC-time, it will be simply collected.

In general this allocator code is too complicated, I would try to find a 
way to simplify this.


- Peter Bacsko


On szept. 18, 2018, 1:06 du, András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68737/
> ---
> 
> (Updated szept. 18, 2018, 1:06 du)
> 
> 
> Review request for oozie and Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3307 [core][oya] Limit heap usage of LauncherAM
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 0385c77b4c01a3ec7ee9147b2369db5b1548ad80 
>   core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
> ada7005e01c949a3800427678b95edf98953e635 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestBytesAndUOMConverter.java
>  PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> 784dc96c314ca9cde3685b0d8360f9b0d73b77cb 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLastParameterValueExtractor.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/68737/diff/3/
> 
> 
> Testing
> ---
> 
> New test cases / classes added:
> 
> * `TestJavaActionExecutor`
> * `TestBytesAndUOMConverter`
> * `TestLastParameterValueExtractor`
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Commented] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619088#comment-16619088
 ] 

Hadoop QA commented on OOZIE-3307:
--

PreCommit-OOZIE-Build started


> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch, 
> OOZIE-3307.003.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619079#comment-16619079
 ] 

Andras Piros commented on OOZIE-3307:
-

Thanks for the review [~gezapeti]! Uploaded a new patch that doesn't contain 
unrelated {{pom.xml}} changes.

> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch, 
> OOZIE-3307.003.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3307:

Attachment: OOZIE-3307.003.patch

> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch, 
> OOZIE-3307.003.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 68737: OOZIE-3307 [core][oya] Limit heap usage of LauncherAM

[András Piros via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68737/
---

(Updated Sept. 18, 2018, 1:06 p.m.)


Review request for oozie and Peter Bacsko.


Repository: oozie-git


Description
---

OOZIE-3307 [core][oya] Limit heap usage of LauncherAM


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
0385c77b4c01a3ec7ee9147b2369db5b1548ad80 
  core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
ada7005e01c949a3800427678b95edf98953e635 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestBytesAndUOMConverter.java 
PRE-CREATION 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
784dc96c314ca9cde3685b0d8360f9b0d73b77cb 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLastParameterValueExtractor.java
 PRE-CREATION 


Diff: https://reviews.apache.org/r/68737/diff/3/

Changes: https://reviews.apache.org/r/68737/diff/2-3/


Testing
---

New test cases / classes added:

* `TestJavaActionExecutor`
* `TestBytesAndUOMConverter`
* `TestLastParameterValueExtractor`


Thanks,

András Piros

[jira] [Commented] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619066#comment-16619066
 ] 

Andras Piros commented on OOZIE-3120:
-

[~dionusos] the RAT warning on {{master}} is because of OOZIE-2734, amendment 
patch is available.

If you know why there are test errors related {{ConnectException}}, please feel 
free to create a JIRA / patch :) Even just creating a subtask of OOZIE-3111 
would suffice.

> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-3120-001.patch
>
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on 
> project oozie-main: No formats specified in the execution parameters or the 
> assembly descriptor. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> ERROR, Oozie distro creation failed
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2734) [docs] Switch from TWiki to Markdown

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619062#comment-16619062
 ] 

Hadoop QA commented on OOZIE-2734:
--

PreCommit-OOZIE-Build started


> [docs] Switch from TWiki to Markdown
> 
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-10.patch, 
> OOZIE-2734-2.patch, OOZIE-2734-3.patch, OOZIE-2734-4.patch, 
> OOZIE-2734-5.patch, OOZIE-2734-6.patch, OOZIE-2734-7.patch, 
> OOZIE-2734-8.patch, OOZIE-2734-9.patch, OOZIE-2734-amend-11.patch, 
> OOZIE-2734.amend.002.patch, oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, 
> oozie_generated_html_markdown_20180912.zip, 
> oozie_generated_html_markdown_20180913.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-2734) [docs] Switch from TWiki to Markdown

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-2734:

Attachment: OOZIE-2734.amend.002.patch

> [docs] Switch from TWiki to Markdown
> 
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-10.patch, 
> OOZIE-2734-2.patch, OOZIE-2734-3.patch, OOZIE-2734-4.patch, 
> OOZIE-2734-5.patch, OOZIE-2734-6.patch, OOZIE-2734-7.patch, 
> OOZIE-2734-8.patch, OOZIE-2734-9.patch, OOZIE-2734-amend-11.patch, 
> OOZIE-2734.amend.002.patch, oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, 
> oozie_generated_html_markdown_20180912.zip, 
> oozie_generated_html_markdown_20180913.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (OOZIE-2734) [docs] Switch from TWiki to Markdown

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros reopened OOZIE-2734:
-
  Assignee: Andras Piros  (was: Andras Salamon)

Current {{master}} doesn't recognize {{README.md}} as an exclude for RAT 
checks, hence a RAT warning.

> [docs] Switch from TWiki to Markdown
> 
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-10.patch, 
> OOZIE-2734-2.patch, OOZIE-2734-3.patch, OOZIE-2734-4.patch, 
> OOZIE-2734-5.patch, OOZIE-2734-6.patch, OOZIE-2734-7.patch, 
> OOZIE-2734-8.patch, OOZIE-2734-9.patch, OOZIE-2734-amend-11.patch, 
> oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, 
> oozie_generated_html_markdown_20180912.zip, 
> oozie_generated_html_markdown_20180913.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619016#comment-16619016
 ] 

Hadoop QA commented on OOZIE-3343:
--

PreCommit-OOZIE-Build started


> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3346) fix git example

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619015#comment-16619015
 ] 

Hadoop QA commented on OOZIE-3346:
--

PreCommit-OOZIE-Build started


> fix git example
> ---
>
> Key: OOZIE-3346
> URL: https://issues.apache.org/jira/browse/OOZIE-3346
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3346-1.patch
>
>
> The git action example is not working, it gives E0701 error code:
> {noformat}
> $ bin/oozie job -oozie http://localhost:11000/oozie -config 
> examples/src/main/apps/git/job.properties -run 
> -DnameNode=hdfs://localhost:9000 -D jobTracker=localhost:8032
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.c: The matching 
> wildcard is strict, but no declaration can be found for element 'git'.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3342) Missing examples archive from fluentjob examples

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618999#comment-16618999
 ] 

Hadoop QA commented on OOZIE-3342:
--

PreCommit-OOZIE-Build started


> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
> not found
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
> org.apache.oozie.example.DemoJavaMain not found{noformat}
>  
> The examples should be modified to allow the user to specify the path of an 
> archive which contains the necessary files.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3307 PreCommit Build #827

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3307
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/827/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 9.50 MB...]
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive2].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[ERROR] There are [1] new bugs found below threshold in total that must be 
fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2964 bytes
[TRACE] Full summary file size is 1848 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3307

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 4 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
-1 There are [1] new bugs found below threshold in total that must be fixed.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 -1 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:
 At JavaActionExecutor.java:[line 2068]: The regular expression 
"^.*([\\s]*\\-Xmx[\\:]?([0-9]+[kKmMgG]?)[\\s]*)+.*$" is vulnerable to a denial 
of service attack (ReDOS)
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [webapp].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
There were errors during execution. Check console output for details.
Tests failed at first run:
TestWorkflowRetries>TestWorkflow#testWorkflowWithStartAndEndCompletesSuccessfully
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/827/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  41450   201  100  3944487   9564 --:--:-- --:--:-- --:--:--  9572
{"errorMessages":["Unexpected character ('^' (code 94)): was expecting comma to 
separate OBJECT entries\n at [Source: 
org.apache.catalina.connector.CoyoteInputStream@6375d14f; line: 1, column: 
1879]"]}
test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3307
Archiving artifacts

[jira] [Commented] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618982#comment-16618982
 ] 

Peter Cseh commented on OOZIE-3307:
---

Taking a quick look on the patch it looks like a fine improvement. +1 (pending 
jenkins) on it.
There are some changes in the root pom.xml which are seemingly unrelated to 
this issue. Maybe they are leftovers from an other patch you're working on. 
Please remove them before commit, but don't wait for an other Jenkins build for 
it.

> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618983#comment-16618983
 ] 

Peter Cseh commented on OOZIE-3307:
---

Taking a quick look on the patch it looks like a fine improvement. +1 (pending 
jenkins) on it.
There are some changes in the root pom.xml which are seemingly unrelated to 
this issue. Maybe they are leftovers from an other patch you're working on. 
Please remove them before commit, but don't wait for an other Jenkins build for 
it.

> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Peter Cseh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Cseh updated OOZIE-3307:
--
Comment: was deleted

(was: Taking a quick look on the patch it looks like a fine improvement. +1 
(pending jenkins) on it.
There are some changes in the root pom.xml which are seemingly unrelated to 
this issue. Maybe they are leftovers from an other patch you're working on. 
Please remove them before commit, but don't wait for an other Jenkins build for 
it.)

> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OOZIE-3348) [Hive action] Remove dependency hive-contrib

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros reassigned OOZIE-3348:
---

Assignee: Andras Piros

> [Hive action] Remove dependency hive-contrib
> 
>
> Key: OOZIE-3348
> URL: https://issues.apache.org/jira/browse/OOZIE-3348
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.2.0
>
>
> As per HIVE-20020 the dependency {{org.apache.hive:hive-contrib}} is packaged 
> differently - moved out of under Hive's lib.
> {{oozie-sharelib-hive}} exports some of the Hive dependencies, and that 
> includes {{hive-contrib.jar}}. In order to be synced with Hive we should 
> remove it too.
> Oozie doesn't depend on this jar runtime so there's no use of it being in 
> {{oozie-sharelib-hive}} anyway.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3348) [Hive action] Remove dependency hive-contrib

[Andras Piros (JIRA)]

Andras Piros created OOZIE-3348:
---

 Summary: [Hive action] Remove dependency hive-contrib
 Key: OOZIE-3348
 URL: https://issues.apache.org/jira/browse/OOZIE-3348
 Project: Oozie
  Issue Type: Improvement
  Components: action
Affects Versions: 5.0.0
Reporter: Andras Piros
 Fix For: 5.2.0


As per HIVE-20020 the dependency {{org.apache.hive:hive-contrib}} is packaged 
differently - moved out of under Hive's lib.

{{oozie-sharelib-hive}} exports some of the Hive dependencies, and that 
includes {{hive-contrib.jar}}. In order to be synced with Hive we should remove 
it too.

Oozie doesn't depend on this jar runtime so there's no use of it being in 
{{oozie-sharelib-hive}} anyway.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3347) fix fluentjob Global example

[Andras Salamon (JIRA)]

Andras Salamon created OOZIE-3347:
-

 Summary: fix fluentjob Global example
 Key: OOZIE-3347
 URL: https://issues.apache.org/jira/browse/OOZIE-3347
 Project: Oozie
  Issue Type: Improvement
  Components: fluent-job
Affects Versions: trunk
Reporter: Andras Salamon


The fluentjob Global example is not working. It generates the following {{XML}} 
file:

{noformat}



${resourceManager}
${nameNode}

1024
1
http://www.w3.org/2001/XMLSchema-instance; xsi:nil="true"/>
http://www.w3.org/2001/XMLSchema-instance; xsi:nil="true"/>
http://www.w3.org/2001/XMLSchema-instance; xsi:nil="true"/>
http://www.w3.org/2001/XMLSchema-instance; xsi:nil="true"/>

job.xml


key1
value1





Action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]



{noformat}

Checking the XML using {{-validatejar}} gives the following error:

{noformat}Error: E0701 : E0701: XML schema error, 
/var/folders/1c/dqsz948s2xq625h45d313yswgp/T/workflow6183755144852401125.xml,
 org.xml.sax.SAXParseException; lineNumber: 9; columnNumber: 99; cvc-elt.3.1: 
Attribute 'http://www.w3.org/2001/XMLSchema-instance,nil' must not appear on 
element 'workflow:queue', because the {nillable} property of 'workflow:queue' 
is false
{noformat}

The example looks unfinished to me.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Julia Kinga Marton (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julia Kinga Marton updated OOZIE-3343:
--
Attachment: (was: OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch)

> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3342) Missing examples archive from fluentjob examples

[Andras Salamon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Salamon updated OOZIE-3342:
--
Attachment: OOZIE-3342-2.patch

> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
> not found
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
> org.apache.oozie.example.DemoJavaMain not found{noformat}
>  
> The examples should be modified to allow the user to specify the path of an 
> archive which contains the necessary files.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3342) Missing examples archive from fluentjob examples

[Andras Salamon (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618867#comment-16618867
 ] 

Andras Salamon commented on OOZIE-3342:
---

The spark fluentjob example had a similar problem, the second patch also fixes 
that.

> Missing examples archive from fluentjob examples
> 
>
> Key: OOZIE-3342
> URL: https://issues.apache.org/jira/browse/OOZIE-3342
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3342-1.patch, OOZIE-3342-2.patch
>
>
> When {{-runjar}} option is used to execute a fluentjob example, oozie sets 
> the app path to a newly created (timestamped) directory and copies the 
> freshly generated {{workflow.xml}} file to this directory:
> {noformat}
> /user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
> This directory does not contain any other {{jar}} file, hence some of the 
> examples are not working. 
> For instance the 
> [JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
>  example cannot find the DemoJavaMain class:
> {noformat}
> 180910095203189-oozie-andr-W] 
> ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
> java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
> not found
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
> org.apache.oozie.example.DemoJavaMain not found{noformat}
>  
> The examples should be modified to allow the user to specify the path of an 
> archive which contains the necessary files.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618816#comment-16618816
 ] 

Hadoop QA commented on OOZIE-3307:
--

PreCommit-OOZIE-Build started


> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3229) Improved filtering options in V2SLAServlet

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618815#comment-16618815
 ] 

Hadoop QA commented on OOZIE-3229:
--


Testing JIRA OOZIE-3229

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 3 line(s) longer than 132 
characters
.{color:green}+1{color} the patch adds/modifies 6 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
.{color:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [examples].
. {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 
[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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [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:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{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/826/



> Improved filtering options in V2SLAServlet
> --
>
> Key: OOZIE-3229
> URL: https://issues.apache.org/jira/browse/OOZIE-3229
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Andras Piros
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3229-1.patch, OOZIE-3229-2.patch, 
> OOZIE-3229-3.patch, OOZIE-3229-4.patch, OOZIE-3229-5.patch, 
> OOZIE-3229-6.patch, OOZIE-3229-7.patch, OOZIE-3229-8.patch
>
>
> Currently we can apply a range of filters on top of {{V2SLAServlet}} that can 
> be used in a rich but undocumented set of ways:
> * {{id}}
> * {{parent_id}}
> * {{event_status}}
> * {{app_name}}
> * {{nominal_start}}
> * {{nominal_end}}
> Need to refactor {{V2SLAServlet}} to feature:
> * a richer set of {{SLAEvent}}, {{SLARegistration}}, and {{SLASummary}} 
> filtering based on their attributes
> * filter options will always be {{AND}}-ed, never {{OR}}-ed to each other
> * maintain compatibility with the parameter names and behavior used thus far
> * remove {{SLASummaryFilter}} and refactor 
> {{SLASummaryGetForFilterJPAExecutor}} as just another possibility for 
> confusion
> * 

Failed: OOZIE-3229 PreCommit Build #826

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3229
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/826/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 6.58 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/git].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[WARN] There are [1] new bugs found in total that would be nice to have fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2715 bytes
[TRACE] Full summary file size is 1601 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3229

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 3 line(s) longer than 132 characters
+1 the patch adds/modifies 6 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
0 There are [1] new bugs found in total that would be nice to have fixed.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 0 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
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
There were errors during execution. Check console output for details.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/826/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  34830 0  100  3483  0   3400  0:00:01  0:00:01 --:--:--  

Re: Review Request 68140: OOZIE-3229 Improved filtering options in V2SLAServlet

[András Piros via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68140/#review208701
---



Great work thus far! Only a couple of thingies left.


core/src/main/java/org/apache/oozie/FilterParser.java
Lines 44-45 (patched)


What about using Guava's 
[SortedSetMultimap](https://google.github.io/guava/releases/21.0/api/docs/com/google/common/collect/SortedSetMultimap.html)
 instead?



core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
Lines 101-108 (patched)


Would need a short example of a bundle ID here, to better see what's this 
regexp all about.



core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
Lines 68-75 (original), 123-130 (patched)


Any ideas of better names here? The format `*START_START` and `*END_END` 
isn't easily understandable.



core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
Line 115 (original), 202 (patched)


Should be `static class` if possible.



core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
Line 116 (original), 203 (patched)


`LinkedHashMap` would be a better choice, for maintaining the insertion 
order.



core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
Lines 268 (patched)


Why not use `SLASummaryGetForFilterJPAExecutor.class.getSimpleName()` 
instead?



core/src/test/java/org/apache/oozie/TestFilterParser.java
Lines 32 (patched)


Why not use `@Test` annotations and not `extends TestCase` instead?



core/src/test/java/org/apache/oozie/TestFilterParser.java
Lines 83-86 (patched)


This stuff would be also simpler using Guava's `OrderedSetMultimap`.



core/src/test/java/org/apache/oozie/TestFilterParser.java
Lines 91-96 (patched)


This stuff would be also simpler using Guava's `OrderedSetMultimap`.



core/src/test/java/org/apache/oozie/TestFilterParser.java
Lines 101-104 (patched)


This stuff would be also simpler using Guava's `OrderedSetMultimap`.



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 58-60 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 69-71 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 80-82 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 90-92 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 136-138 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 147-149 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 193-195 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 207-209 (patched)


Is it still needed as we use `ExpectedException`?



core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
Lines 221-223 (patched)


Is it still needed as we use `ExpectedException`?

[jira] [Created] (OOZIE-3346) fix git example

[Andras Salamon (JIRA)]

Andras Salamon created OOZIE-3346:
-

 Summary: fix git example
 Key: OOZIE-3346
 URL: https://issues.apache.org/jira/browse/OOZIE-3346
 Project: Oozie
  Issue Type: Improvement
Affects Versions: trunk
Reporter: Andras Salamon
Assignee: Andras Salamon
 Fix For: 5.1.0


The git action example is not working, it gives E0701 error code:
{noformat}
$ bin/oozie job -oozie http://localhost:11000/oozie -config 
examples/src/main/apps/git/job.properties -run -DnameNode=hdfs://localhost:9000 
-D jobTracker=localhost:8032
Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.c: The matching 
wildcard is strict, but no declaration can be found for element 'git'.
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

[Denes Bodo (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618752#comment-16618752
 ] 

Denes Bodo edited comment on OOZIE-3120 at 9/18/18 9:21 AM:


PreCommit build has error:
{code:java}
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check 
(default-cli) on project oozie-main: Too many files with unapproved license: 1 
See RAT report in: 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/target/rat.txt 
- [Help 1]{code}
And several test errors due to {code}java.net.ConnectException: Connection 
refused{code}


was (Author: dionusos):
PreCommit build has error:

{code}
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check 
(default-cli) on project oozie-main: Too many files with unapproved license: 1 
See RAT report in: 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/target/rat.txt 
- [Help 1]
{code}

> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-3120-001.patch
>
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on 
> project oozie-main: No formats specified in the execution parameters or the 
> assembly descriptor. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> ERROR, Oozie distro creation failed
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

[Denes Bodo (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618752#comment-16618752
 ] 

Denes Bodo commented on OOZIE-3120:
---

PreCommit build has error:

{code}
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.12:check 
(default-cli) on project oozie-main: Too many files with unapproved license: 1 
See RAT report in: 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/target/rat.txt 
- [Help 1]
{code}

> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-3120-001.patch
>
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on 
> project oozie-main: No formats specified in the execution parameters or the 
> assembly descriptor. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> ERROR, Oozie distro creation failed
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 68737: OOZIE-3307 [core][oya] Limit heap usage of LauncherAM

[András Piros via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68737/
---

(Updated Sept. 18, 2018, 8:20 a.m.)


Review request for oozie and Peter Bacsko.


Changes
---

Addressed pre-commit issues:

* `FINDBUGS_DIFF` error because of complex regexp
* `RAT` errors on `HEAD` because of incorrect settings


Repository: oozie-git


Description
---

OOZIE-3307 [core][oya] Limit heap usage of LauncherAM


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
0385c77b4c01a3ec7ee9147b2369db5b1548ad80 
  core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
ada7005e01c949a3800427678b95edf98953e635 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestBytesAndUOMConverter.java 
PRE-CREATION 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
784dc96c314ca9cde3685b0d8360f9b0d73b77cb 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLastParameterValueExtractor.java
 PRE-CREATION 
  pom.xml d6440e44315c6bb114ac57ebd7081511fa5faf43 


Diff: https://reviews.apache.org/r/68737/diff/2/

Changes: https://reviews.apache.org/r/68737/diff/1-2/


Testing
---

New test cases / classes added:

* `TestJavaActionExecutor`
* `TestBytesAndUOMConverter`
* `TestLastParameterValueExtractor`


Thanks,

András Piros

[jira] [Commented] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618680#comment-16618680
 ] 

Andras Piros commented on OOZIE-3307:
-

Addressed pre-commit issues:
* {{FINDBUGS_DIFF}} error because of complex regexp
* {{RAT}} errors on {{HEAD}} because of incorrect settings

> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3307) [core][oya] Limit heap usage of LauncherAM

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3307:

Attachment: OOZIE-3307.002.patch

> [core][oya] Limit heap usage of LauncherAM
> --
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0
>Reporter: Sabir Naikwadi
>Assignee: Andras Piros
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch
>
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_02 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_01] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_01 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_01
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 68140: OOZIE-3229 Improved filtering options in V2SLAServlet

[Andras Salamon]

> On Sept. 4, 2018, 12:25 p.m., András Piros wrote:
> > core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
> > Lines 218 (patched)
> > 
> >
> > Always `ORDER BY NOMINAL_TIME`?

Added sortby and order parameters similar to job filter. To avoid undefined 
ordering I always add a second order by nominal_time. I'm not sure about this.


> On Sept. 4, 2018, 12:25 p.m., András Piros wrote:
> > core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
> > Lines 228-239 (patched)
> > 
> >
> > I'm thinking whether `fieldName LIKE '%fieldValue%'` can / should be 
> > supported.

Added support for like. I'm not sure if % and _ is suitable for the users. 
Maybe we should allow only * (and convert it to %) instead.


> On Sept. 4, 2018, 12:25 p.m., András Piros wrote:
> > core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
> > Lines 296-354 (patched)
> > 
> >
> > Isn't it possible to use the Visitor design pattern instead? Or, at the 
> > very least, extract the `case` contents to well named methods?

Create an enum based strategy like solution.


> On Sept. 4, 2018, 12:25 p.m., András Piros wrote:
> > core/src/test/java/org/apache/oozie/servlet/TestV2SLAServletRun.java
> > Lines 30 (patched)
> > 
> >
> > `TestIntegrationV2SLAServlet` might be a better name

Using TestV2SLAServletIntegration instead, to keep it similar to the other test 
class names.


> On Sept. 4, 2018, 12:25 p.m., András Piros wrote:
> > core/src/test/java/org/apache/oozie/servlet/V2SLAServletTestCase.java
> > Lines 38 (patched)
> > 
> >
> > I'm wondering why we have to `extends XDataTestCase` and why this class 
> > has to be extended instead of being a composite in the caller class.

We need createBundleJob method for instance.

I created two classes because half of the methods were using one type of setup 
method, the other half was using a different type of setup method.


> On Sept. 4, 2018, 12:25 p.m., András Piros wrote:
> > core/src/test/java/org/apache/oozie/servlet/V2SLAServletTestCase.java
> > Lines 45-46 (patched)
> > 
> >
> > Sure it isn't handled by ancestors?

Yes, I've tested without this.


- Andras


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68140/#review208294
---


On Sept. 18, 2018, 7:46 a.m., Andras Salamon wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68140/
> ---
> 
> (Updated Sept. 18, 2018, 7:46 a.m.)
> 
> 
> Review request for oozie, András Piros and Kinga Marton.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Added lots of new filter fields, also refactored 
> SLASummaryGetForFilterJPAExecutor class to eliminate FindBugs errors. I'm not 
> sure about the filter field names.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/client/OozieClient.java 949b4532f 
>   client/src/main/java/org/apache/oozie/client/rest/RestConstants.java 
> 9873ff3ad 
>   core/src/main/java/org/apache/oozie/FilterParser.java PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
>  b54161e98 
>   core/src/main/java/org/apache/oozie/servlet/V2SLAServlet.java 3982d1e06 
>   core/src/test/java/org/apache/oozie/TestFilterParser.java PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
>  PRE-CREATION 
>   core/src/test/java/org/apache/oozie/servlet/TestV2SLAServlet.java aa633225b 
>   core/src/test/java/org/apache/oozie/servlet/TestV2SLAServletBundle.java 
> PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/servlet/TestV2SLAServletIntegration.java 
> PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/servlet/TestV2SLAServletSLAJSONResponse.java
>  PRE-CREATION 
>   core/src/test/java/org/apache/oozie/servlet/V2SLAServletTestCase.java 
> PRE-CREATION 
>   docs/src/site/markdown/DG_SLAMonitoring.md 0831b93bd 
>   webapp/src/main/webapp/console/sla/css/oozie-sla.css d2f2deeec 
>   webapp/src/main/webapp/console/sla/js/oozie-sla.js 2ecad228a 
>   webapp/src/main/webapp/console/sla/oozie-sla.html e5bf6275a 
> 
> 
> Diff: 

[jira] [Commented] (OOZIE-3345) forkjoin validation error when multiple(>=3) actions with "ok to""error to" same action

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618641#comment-16618641
 ] 

Andras Piros commented on OOZIE-3345:
-

Thanks for the reproduction case [~Dr.hahaha]!

> forkjoin validation error when multiple(>=3) actions with "ok to""error to" 
> same action
> ---
>
> Key: OOZIE-3345
> URL: https://issues.apache.org/jira/browse/OOZIE-3345
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: wang jinyin
>Priority: Major
> Fix For: 5.2.0
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> when multiple (n >= 3) actions with "ok to" "error to" transition to same 
> action, forkjoin validation will throw WorkflowException(ErrorCode.E0743)
> {quote}org.apache.oozie.workflow.WorkflowException: E0743: Multiple "ok to" 
> transitions to the same node, [C], are not allowed
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:186)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:267)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:271)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:275)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateWorkflow(LiteWorkflowValidator.java:62)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowAppParser.validateAndParse(LiteWorkflowAppParser.java:185)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowLib.parseDef(LiteWorkflowLib.java:58)
>  at 
> org.apache.oozie.service.LiteWorkflowAppService.parseDef(LiteWorkflowAppService.java:57)
>  at 
> org.apache.oozie.service.LiteWorkflowAppService.parseDef(LiteWorkflowAppService.java:46)
>  at 
> org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:167)
> {quote}
>  
> workflow definition:
> {quote}
>     
>     
> 
> 
>     
>     
> 
> 
>     
>     
> 
> {quote}
>  
> [reason]
> When validate A's "ok to" path -> B's "ok to" path, action node C has already 
> been added into nodeAndDecisionParents.
> When validate A's "error to" path -> B's "ok to" path, C's decisionParent == 
> null and topDecisionParent == null. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3345) forkjoin validation error when multiple(>=3) actions with "ok to""error to" same action

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-3345:

Fix Version/s: 5.2.0

> forkjoin validation error when multiple(>=3) actions with "ok to""error to" 
> same action
> ---
>
> Key: OOZIE-3345
> URL: https://issues.apache.org/jira/browse/OOZIE-3345
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: wang jinyin
>Priority: Major
> Fix For: 5.2.0
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> when multiple (n >= 3) actions with "ok to" "error to" transition to same 
> action, forkjoin validation will throw WorkflowException(ErrorCode.E0743)
> {quote}org.apache.oozie.workflow.WorkflowException: E0743: Multiple "ok to" 
> transitions to the same node, [C], are not allowed
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:186)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:267)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:271)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateForkJoin(LiteWorkflowValidator.java:275)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowValidator.validateWorkflow(LiteWorkflowValidator.java:62)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowAppParser.validateAndParse(LiteWorkflowAppParser.java:185)
>  at 
> org.apache.oozie.workflow.lite.LiteWorkflowLib.parseDef(LiteWorkflowLib.java:58)
>  at 
> org.apache.oozie.service.LiteWorkflowAppService.parseDef(LiteWorkflowAppService.java:57)
>  at 
> org.apache.oozie.service.LiteWorkflowAppService.parseDef(LiteWorkflowAppService.java:46)
>  at 
> org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:167)
> {quote}
>  
> workflow definition:
> {quote}
>     
>     
> 
> 
>     
>     
> 
> 
>     
>     
> 
> {quote}
>  
> [reason]
> When validate A's "ok to" path -> B's "ok to" path, action node C has already 
> been added into nodeAndDecisionParents.
> When validate A's "error to" path -> B's "ok to" path, C's decisionParent == 
> null and topDecisionParent == null. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 68140: OOZIE-3229 Improved filtering options in V2SLAServlet

[Andras Salamon]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68140/
---

(Updated Sept. 18, 2018, 7:46 a.m.)


Review request for oozie, András Piros and Kinga Marton.


Repository: oozie-git


Description
---

Added lots of new filter fields, also refactored 
SLASummaryGetForFilterJPAExecutor class to eliminate FindBugs errors. I'm not 
sure about the filter field names.


Diffs (updated)
-

  client/src/main/java/org/apache/oozie/client/OozieClient.java 949b4532f 
  client/src/main/java/org/apache/oozie/client/rest/RestConstants.java 
9873ff3ad 
  core/src/main/java/org/apache/oozie/FilterParser.java PRE-CREATION 
  
core/src/main/java/org/apache/oozie/executor/jpa/sla/SLASummaryGetForFilterJPAExecutor.java
 b54161e98 
  core/src/main/java/org/apache/oozie/servlet/V2SLAServlet.java 3982d1e06 
  core/src/test/java/org/apache/oozie/TestFilterParser.java PRE-CREATION 
  
core/src/test/java/org/apache/oozie/executor/jpa/sla/TestSLASummaryGetForFilterJPAExecutorFilterCollection.java
 PRE-CREATION 
  core/src/test/java/org/apache/oozie/servlet/TestV2SLAServlet.java aa633225b 
  core/src/test/java/org/apache/oozie/servlet/TestV2SLAServletBundle.java 
PRE-CREATION 
  core/src/test/java/org/apache/oozie/servlet/TestV2SLAServletIntegration.java 
PRE-CREATION 
  
core/src/test/java/org/apache/oozie/servlet/TestV2SLAServletSLAJSONResponse.java
 PRE-CREATION 
  core/src/test/java/org/apache/oozie/servlet/V2SLAServletTestCase.java 
PRE-CREATION 
  docs/src/site/markdown/DG_SLAMonitoring.md 0831b93bd 
  webapp/src/main/webapp/console/sla/css/oozie-sla.css d2f2deeec 
  webapp/src/main/webapp/console/sla/js/oozie-sla.js 2ecad228a 
  webapp/src/main/webapp/console/sla/oozie-sla.html e5bf6275a 


Diff: https://reviews.apache.org/r/68140/diff/6/

Changes: https://reviews.apache.org/r/68140/diff/5-6/


Testing
---


Thanks,

Andras Salamon

[jira] [Commented] (OOZIE-3229) Improved filtering options in V2SLAServlet

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618617#comment-16618617
 ] 

Hadoop QA commented on OOZIE-3229:
--

PreCommit-OOZIE-Build started


> Improved filtering options in V2SLAServlet
> --
>
> Key: OOZIE-3229
> URL: https://issues.apache.org/jira/browse/OOZIE-3229
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Andras Piros
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3229-1.patch, OOZIE-3229-2.patch, 
> OOZIE-3229-3.patch, OOZIE-3229-4.patch, OOZIE-3229-5.patch, 
> OOZIE-3229-6.patch, OOZIE-3229-7.patch, OOZIE-3229-8.patch
>
>
> Currently we can apply a range of filters on top of {{V2SLAServlet}} that can 
> be used in a rich but undocumented set of ways:
> * {{id}}
> * {{parent_id}}
> * {{event_status}}
> * {{app_name}}
> * {{nominal_start}}
> * {{nominal_end}}
> Need to refactor {{V2SLAServlet}} to feature:
> * a richer set of {{SLAEvent}}, {{SLARegistration}}, and {{SLASummary}} 
> filtering based on their attributes
> * filter options will always be {{AND}}-ed, never {{OR}}-ed to each other
> * maintain compatibility with the parameter names and behavior used thus far
> * remove {{SLASummaryFilter}} and refactor 
> {{SLASummaryGetForFilterJPAExecutor}} as just another possibility for 
> confusion
> * document new functionality with rich use case / example library so that 
> users can leverage



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618616#comment-16618616
 ] 

Hadoop QA commented on OOZIE-3343:
--


Testing JIRA OOZIE-3343

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: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:red}WARNING: the current HEAD has 1 RAT warning(s), they should be 
addressed ASAP{color}
{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:orange}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 [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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 
[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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [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 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/825/



> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch, 
> OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Failed: OOZIE-3343 PreCommit Build #825

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/OOZIE-3343
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/825/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.69 MB...]
[DEBUG] There are no new bugs found in [sharelib/hcatalog].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/git].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/distcp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2588 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
bin/test-patch-20-tests: line 198: syntax error near unexpected token `else'
bin/test-patch-20-tests: line 198: `else'
  Running test-patch task DISTRO


Testing JIRA OOZIE-3343

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 2 line(s) longer than 132 characters
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
WARNING: the current HEAD has 1 RAT warning(s), they should be addressed 
ASAP
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/825/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32560 0  100  3256  0   3114  0:00:01  0:00:01 --:--:--  

[jira] [Updated] (OOZIE-3229) Improved filtering options in V2SLAServlet

[Andras Salamon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Salamon updated OOZIE-3229:
--
Attachment: OOZIE-3229-8.patch

> Improved filtering options in V2SLAServlet
> --
>
> Key: OOZIE-3229
> URL: https://issues.apache.org/jira/browse/OOZIE-3229
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Andras Piros
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3229-1.patch, OOZIE-3229-2.patch, 
> OOZIE-3229-3.patch, OOZIE-3229-4.patch, OOZIE-3229-5.patch, 
> OOZIE-3229-6.patch, OOZIE-3229-7.patch, OOZIE-3229-8.patch
>
>
> Currently we can apply a range of filters on top of {{V2SLAServlet}} that can 
> be used in a rich but undocumented set of ways:
> * {{id}}
> * {{parent_id}}
> * {{event_status}}
> * {{app_name}}
> * {{nominal_start}}
> * {{nominal_end}}
> Need to refactor {{V2SLAServlet}} to feature:
> * a richer set of {{SLAEvent}}, {{SLARegistration}}, and {{SLASummary}} 
> filtering based on their attributes
> * filter options will always be {{AND}}-ed, never {{OR}}-ed to each other
> * maintain compatibility with the parameter names and behavior used thus far
> * remove {{SLASummaryFilter}} and refactor 
> {{SLASummaryGetForFilterJPAExecutor}} as just another possibility for 
> confusion
> * document new functionality with rich use case / example library so that 
> users can leverage



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618597#comment-16618597
 ] 

Hadoop QA commented on OOZIE-3343:
--

PreCommit-OOZIE-Build started


> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch, 
> OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618594#comment-16618594
 ] 

Hadoop QA commented on OOZIE-3343:
--

PreCommit-OOZIE-Build started


> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch, 
> OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3343) [build] Add the first x errors per module in case of junit errors to the precommit report

[Julia Kinga Marton (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julia Kinga Marton updated OOZIE-3343:
--
Attachment: OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch

> [build] Add the first x errors per module in case of junit errors to the 
> precommit report
> -
>
> Key: OOZIE-3343
> URL: https://issues.apache.org/jira/browse/OOZIE-3343
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-3343-001.patch, 
> OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch
>
>
> After fixing the false positive precommit reports in OOZIE-3317, if there are 
> some kind of errors during junit execution, the following information is 
> printed out: 
> {color:#FF}-1 TESTS{color}
> There were errors during execution. Check console output for details.
> It should be useful to have the concrete errors printed out as well. In order 
> to avoid the very long reports in case of lots of failures, we should limit 
> the printed out errors to a specific number (5)/module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3317) [build] Fix false positive precommit reports

[Julia Kinga Marton (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julia Kinga Marton updated OOZIE-3317:
--
Attachment: OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch

> [build] Fix false positive precommit reports
> 
>
> Key: OOZIE-3317
> URL: https://issues.apache.org/jira/browse/OOZIE-3317
> Project: Oozie
>  Issue Type: Sub-task
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3317-001.patch, OOZIE-3317-002.patch, 
> OOZIE-3317-003.patch, OOZIE-3317-DO_NOT_MERGE.patch, 
> OOZIE-3317-DO_NOT_MERGE2.patch, OOZIE-3317-TESTING.patch, 
> OOZIE-3317-amend001.patch, consoleFull.txt
>
>
> Some steps of the current precommit are failing but we get a +1 anyways ( see 
> OOZIE-3304 for a recent example)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3317) [build] Fix false positive precommit reports

[Julia Kinga Marton (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julia Kinga Marton updated OOZIE-3317:
--
Attachment: (was: OOZIE-3343-DEBUG_PURPOSE_DO_NOT_MERGE.patch)

> [build] Fix false positive precommit reports
> 
>
> Key: OOZIE-3317
> URL: https://issues.apache.org/jira/browse/OOZIE-3317
> Project: Oozie
>  Issue Type: Sub-task
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3317-001.patch, OOZIE-3317-002.patch, 
> OOZIE-3317-003.patch, OOZIE-3317-DO_NOT_MERGE.patch, 
> OOZIE-3317-DO_NOT_MERGE2.patch, OOZIE-3317-TESTING.patch, 
> OOZIE-3317-amend001.patch, consoleFull.txt
>
>
> Some steps of the current precommit are failing but we get a +1 anyways ( see 
> OOZIE-3304 for a recent example)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (92 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3343  [build] Add the first x errors per module in case of junit errors 
to the precommit report
https://issues.apache.org/jira/browse/OOZIE-3343
OOZIE-3326  Sqoop Action should support tez delegation tokens for hive-import
https://issues.apache.org/jira/browse/OOZIE-3326
OOZIE-3320  Oozie ShellAction should support absolute bash file path
https://issues.apache.org/jira/browse/OOZIE-3320
OOZIE-3319  Log SSH action callback error output
https://issues.apache.org/jira/browse/OOZIE-3319
OOZIE-3307  [core][oya] Limit heap usage of LauncherAM
https://issues.apache.org/jira/browse/OOZIE-3307
OOZIE-3301  Update NOTICE file
https://issues.apache.org/jira/browse/OOZIE-3301
OOZIE-3277  [build] Check for star imports in patches in pre-commit
https://issues.apache.org/jira/browse/OOZIE-3277
OOZIE-3274  Remove slf4j
https://issues.apache.org/jira/browse/OOZIE-3274
OOZIE-3266  Coord action rerun support RERUN_SKIP_NODES option
https://issues.apache.org/jira/browse/OOZIE-3266
OOZIE-3265  properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to 
appear together
https://issues.apache.org/jira/browse/OOZIE-3265
OOZIE-3256  refactor OozieCLI class
https://issues.apache.org/jira/browse/OOZIE-3256
OOZIE-3249  [tools] Instrumentation log parser
https://issues.apache.org/jira/browse/OOZIE-3249
OOZIE-3229  Improved filtering options in V2SLAServlet
https://issues.apache.org/jira/browse/OOZIE-3229
OOZIE-3218  Oozie Sqoop action with command splits the select clause into 
multiple parts due to delimiter being space
https://issues.apache.org/jira/browse/OOZIE-3218
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3196  Authorization: restrict world readability by user
https://issues.apache.org/jira/browse/OOZIE-3196
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3120  maven-assembly-plugin fails when bumped from 2.2.1
https://issues.apache.org/jira/browse/OOZIE-3120
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2714  Detect conflicting resources during class loading
https://issues.apache.org/jira/browse/OOZIE-2714
OOZIE-2694