[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (111 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3106  upgrade surefire-plugin to 2.20.1
https://issues.apache.org/jira/browse/OOZIE-3106
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3101  Oozie should add error message to the response body
https://issues.apache.org/jira/browse/OOZIE-3101
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
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-3083  Make improved version Info backward compatible
https://issues.apache.org/jira/browse/OOZIE-3083
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-3022  fix for warning has no file and won't be listed in dependency files 
details
https://issues.apache.org/jira/browse/OOZIE-3022
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-3001  core library has many instances of warnings with trailing spaces 
and lines longer than 132 chars
https://issues.apache.org/jira/browse/OOZIE-3001
OOZIE-2997  files contain trailing white spaces in client lib
https://issues.apache.org/jira/browse/OOZIE-2997
OOZIE-2996  add option for -UseGCOverheadLimit to maven opts as sometimes local 
testing fails
https://issues.apache.org/jira/browse/OOZIE-2996
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2969  Drop support for Java 1.7
https://issues.apache.org/jira/browse/OOZIE-2969
OOZIE-2964  Add -Xdoclint:none to javadoc opts to avoid warnings
https://issues.apache.org/jira/browse/OOZIE-2964
OOZIE-2962  bump maven-javadoc-plugin to 2.10.4
https://issues.apache.org/jira/browse/OOZIE-2962
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
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-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2897  LauncherAM should support ACLs
https://issues.apache.org/jira/browse/OOZIE-2897
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
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-2829  Improve 

[jira] [Commented] (OOZIE-3101) Oozie should add error message to the response body

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3101:
--

Testing JIRA OOZIE-3101

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 does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 77 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 [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/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 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: 2050
.Tests failed: 2
.Tests errors: 1

.The patch failed the following testcases:

.  testInvalidResource(org.apache.oozie.servlet.TestJsonRestServlet)
.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

{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/181/

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch, OOZIE-3101-4.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: OOZIE-3101 PreCommit Build #181

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.61 MB...]
 +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 [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/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 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: 2050
Tests failed: 2
Tests errors: 1

The patch failed the following testcases:

  testInvalidResource(org.apache.oozie.servlet.TestJsonRestServlet)
  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

+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/181/

  % 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
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  4004k  0 --:--:-- --:--:-- --:--:-- 9962k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3101
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 29.4% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
3 tests failed.
FAILED:  org.apache.oozie.servlet.TestJsonRestServlet.testInvalidResource

Error Message:
expected:<...nvalid resource [any[\]/any]> but was:<...nvalid resource 
[any[]/any]>

Stack Trace:
junit.framework.ComparisonFailure: expected:<...nvalid resource [any[\]/any]> 
but was:<...nvalid resource [any[]/any]>
at junit.framework.Assert.assertEquals(Assert.java:100)
at junit.framework.Assert.assertEquals(Assert.java:107)
at junit.framework.TestCase.assertEquals(TestCase.java:269)
at 
org.apache.oozie.servlet.TestJsonRestServlet$7.call(TestJsonRestServlet.java:192)
at 
org.apache.oozie.servlet.TestJsonRestServlet$7.call(TestJsonRestServlet.java:188)
at 
org.apache.oozie.servlet.TestJsonRestServlet.runTest(TestJsonRestServlet.java:97)
at 
org.apache.oozie.servlet.TestJsonRestServlet.testInvalidResource(TestJsonRestServlet.java:188)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at 

[jira] [Commented] (OOZIE-3101) Oozie should add error message to the response body

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-3101:
---

+1

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch, OOZIE-3101-4.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-3101) Oozie should add error message to the response body

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-3101:
---
Attachment: OOZIE-3101-4.patch

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch, OOZIE-3101-4.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-3101) Oozie should add error message to the response body

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3101:
--

Testing JIRA OOZIE-3101

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 does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 77 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 [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/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 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: 2050
.Tests failed: 1
.Tests errors: 1

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

{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/180/

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: OOZIE-3101 PreCommit Build #180

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.61 MB...]
+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 [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/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 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: 2050
Tests failed: 1
Tests errors: 1

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

+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/180/

  % 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
 51 3706k   51 1908k0 0  2440k  0  0:00:01 --:--:--  0:00:01 
2440k100 3706k  100 3706k0 0  4584k  0 --:--:-- --:--:-- --:--:-- 
67.5M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3101
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 29.4% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation

Error Message:
Unable to open socket file: target process not responding or HotSpot VM not 
loaded

Stack Trace:
com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: 
target process not responding or HotSpot VM not loaded
at 
sun.tools.attach.LinuxVirtualMachine.(LinuxVirtualMachine.java:106)
at 
sun.tools.attach.LinuxAttachProvider.attachVirtualMachine(LinuxAttachProvider.java:78)
at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:250)
at 
org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation(TestMetricsInstrumentation.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 

[jira] [Commented] (OOZIE-3101) Oozie should add error message to the response body

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-3101:
---

1) Do we need all three escaping - xml, javascript and html to get rid of the 
findbugs XSS vulnerability warning? OOZIE-3109 only does html escaping. If it 
is better to do all three, then we should do that in OOZIE-3109 as well.
2) The new constants should be in JsonTags instead of RestConstants and camel 
casing should be used. RestConstants is only used for query params.

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-3101) Oozie should add error message to the response body

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley updated OOZIE-3101:
---
Attachment: OOZIE-3101-3.patch

> Oozie should add error message to the response body
> ---
>
> Key: OOZIE-3101
> URL: https://issues.apache.org/jira/browse/OOZIE-3101
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3101-1.patch, OOZIE-3101-2.patch, 
> OOZIE-3101-3.patch
>
>
> For web service APIs, currently Oozie adds error message in a custom response 
> header which is parsed out by the OozieClient. Oozie should also put error 
> message in the response body so that clients like curl can display the error 
> message to users without having to turn on verbose output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OOZIE-3103) Improve log message regarding max concurrency for coordinators

[Robert Kanter (JIRA)]

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

Robert Kanter resolved OOZIE-3103.
--
   Resolution: Fixed
 Assignee: Attila Sasvari
Fix Version/s: 5.0.0b1

Thanks [~asasvari].  Committed to master!

> Improve log message regarding max concurrency for coordinators
> --
>
> Key: OOZIE-3103
> URL: https://issues.apache.org/jira/browse/OOZIE-3103
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-3103-001.patch, OOZIE-3103-002.patch
>
>
> Currently, when maximum concurrency is reached for coordinators, the log 
> message is as follows:
> {code}
> 2017-09-25 06:00:00,069 WARN 
> org.apache.oozie.command.coord.CoordActionReadyXCommand: 
> SERVER[dsfsdfsdfds.com] USER[testclu0] GROUP[-] TOKEN[] 
> APP[test->dev->xyzabc] JOB[065-191474932323346-oozie-oozi-C] ACTION[] No 
> actions to start for jobId=065-191474932323346-oozie-oozi-C as max 
> concurrency reached!
> {code}
> It's confusing as-is and sounds like something is wrong, even though it's 
> perfectly fine. 
> We should make it an INFO message and say something more specific and less 
> scary sounding (no exclamation ). Maybe something like "Not starting any 
> additional actions because max concurrency \[] for \[] has 
> been reached"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-3103) Improve log message regarding max concurrency for coordinators

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-3103:
--

+1

> Improve log message regarding max concurrency for coordinators
> --
>
> Key: OOZIE-3103
> URL: https://issues.apache.org/jira/browse/OOZIE-3103
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-3103-001.patch, OOZIE-3103-002.patch
>
>
> Currently, when maximum concurrency is reached for coordinators, the log 
> message is as follows:
> {code}
> 2017-09-25 06:00:00,069 WARN 
> org.apache.oozie.command.coord.CoordActionReadyXCommand: 
> SERVER[dsfsdfsdfds.com] USER[testclu0] GROUP[-] TOKEN[] 
> APP[test->dev->xyzabc] JOB[065-191474932323346-oozie-oozi-C] ACTION[] No 
> actions to start for jobId=065-191474932323346-oozie-oozi-C as max 
> concurrency reached!
> {code}
> It's confusing as-is and sounds like something is wrong, even though it's 
> perfectly fine. 
> We should make it an INFO message and say something more specific and less 
> scary sounding (no exclamation ). Maybe something like "Not starting any 
> additional actions because max concurrency \[] for \[] has 
> been reached"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2726) Flaky test due to daylight saving changes

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2726:
-

[~satishsaley] thanks for the contribution! Left some review comments on 
ReviewBoard.

> Flaky test due to daylight saving changes
> -
>
> Key: OOZIE-2726
> URL: https://issues.apache.org/jira/browse/OOZIE-2726
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-2726-1.patch, OOZIE-2726-2.patch, 
> OOZIE-2726-3.patch, OOZIE-2726-4.patch, OOZIE-2726-5.patch
>
>
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup
> {code}
> Error Message
> expected: but was:
> Stacktrace
> junit.framework.AssertionFailedError: expected: 
> but was:
>   at junit.framework.Assert.fail(Assert.java:50)
>   at junit.framework.Assert.failNotEquals(Assert.java:287)
>   at junit.framework.Assert.assertEquals(Assert.java:67)
>   at junit.framework.Assert.assertEquals(Assert.java:74)
>   at 
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:243)
>   at junit.framework.TestSuite.run(TestSuite.java:238)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:24)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 53775: [OOZIE-2726] Flaky test due to daylight saving changes

[András Piros via Review Board]

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




core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java
Lines 537-559 (patched)


Would extract to `DaylightOffsetCalculator` and create separate unit test 
cases.



core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java
Lines 538 (patched)


What if  both `start` and `end` are in daylight saving time? In that case, 
we don't need to change IMO, even if there were an even number of daylight 
changes in between.



core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java
Lines 597-600 (patched)


Extract method `setStartAndEndTimesToDaylight()`.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Line 336 (original), 336 (patched)


`TimeUnit.HOURS.toSeconds(4)`



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Line 341 (original), 341 (patched)


Extract `3` to a well-named local variable.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Line 347 (original), 347 (patched)


Extract `3` to a well-named local variable.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Line 372 (original), 372 (patched)


Extract `5` to a well-named local variable.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Lines 636-657 (patched)


Extract method.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Lines 639 (patched)


Extract method.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Lines 648 (patched)


`TimeUnit.HOURS.toSeconds(1)`



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Line 634 (original), 659-678 (patched)


Extract method.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Lines 661 (patched)


Extract method.



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Lines 670 (patched)


`TimeUnit.HOURS.toSeconds(1)`



core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
Line 941 (original), 985 (patched)


An explaining Javadoc why we substract would be extremely useful.


- András Piros


On Nov. 22, 2016, 1:02 a.m., Satish Saley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53775/
> ---
> 
> (Updated Nov. 22, 2016, 1:02 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2726
> https://issues.apache.org/jira/browse/OOZIE-2726
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> [OOZIE-2726] Flaky test due to daylight saving changes
> 
> 
> Diffs
> -
> 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
>  29e7ca1 
> 
> 
> Diff: https://reviews.apache.org/r/53775/diff/3/
> 
> 
> Testing
> ---
> 
> Tested locally
> 
> 
> Thanks,
> 
> Satish Saley
> 
>

[jira] [Updated] (OOZIE-3109) Escape log-streaming's HTML-specific characters

[Denes Bodo (JIRA)]

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

Denes Bodo updated OOZIE-3109:
--
Summary: Escape log-streaming's HTML-specific characters  (was: Good coding 
practice)

> Escape log-streaming's HTML-specific characters
> ---
>
> Key: OOZIE-3109
> URL: https://issues.apache.org/jira/browse/OOZIE-3109
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
> Attachments: OOZIE-3109-v001.patch
>
>
> That can be a security problem if we do not encode the stream read from log 
> files before transferred to the web browser.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-3109) Good coding practice

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3109:
-

[~dionusos] could you please rename this JIRA? The title "Good coding practice" 
is not really specific enough.

> Good coding practice
> 
>
> Key: OOZIE-3109
> URL: https://issues.apache.org/jira/browse/OOZIE-3109
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
> Attachments: OOZIE-3109-v001.patch
>
>
> That can be a security problem if we do not encode the stream read from log 
> files before transferred to the web browser.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2897) LauncherAM should support ACLs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2897:
--

Testing JIRA OOZIE-2897

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 does adds/modifies 10 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 77 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 [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/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 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: 2054
.Tests failed: 9
.Tests errors: 3

.The patch failed the following testcases:

.  testImportTablesOverflowBatchSize(org.apache.oozie.tools.TestDBLoadDump)
.  
testImportInvalidDataLeavesTablesEmpty(org.apache.oozie.tools.TestDBLoadDump)
.  
testImportToNonEmptyTablesCausesPrematureExit(org.apache.oozie.tools.TestDBLoadDump)
.  testImportedDBIsExportedCorrectly(org.apache.oozie.tools.TestDBLoadDump)
.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)
.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)

.Tests failing with errors:
.  testAddXIncludeFromReader(org.apache.oozie.util.TestXConfiguration)
.  testAddXIncludeFromStream(org.apache.oozie.util.TestXConfiguration)
.  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

{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/179/

> LauncherAM should support ACLs
> --
>
> Key: OOZIE-2897
> URL: https://issues.apache.org/jira/browse/OOZIE-2897
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2897-001.patch, OOZIE-2897-002.patch, 
> OOZIE-2897-003.patch, OOZIE-2897-004.patch, OOZIE-2897-005.patch, 
> OOZIE-2897-006.patch
>
>
> In MapReduce, you can define ACL-related properties:
> {noformat}
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modify-job
> {noformat}
> {{acl-view-job}} defines a list of users/groups who can retrieve the job 
> statistics. {{acl-modify-job}} defines a list of users/groups who 

Failed: OOZIE-2897 PreCommit Build #179

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.62 MB...]
 +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/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 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: 2054
Tests failed: 9
Tests errors: 3

The patch failed the following testcases:

  testImportTablesOverflowBatchSize(org.apache.oozie.tools.TestDBLoadDump)
  
testImportInvalidDataLeavesTablesEmpty(org.apache.oozie.tools.TestDBLoadDump)
  
testImportToNonEmptyTablesCausesPrematureExit(org.apache.oozie.tools.TestDBLoadDump)
  testImportedDBIsExportedCorrectly(org.apache.oozie.tools.TestDBLoadDump)
  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)
  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)

Tests failing with errors:
  testAddXIncludeFromReader(org.apache.oozie.util.TestXConfiguration)
  testAddXIncludeFromStream(org.apache.oozie.util.TestXConfiguration)
  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

+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/179/

  % 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
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  3540k  0  0:00:01  0:00:01 --:--:-- 4954k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2897
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 24.1% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
12 tests failed.
FAILED:  org.apache.oozie.util.TestXConfiguration.testAddXIncludeFromReader

Error Message:
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build%402/core/target/test-classes/test-oozie-default.xml
 (No such file or directory)

Stack Trace:
java.io.FileNotFoundException: 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build%402/core/target/test-classes/test-oozie-default.xml
 (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at java.io.FileInputStream.(FileInputStream.java:93)
at java.io.FileReader.(FileReader.java:58)
at 
org.apache.oozie.util.TestXConfiguration.prepareXmlWithInclude(TestXConfiguration.java:94)
at 
org.apache.oozie.util.TestXConfiguration.testAddXIncludeFromReader(TestXConfiguration.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 

Failed: OOZIE-2897 PreCommit Build #175

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.61 MB...]
+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 [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/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 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: 2054
Tests failed: 1
Tests errors: 1

The patch failed the following testcases:

  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

Tests failing with errors:
  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

+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/175/

  % 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
  0 3706k0 130320 0  22070  0  0:02:51 --:--:--  0:02:51 
22070100 3706k  100 3706k0 0  4798k  0 --:--:-- --:--:-- --:--:-- 
19.9M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2897
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 41.5% relative to #164
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation

Error Message:
Unable to open socket file: target process not responding or HotSpot VM not 
loaded

Stack Trace:
com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: 
target process not responding or HotSpot VM not loaded
at 
sun.tools.attach.LinuxVirtualMachine.(LinuxVirtualMachine.java:106)
at 
sun.tools.attach.LinuxAttachProvider.attachVirtualMachine(LinuxAttachProvider.java:78)
at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:250)
at 
org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation(TestMetricsInstrumentation.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 

[jira] [Commented] (OOZIE-2897) LauncherAM should support ACLs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2897:
--

Testing JIRA OOZIE-2897

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 does adds/modifies 10 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 77 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 [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/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 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: 2054
.Tests failed: 1
.Tests errors: 1

.The patch failed the following testcases:

.  
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)

.Tests failing with errors:
.  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

{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/175/

> LauncherAM should support ACLs
> --
>
> Key: OOZIE-2897
> URL: https://issues.apache.org/jira/browse/OOZIE-2897
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2897-001.patch, OOZIE-2897-002.patch, 
> OOZIE-2897-003.patch, OOZIE-2897-004.patch, OOZIE-2897-005.patch, 
> OOZIE-2897-006.patch
>
>
> In MapReduce, you can define ACL-related properties:
> {noformat}
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modify-job
> {noformat}
> {{acl-view-job}} defines a list of users/groups who can retrieve the job 
> statistics. {{acl-modify-job}} defines a list of users/groups who can kill a 
> job or adjust the priority of it.
> Docs: 
> https://hadoop.apache.org/docs/r1.2.1/mapred_tutorial.html#Job+Authorization
> In YARN, we can provide backward compatibility for these properties. Example 
> code:
> {code}
> Map acls = new HashMap String>();
> acls.put(ApplicationAccessType.MODIFY_APP, "*");
> acls.put(ApplicationAccessType.VIEW_APP, "*");
> amContainer.setApplicationACLs(acls);
> {code}
> This has to be done before application submission. We have to do what 
> YARNRunner.java does: 
> 

[jira] [Commented] (OOZIE-3106) upgrade surefire-plugin to 2.20.1

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3106:
-

the tests are unrelated, they pass locally.

> upgrade surefire-plugin to 2.20.1
> -
>
> Key: OOZIE-3106
> URL: https://issues.apache.org/jira/browse/OOZIE-3106
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-3106-00.patch
>
>
> surefire plugin is 2.12.2 which is 5 years old. the most current release as 
> of this jira is 2.20.1 released September 2017 and has many fixes and 
> features to integrate with latest maven.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-2897) LauncherAM should support ACLs

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2897:

Attachment: OOZIE-2897-006.patch

> LauncherAM should support ACLs
> --
>
> Key: OOZIE-2897
> URL: https://issues.apache.org/jira/browse/OOZIE-2897
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2897-001.patch, OOZIE-2897-002.patch, 
> OOZIE-2897-003.patch, OOZIE-2897-004.patch, OOZIE-2897-005.patch, 
> OOZIE-2897-006.patch
>
>
> In MapReduce, you can define ACL-related properties:
> {noformat}
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modify-job
> {noformat}
> {{acl-view-job}} defines a list of users/groups who can retrieve the job 
> statistics. {{acl-modify-job}} defines a list of users/groups who can kill a 
> job or adjust the priority of it.
> Docs: 
> https://hadoop.apache.org/docs/r1.2.1/mapred_tutorial.html#Job+Authorization
> In YARN, we can provide backward compatibility for these properties. Example 
> code:
> {code}
> Map acls = new HashMap String>();
> acls.put(ApplicationAccessType.MODIFY_APP, "*");
> acls.put(ApplicationAccessType.VIEW_APP, "*");
> amContainer.setApplicationACLs(acls);
> {code}
> This has to be done before application submission. We have to do what 
> YARNRunner.java does: 
> https://github.com/apache/hadoop/blob/3721cfe1fbd98c5b6aa46aefdfcf62276c28c4a4/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/YARNRunner.java#L502-L507
>  
> We should also ensure the compatibility with the properties of:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2726) Flaky test due to daylight saving changes

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2726:
--

Testing JIRA OOZIE-2726

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Flaky test due to daylight saving changes
> -
>
> Key: OOZIE-2726
> URL: https://issues.apache.org/jira/browse/OOZIE-2726
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-2726-1.patch, OOZIE-2726-2.patch, 
> OOZIE-2726-3.patch, OOZIE-2726-4.patch, OOZIE-2726-5.patch
>
>
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup
> {code}
> Error Message
> expected: but was:
> Stacktrace
> junit.framework.AssertionFailedError: expected: 
> but was:
>   at junit.framework.Assert.fail(Assert.java:50)
>   at junit.framework.Assert.failNotEquals(Assert.java:287)
>   at junit.framework.Assert.assertEquals(Assert.java:67)
>   at junit.framework.Assert.assertEquals(Assert.java:74)
>   at 
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:243)
>   at junit.framework.TestSuite.run(TestSuite.java:238)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:24)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: OOZIE-2726 PreCommit Build #178

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 678.18 KB...]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [ 13.897 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 18.615 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 20.907 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.023 s]
[INFO] Apache Oozie Docs .. SUCCESS [  7.313 s]
[INFO] Apache Oozie WebApp  SUCCESS [  5.199 s]
[INFO] Apache Oozie Tools . SUCCESS [ 22.860 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  3.817 s]
[INFO] Apache Oozie Server  SUCCESS [ 20.051 s]
[INFO] Apache Oozie Distro  SUCCESS [  3.105 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  5.802 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 06:47 min
[INFO] Finished at: 2017-11-06T14:30:04Z
[INFO] Final Memory: 648M/1891M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
a/core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
 => 
b/core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java...
error: 
a/core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java:
 No such file or directory
Checking patch 
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java...
error: while searching for:
if (!tz.inDaylightTime(d1) && tz.inDaylightTime(d2)) {
Calendar cal = Calendar.getInstance(tz);
cal.setTime(d2);
return cal.get(Calendar.DST_OFFSET);
}
return 0;
}
}

error: patch failed: 
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java:938
error: 
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java:
 patch does not apply
Patch failed to apply to head of branch

  % 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
  0 3706k0 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  4019k  0 --:--:-- --:--:-- --:--:-- 17.4M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2726
Archiving artifacts
[Fast Archiver] Compressed 844.65 KB of artifacts by 37.9% relative to #164
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (OOZIE-2726) Flaky test due to daylight saving changes

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2726:
--

Testing JIRA OOZIE-2726

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Flaky test due to daylight saving changes
> -
>
> Key: OOZIE-2726
> URL: https://issues.apache.org/jira/browse/OOZIE-2726
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-2726-1.patch, OOZIE-2726-2.patch, 
> OOZIE-2726-3.patch, OOZIE-2726-4.patch, OOZIE-2726-5.patch
>
>
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup
> {code}
> Error Message
> expected: but was:
> Stacktrace
> junit.framework.AssertionFailedError: expected: 
> but was:
>   at junit.framework.Assert.fail(Assert.java:50)
>   at junit.framework.Assert.failNotEquals(Assert.java:287)
>   at junit.framework.Assert.assertEquals(Assert.java:67)
>   at junit.framework.Assert.assertEquals(Assert.java:74)
>   at 
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:243)
>   at junit.framework.TestSuite.run(TestSuite.java:238)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:24)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: OOZIE-2726 PreCommit Build #177

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 678.51 KB...]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [ 12.761 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 18.005 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 20.065 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.041 s]
[INFO] Apache Oozie Docs .. SUCCESS [  7.583 s]
[INFO] Apache Oozie WebApp  SUCCESS [  4.813 s]
[INFO] Apache Oozie Tools . SUCCESS [ 22.989 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  3.488 s]
[INFO] Apache Oozie Server  SUCCESS [ 19.417 s]
[INFO] Apache Oozie Distro  SUCCESS [  3.444 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  5.945 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 06:50 min
[INFO] Finished at: 2017-11-06T14:18:20Z
[INFO] Final Memory: 646M/1851M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
a/core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
 => 
b/core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java...
error: 
a/core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java:
 No such file or directory
Checking patch 
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java...
error: while searching for:
if (!tz.inDaylightTime(d1) && tz.inDaylightTime(d2)) {
Calendar cal = Calendar.getInstance(tz);
cal.setTime(d2);
return cal.get(Calendar.DST_OFFSET);
}
return 0;
}
}

error: patch failed: 
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java:938
error: 
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java:
 patch does not apply
Patch failed to apply to head of branch

  % 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
100 3706k  100 3706k0 0  4356k  0 --:--:-- --:--:-- --:--:-- 4356k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-2726
Archiving artifacts
[Fast Archiver] Compressed 844.65 KB of artifacts by 37.9% relative to #164
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

Re: Review Request 63327: OOZIE-2897 LauncherAM should support ACLs

[Peter Cseh via Review Board]

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




core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java
Lines 92 (patched)


Unused import.



core/src/test/java/org/apache/oozie/test/XTestCase.java
Lines 1028-1030 (original), 1029-1031 (patched)


These properties should be set in case of capacity scheduler used.


- Peter Cseh


On Nov. 6, 2017, 12:08 p.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63327/
> ---
> 
> (Updated Nov. 6, 2017, 12:08 p.m.)
> 
> 
> Review request for oozie, András Piros, Attila Sasvari, Peter Cseh, and 
> Robert Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2897
> 
> 
> Diffs
> -
> 
>   client/src/main/resources/oozie-common-1.0.xsd ddae91224 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 6a25e5c89 
>   core/src/main/java/org/apache/oozie/action/hadoop/YarnACLHandler.java 
> PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
> c36774239 
>   core/src/main/resources/oozie-default.xml 8285df0a7 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
> 36b302667 
>   core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
> 43c71b0ad 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> adb2168ca 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
>  4c5b0f972 
>   core/src/test/java/org/apache/oozie/action/hadoop/TestYarnACLHandler.java 
> PRE-CREATION 
>   core/src/test/java/org/apache/oozie/service/TestSchemaService.java 
> 940868aeb 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 912c3f316 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  a361078ac 
>   core/src/test/resources/fair-scheduler-alloc.xml PRE-CREATION 
>   core/src/test/resources/wf-schema-global-launcherconf.xml 9cd4f6c37 
> 
> 
> Diff: https://reviews.apache.org/r/63327/diff/3/
> 
> 
> Testing
> ---
> 
> - Unit test added
> - Verified on a 4-node cluster
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

[jira] [Updated] (OOZIE-3109) Good coding practice

[Denes Bodo (JIRA)]

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

Denes Bodo updated OOZIE-3109:
--
Attachment: OOZIE-3109-v001.patch

> Good coding practice
> 
>
> Key: OOZIE-3109
> URL: https://issues.apache.org/jira/browse/OOZIE-3109
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
> Attachments: OOZIE-3109-v001.patch
>
>
> That can be a security problem if we do not encode the stream read from log 
> files before transferred to the web browser.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-2900) Retrieve tokens for oozie.launcher.mapreduce.job.hdfs-servers before submission

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2900:
--
Fix Version/s: 5.0.0b1

> Retrieve tokens for oozie.launcher.mapreduce.job.hdfs-servers before 
> submission
> ---
>
> Key: OOZIE-2900
> URL: https://issues.apache.org/jira/browse/OOZIE-2900
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Attila Sasvari
> Fix For: 5.0.0b1
>
>
> We have to get tokens for oozie.launcher.mapreduce.job.hdfs-servers. Cannot 
> do cross cluster distcp without that.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-2600) OYA: Update Documentation

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2600:
--
Fix Version/s: (was: oya)
   5.0.0b1

> OYA: Update Documentation
> -
>
> Key: OOZIE-2600
> URL: https://issues.apache.org/jira/browse/OOZIE-2600
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: oya, 5.0.0
>Reporter: Robert Kanter
>Priority: Blocker
> Fix For: 5.0.0b1
>
>
> Based on the work done in OOZIE-2896, document also the way how 
> {{oozie.launcher.override.\*}} and {{oozie.launcher.prepend.\*}} parameters 
> function.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OOZIE-3109) Good coding practice

[Denes Bodo (JIRA)]

Denes Bodo created OOZIE-3109:
-

 Summary: Good coding practice
 Key: OOZIE-3109
 URL: https://issues.apache.org/jira/browse/OOZIE-3109
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.3.0
Reporter: Denes Bodo
Assignee: Denes Bodo


That can be a security problem if we do not encode the stream read from log 
files before transferred to the web browser.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-1779) Add parent-id as a filter option

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-1779:
--

Testing JIRA OOZIE-1779

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Add parent-id as a filter option
> 
>
> Key: OOZIE-1779
> URL: https://issues.apache.org/jira/browse/OOZIE-1779
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Azrael Seoeun
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-1779.1.patch, OOZIE-1779.2.patch
>
>
> Currently filtering options on jobs list are
> name, user, group, status, frequency and time-unit. 
> With increasing usage of coordinators and bundles, adding parent-id should be 
> useful instead of always searching top-down from parent to child.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Failed: OOZIE-1779 PreCommit Build #176

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 688.18 KB...]

import org.apache.oozie.service.Services;
import org.apache.oozie.test.XTestCase;
import org.junit.Test;

error: patch failed: 
core/src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java:20
error: core/src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java: 
patch does not apply
Checking patch core/src/test/java/org/apache/oozie/TestDagEngine.java...
Hunk #1 succeeded at 42 (offset 1 line).
Hunk #2 succeeded at 236 (offset 1 line).
Checking patch 
core/src/test/java/org/apache/oozie/store/TestDBWorkflowStore.java...
Hunk #1 succeeded at 397 (offset 1 line).
Checking patch 
core/src/test/java/org/apache/oozie/store/TestStoreStatusFilter.java...
Checking patch src/main/java/org/apache/oozie/client/OozieClient.java...
error: src/main/java/org/apache/oozie/client/OozieClient.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/BundleEngine.java...
error: src/main/java/org/apache/oozie/BundleEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/CoordinatorEngine.java...
error: src/main/java/org/apache/oozie/CoordinatorEngine.java: No such file or 
directory
Checking patch src/main/java/org/apache/oozie/DagEngine.java...
error: src/main/java/org/apache/oozie/DagEngine.java: No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/BundleJobInfoGetJPAExecutor.java: 
No such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/CoordJobInfoGetJPAExecutor.java: No 
such file or directory
Checking patch 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java...
error: 
src/main/java/org/apache/oozie/executor/jpa/WorkflowsJobGetJPAExecutor.java: No 
such file or directory
Checking patch src/main/java/org/apache/oozie/store/CoordinatorStore.java...
error: src/main/java/org/apache/oozie/store/CoordinatorStore.java: No such file 
or directory
Checking patch src/main/java/org/apache/oozie/store/StoreStatusFilter.java...
error: src/main/java/org/apache/oozie/store/StoreStatusFilter.java: No such 
file or directory
Checking patch src/main/java/org/apache/oozie/store/WorkflowStore.java...
error: src/main/java/org/apache/oozie/store/WorkflowStore.java: No such file or 
directory
Checking patch 
src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java...
error: src/test/java/org/apache/oozie/TestCoordinatorEngineSimple.java: No such 
file or directory
Checking patch src/test/java/org/apache/oozie/TestDagEngine.java...
error: src/test/java/org/apache/oozie/TestDagEngine.java: No such file or 
directory
Checking patch src/test/java/org/apache/oozie/store/TestDBWorkflowStore.java...
error: src/test/java/org/apache/oozie/store/TestDBWorkflowStore.java: No such 
file or directory
Checking patch 
src/test/java/org/apache/oozie/store/TestStoreStatusFilter.java...
Patch failed to apply to head of branch

  % 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
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  4285k  0 --:--:-- --:--:-- --:--:-- 5920k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-1779
Archiving artifacts
[Fast Archiver] Compressed 844.80 KB of artifacts by 37.9% relative to #164
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (OOZIE-1779) Add parent-id as a filter option

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-1779:
-

[~seoeun25] can you please update your patch on top of current master? Thanks!

> Add parent-id as a filter option
> 
>
> Key: OOZIE-1779
> URL: https://issues.apache.org/jira/browse/OOZIE-1779
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Azrael Seoeun
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-1779.1.patch, OOZIE-1779.2.patch
>
>
> Currently filtering options on jobs list are
> name, user, group, status, frequency and time-unit. 
> With increasing usage of coordinators and bundles, adding parent-id should be 
> useful instead of always searching top-down from parent to child.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 63327: OOZIE-2897 LauncherAM should support ACLs

[András Piros via Review Board]

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


Ship it!




Ship It!

- András Piros


On Nov. 6, 2017, 12:08 p.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63327/
> ---
> 
> (Updated Nov. 6, 2017, 12:08 p.m.)
> 
> 
> Review request for oozie, András Piros, Attila Sasvari, Peter Cseh, and 
> Robert Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2897
> 
> 
> Diffs
> -
> 
>   client/src/main/resources/oozie-common-1.0.xsd ddae91224 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 6a25e5c89 
>   core/src/main/java/org/apache/oozie/action/hadoop/YarnACLHandler.java 
> PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
> c36774239 
>   core/src/main/resources/oozie-default.xml 8285df0a7 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
> 36b302667 
>   core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
> 43c71b0ad 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> adb2168ca 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
>  4c5b0f972 
>   core/src/test/java/org/apache/oozie/action/hadoop/TestYarnACLHandler.java 
> PRE-CREATION 
>   core/src/test/java/org/apache/oozie/service/TestSchemaService.java 
> 940868aeb 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 912c3f316 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  a361078ac 
>   core/src/test/resources/fair-scheduler-alloc.xml PRE-CREATION 
>   core/src/test/resources/wf-schema-global-launcherconf.xml 9cd4f6c37 
> 
> 
> Diff: https://reviews.apache.org/r/63327/diff/3/
> 
> 
> Testing
> ---
> 
> - Unit test added
> - Verified on a 4-node cluster
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

Re: Review Request 63327: OOZIE-2897 LauncherAM should support ACLs

[Peter Bacsko via Review Board]

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

(Updated nov. 6, 2017, 12:08 du)


Review request for oozie, András Piros, Attila Sasvari, Peter Cseh, and Robert 
Kanter.


Repository: oozie-git


Description
---

https://issues.apache.org/jira/browse/OOZIE-2897


Diffs (updated)
-

  client/src/main/resources/oozie-common-1.0.xsd ddae91224 
  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
6a25e5c89 
  core/src/main/java/org/apache/oozie/action/hadoop/YarnACLHandler.java 
PRE-CREATION 
  core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
c36774239 
  core/src/main/resources/oozie-default.xml 8285df0a7 
  core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
36b302667 
  core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
43c71b0ad 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
adb2168ca 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
 4c5b0f972 
  core/src/test/java/org/apache/oozie/action/hadoop/TestYarnACLHandler.java 
PRE-CREATION 
  core/src/test/java/org/apache/oozie/service/TestSchemaService.java 940868aeb 
  core/src/test/java/org/apache/oozie/test/XTestCase.java 912c3f316 
  
core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
 a361078ac 
  core/src/test/resources/fair-scheduler-alloc.xml PRE-CREATION 
  core/src/test/resources/wf-schema-global-launcherconf.xml 9cd4f6c37 


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

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


Testing
---

- Unit test added
- Verified on a 4-node cluster


Thanks,

Peter Bacsko

[jira] [Updated] (OOZIE-2897) LauncherAM should support ACLs

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-2897:

Attachment: OOZIE-2897-005.patch

> LauncherAM should support ACLs
> --
>
> Key: OOZIE-2897
> URL: https://issues.apache.org/jira/browse/OOZIE-2897
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2897-001.patch, OOZIE-2897-002.patch, 
> OOZIE-2897-003.patch, OOZIE-2897-004.patch, OOZIE-2897-005.patch
>
>
> In MapReduce, you can define ACL-related properties:
> {noformat}
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modify-job
> {noformat}
> {{acl-view-job}} defines a list of users/groups who can retrieve the job 
> statistics. {{acl-modify-job}} defines a list of users/groups who can kill a 
> job or adjust the priority of it.
> Docs: 
> https://hadoop.apache.org/docs/r1.2.1/mapred_tutorial.html#Job+Authorization
> In YARN, we can provide backward compatibility for these properties. Example 
> code:
> {code}
> Map acls = new HashMap String>();
> acls.put(ApplicationAccessType.MODIFY_APP, "*");
> acls.put(ApplicationAccessType.VIEW_APP, "*");
> amContainer.setApplicationACLs(acls);
> {code}
> This has to be done before application submission. We have to do what 
> YARNRunner.java does: 
> https://github.com/apache/hadoop/blob/3721cfe1fbd98c5b6aa46aefdfcf62276c28c4a4/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/YARNRunner.java#L502-L507
>  
> We should also ensure the compatibility with the properties of:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 63327: OOZIE-2897 LauncherAM should support ACLs

[Peter Bacsko via Review Board]

> On nov. 3, 2017, 10:33 de, András Piros wrote:
> > core/src/test/java/org/apache/oozie/test/XTestCase.java
> > Lines 1046-1047 (patched)
> > 
> >
> > Depending on the runtime value of 
> > `yarn.resourcemanager.scheduler.class`, please set 
> > `yarn.scheduler.fair.allocation.file` to `fair-scheduler-alloc.xml` for 
> > `FairScheduler`, and please set another value and another XML configuration 
> > file for `CapacityScheduler`.
> > 
> > As `CapacityScheduler` is the default one in upstream Hadoop, we 
> > shouldn't override `yarn.resourcemanager.scheduler.class` to 
> > `FairScheduler`.

I'll change the code based on your suggestion.

There will be one difference: there will be no XML config for Capacity 
Scheduler, because it's hard-coded to look up capacity-scheduler.xml from the 
classpath. If there are multiple XMLs on the classpath with the same name, we 
don't know which one will be loaded. I think it's really silly, but that's how 
it works right now.


- Peter


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


On okt. 31, 2017, 3:02 du, Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63327/
> ---
> 
> (Updated okt. 31, 2017, 3:02 du)
> 
> 
> Review request for oozie, András Piros, Attila Sasvari, Peter Cseh, and 
> Robert Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2897
> 
> 
> Diffs
> -
> 
>   client/src/main/resources/oozie-common-1.0.xsd ddae91224 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 6a25e5c89 
>   core/src/main/java/org/apache/oozie/action/hadoop/YarnACLHandler.java 
> PRE-CREATION 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
> c36774239 
>   core/src/main/resources/oozie-default.xml b2036997d 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
> 36b302667 
>   core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
> 43c71b0ad 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> adb2168ca 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
>  4c5b0f972 
>   core/src/test/java/org/apache/oozie/action/hadoop/TestYarnACLHandler.java 
> PRE-CREATION 
>   core/src/test/java/org/apache/oozie/service/TestSchemaService.java 
> 940868aeb 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 584aa12ef 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  a361078ac 
>   core/src/test/resources/fair-scheduler-alloc.xml PRE-CREATION 
>   core/src/test/resources/wf-schema-global-launcherconf.xml 9cd4f6c37 
> 
> 
> Diff: https://reviews.apache.org/r/63327/diff/2/
> 
> 
> Testing
> ---
> 
> - Unit test added
> - Verified on a 4-node cluster
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

[jira] [Commented] (OOZIE-2296) Add an Oozie diagnostic bundle tool

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2296:
---

Executed tests locally:
{code}
Failed tests:   
testImportInvalidDataLeavesTablesEmpty(org.apache.oozie.tools.TestDBLoadDump): 
import should have been ended prematurely
Failed tests:   
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand):
 expected: but was:
Failed tests:   
testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation): Could 
not fetch metric
{code}
I will investigate failure of {{testJMXInstrumentation}} and 
{{testImportInvalidDataLeavesTablesEmpty}} soon (these should not be related to 
the patch in my opinion). {{testMaterizationLookup}} is known to be flaky.

> Add an Oozie diagnostic bundle tool
> ---
>
> Key: OOZIE-2296
> URL: https://issues.apache.org/jira/browse/OOZIE-2296
> Project: Oozie
>  Issue Type: New Feature
>  Components: tools
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
> Attachments: OOZIE-2296-002.patch, OOZIE-2296-003.patch, 
> OOZIE-2296-004.patch, OOZIE-2296-005.patch, OOZIE-2296-006.patch, 
> OOZIE-2296-009.patch, OOZIE-2296-010.patch, OOZIE-2296-011.patch, 
> OOZIE-2296-012.patch, OOZIE-2296-013.patch, OOZIE-2296-014.patch, 
> OOZIE-2296-015.patch, OOZIE-2296-016.patch, OOZIE-2296-017.patch
>
>
> To help with our support cases, I've built a tool that collects a bunch of 
> job and other information from Oozie that throws it all in a tarball.  The 
> idea is that the user can just click a button in Cloudera Manager, and it 
> will run this tool.  
> This tool could be useful for others as an easy way to get information out of 
> Oozie, so I thought I'd contribute it here.  It's built as a "tool" (so it 
> sits next to the sharelib and database tools), and simply uses the Oozie 
> client for getting pretty much everything, so it doesn't require anything 
> special.
> Here's the information that it can get:
> # Sharelib: {{ooze admin -shareliblist}} and {{oozie admin -shareliblist 
> }}
> # Oozie Server's resolved loaded configuration (from admin endpoint)
> # Other admin commands output (queue dump, env vars, etc)
> # Thread dump (HOST:11000/oozie/admin/jvminfo.jsp)
> # Details from last n jobs and/or specific list of jobs
> #- job.properties contents
> #- XML definition
> #- verbose status for each job and each action etc
> #- Oozie logs
> #- Unfortunately, we can't get the launcher jobs' logs from Hadoop
> # Metrics/Instrumentation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-3102) External Link to "EL Expression Language Quick Reference" not found

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-3102:
---

+1

> External Link to "EL Expression Language Quick Reference" not found
> ---
>
> Key: OOZIE-3102
> URL: https://issues.apache.org/jira/browse/OOZIE-3102
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 3.1.3, 3.2.0, 3.3.0, 3.3.1, 3.3.2, 4.0.0
> Environment: * Linux Mint 18.2 x64
> * Chrome Version 62.0.3202.62
> * Firefox 56.0 (64-bit)
>Reporter: David Eigenstuhler
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-3102-001.patch, OOZIE-3102-002.patch
>
>
> The documentation on https://oozie.apache.org/docs/ provides an external link 
> for more information on EL functions (`EL Expression Language Quick 
> Reference` under Developer Documentation). 
> In the affected versions the link goes to 
> `http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPIntro7.html#wp77280` which 
> is not found and results in the start page of the `The J2EE 1.4 Tutorial`. 
> Correct link would be 
> `https://docs.oracle.com/javaee/1.4/tutorial/doc/JSPIntro7.html#wp71019`



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OOZIE-2913) Investigate if DistCpActionExecutor works as expected

[Attila Sasvari (JIRA)]

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

Attila Sasvari resolved OOZIE-2913.
---
Resolution: Duplicate

> Investigate if DistCpActionExecutor works as expected
> -
>
> Key: OOZIE-2913
> URL: https://issues.apache.org/jira/browse/OOZIE-2913
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>
> We've removed the call of {{getLauncherClasses}} in 
> {{core/src/main/java/org/apache/oozie/action/hadoop/DistcpActionExecutor.java 
> }} 
> We should validate that this does not caused a regression and remove the 
> function or add this call back with some tests if it causes issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-3103) Improve log message regarding max concurrency for coordinators

[Attila Sasvari (JIRA)]

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

Attila Sasvari updated OOZIE-3103:
--
Attachment: OOZIE-3103-002.patch

[~rkanter] thanks for the review! 002 patch addresses your comments.

> Improve log message regarding max concurrency for coordinators
> --
>
> Key: OOZIE-3103
> URL: https://issues.apache.org/jira/browse/OOZIE-3103
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-3103-001.patch, OOZIE-3103-002.patch
>
>
> Currently, when maximum concurrency is reached for coordinators, the log 
> message is as follows:
> {code}
> 2017-09-25 06:00:00,069 WARN 
> org.apache.oozie.command.coord.CoordActionReadyXCommand: 
> SERVER[dsfsdfsdfds.com] USER[testclu0] GROUP[-] TOKEN[] 
> APP[test->dev->xyzabc] JOB[065-191474932323346-oozie-oozi-C] ACTION[] No 
> actions to start for jobId=065-191474932323346-oozie-oozi-C as max 
> concurrency reached!
> {code}
> It's confusing as-is and sounds like something is wrong, even though it's 
> perfectly fine. 
> We should make it an INFO message and say something more specific and less 
> scary sounding (no exclamation ). Maybe something like "Not starting any 
> additional actions because max concurrency \[] for \[] has 
> been reached"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-1401) PurgeCommand should purge the workflow jobs w/o end_time

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-1401:
---

[~gezapeti] thanks for the review. Committed to master.

> PurgeCommand should purge the workflow jobs w/o end_time
> 
>
> Key: OOZIE-1401
> URL: https://issues.apache.org/jira/browse/OOZIE-1401
> Project: Oozie
>  Issue Type: Sub-task
>  Components: bundle, coordinator, workflow
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Attila Sasvari
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-1401-001.patch
>
>
> Currently, {{PurgeXCommand}} logic is not working with those workflow jobs 
> with {{end_time=null}}. This command needs to take care of those jobs as 
> well. This happens in the case of long stuck jobs after Hadoop restarts or DB 
> failures. It could be done by checking {{last_modified_time}} instead, if 
> {{end_time}} is not available.
> The current query:
> {code:sql}
> select w from WorkflowJobBean w where w.endTimestamp < :endTime
> {code}
> There is also an issue when:
> * there is a parent workflow that has its {{end_time}} set
> * is otherwise eligible for {{PurgeXCommand}}: {{end_time}} is older than 
> configured number of days, and has {{status}} either {{KILLED}}, or 
> {{FAILED}}, or {{SUCCEEDED}}
> * has a child workflow that has the {{parent_id}} set to the {{id}} of the 
> parent workflow
> * child workflow has its {{end_time = NULL}}
> In this case, 
> [*{{PurgeXCommand#fetchTerminatedWorkflow()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/PurgeXCommand.java#L249]
>  throws a {{NullPointerException}} like this:
> {noformat}
> 2017-09-29 07:59:46,365 DEBUG org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Purging workflows of long running coordinators is turned on
> 2017-09-29 07:59:46,371 DEBUG org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Execute command [purge] key [null]
> 2017-09-29 07:59:46,371 INFO org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] STARTED Purge to purge Workflow Jobs older than [1] days, 
> Coordinator Jobs older than [1] days, and Bundlejobs older than [1] days.
> 2017-09-29 07:59:46,375 ERROR org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Exception, 
> java.lang.NullPointerException
>   at 
> org.apache.oozie.command.PurgeXCommand.fetchTerminatedWorkflow(PurgeXCommand.java:249)
>   at 
> org.apache.oozie.command.PurgeXCommand.processWorkflowsHelper(PurgeXCommand.java:227)
>   at 
> org.apache.oozie.command.PurgeXCommand.processWorkflows(PurgeXCommand.java:199)
>   at 
> org.apache.oozie.command.PurgeXCommand.execute(PurgeXCommand.java:150)
>   at org.apache.oozie.command.PurgeXCommand.execute(PurgeXCommand.java:53)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:286)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-1401) PurgeCommand should purge the workflow jobs w/o end_time

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-1401:
---

{{TestCoordMaterializeTransitionXCommand.testMaterizationLookup}} is known to 
be flaky - [OOZIE-2726 |https://issues.apache.org/jira/browse/OOZIE-2726]

> PurgeCommand should purge the workflow jobs w/o end_time
> 
>
> Key: OOZIE-1401
> URL: https://issues.apache.org/jira/browse/OOZIE-1401
> Project: Oozie
>  Issue Type: Sub-task
>  Components: bundle, coordinator, workflow
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Attila Sasvari
> Attachments: OOZIE-1401-001.patch
>
>
> Currently, {{PurgeXCommand}} logic is not working with those workflow jobs 
> with {{end_time=null}}. This command needs to take care of those jobs as 
> well. This happens in the case of long stuck jobs after Hadoop restarts or DB 
> failures. It could be done by checking {{last_modified_time}} instead, if 
> {{end_time}} is not available.
> The current query:
> {code:sql}
> select w from WorkflowJobBean w where w.endTimestamp < :endTime
> {code}
> There is also an issue when:
> * there is a parent workflow that has its {{end_time}} set
> * is otherwise eligible for {{PurgeXCommand}}: {{end_time}} is older than 
> configured number of days, and has {{status}} either {{KILLED}}, or 
> {{FAILED}}, or {{SUCCEEDED}}
> * has a child workflow that has the {{parent_id}} set to the {{id}} of the 
> parent workflow
> * child workflow has its {{end_time = NULL}}
> In this case, 
> [*{{PurgeXCommand#fetchTerminatedWorkflow()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/PurgeXCommand.java#L249]
>  throws a {{NullPointerException}} like this:
> {noformat}
> 2017-09-29 07:59:46,365 DEBUG org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Purging workflows of long running coordinators is turned on
> 2017-09-29 07:59:46,371 DEBUG org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Execute command [purge] key [null]
> 2017-09-29 07:59:46,371 INFO org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] STARTED Purge to purge Workflow Jobs older than [1] days, 
> Coordinator Jobs older than [1] days, and Bundlejobs older than [1] days.
> 2017-09-29 07:59:46,375 ERROR org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Exception, 
> java.lang.NullPointerException
>   at 
> org.apache.oozie.command.PurgeXCommand.fetchTerminatedWorkflow(PurgeXCommand.java:249)
>   at 
> org.apache.oozie.command.PurgeXCommand.processWorkflowsHelper(PurgeXCommand.java:227)
>   at 
> org.apache.oozie.command.PurgeXCommand.processWorkflows(PurgeXCommand.java:199)
>   at 
> org.apache.oozie.command.PurgeXCommand.execute(PurgeXCommand.java:150)
>   at org.apache.oozie.command.PurgeXCommand.execute(PurgeXCommand.java:53)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:286)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-1401) PurgeCommand should purge the workflow jobs w/o end_time

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-1401:
---

+1 
Test is failing due OOZIE-2726.

> PurgeCommand should purge the workflow jobs w/o end_time
> 
>
> Key: OOZIE-1401
> URL: https://issues.apache.org/jira/browse/OOZIE-1401
> Project: Oozie
>  Issue Type: Sub-task
>  Components: bundle, coordinator, workflow
>Affects Versions: trunk
>Reporter: Mona Chitnis
>Assignee: Attila Sasvari
> Attachments: OOZIE-1401-001.patch
>
>
> Currently, {{PurgeXCommand}} logic is not working with those workflow jobs 
> with {{end_time=null}}. This command needs to take care of those jobs as 
> well. This happens in the case of long stuck jobs after Hadoop restarts or DB 
> failures. It could be done by checking {{last_modified_time}} instead, if 
> {{end_time}} is not available.
> The current query:
> {code:sql}
> select w from WorkflowJobBean w where w.endTimestamp < :endTime
> {code}
> There is also an issue when:
> * there is a parent workflow that has its {{end_time}} set
> * is otherwise eligible for {{PurgeXCommand}}: {{end_time}} is older than 
> configured number of days, and has {{status}} either {{KILLED}}, or 
> {{FAILED}}, or {{SUCCEEDED}}
> * has a child workflow that has the {{parent_id}} set to the {{id}} of the 
> parent workflow
> * child workflow has its {{end_time = NULL}}
> In this case, 
> [*{{PurgeXCommand#fetchTerminatedWorkflow()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/PurgeXCommand.java#L249]
>  throws a {{NullPointerException}} like this:
> {noformat}
> 2017-09-29 07:59:46,365 DEBUG org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Purging workflows of long running coordinators is turned on
> 2017-09-29 07:59:46,371 DEBUG org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Execute command [purge] key [null]
> 2017-09-29 07:59:46,371 INFO org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] STARTED Purge to purge Workflow Jobs older than [1] days, 
> Coordinator Jobs older than [1] days, and Bundlejobs older than [1] days.
> 2017-09-29 07:59:46,375 ERROR org.apache.oozie.command.PurgeXCommand: 
> SERVER[host-10-17-101-90.coe.cloudera.com] USER[-] GROUP[-] TOKEN[-] APP[-] 
> JOB[-] ACTION[-] Exception, 
> java.lang.NullPointerException
>   at 
> org.apache.oozie.command.PurgeXCommand.fetchTerminatedWorkflow(PurgeXCommand.java:249)
>   at 
> org.apache.oozie.command.PurgeXCommand.processWorkflowsHelper(PurgeXCommand.java:227)
>   at 
> org.apache.oozie.command.PurgeXCommand.processWorkflows(PurgeXCommand.java:199)
>   at 
> org.apache.oozie.command.PurgeXCommand.execute(PurgeXCommand.java:150)
>   at org.apache.oozie.command.PurgeXCommand.execute(PurgeXCommand.java:53)
>   at org.apache.oozie.command.XCommand.call(XCommand.java:286)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)