date:20171027

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 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: 2047
Tests failed: 0
Tests errors: 1

The patch failed the following testcases:

  

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/143/

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

test-patch exit code: 1

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



###
## FAILED TESTS (if any) 
##
1 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 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at

[jira] [Commented] (OOZIE-3097) Change version in pom in master to 5.0.0-beta1


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

Hadoop QA commented on OOZIE-3097:
--

Testing JIRA OOZIE-3097

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 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: 2047
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

.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/143/

> Change version in pom in master to 5.0.0-beta1
> --
>
> Key: OOZIE-3097
> URL: https://issues.apache.org/jira/browse/OOZIE-3097
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0b1
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-3097-00.patch
>
>
> In preparation to the 5b1 release we should modify the version in the POM 
> files to 5.0.0-beta1.



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

[jira] [Commented] (OOZIE-3097) Change version in pom in master to 5.0.0-beta1


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

Hadoop QA commented on OOZIE-3097:
--

Testing JIRA OOZIE-3097

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 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 [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 [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2047
.Tests rerun: 63
.Tests failed at first run: 
org.apache.oozie.command.coord.TestCoordActionsKillXCommand,org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.service.TestPartitionDependencyManagerEhcache,
{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/144/

> Change version in pom in master to 5.0.0-beta1
> --
>
> Key: OOZIE-3097
> URL: https://issues.apache.org/jira/browse/OOZIE-3097
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0b1
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-3097-00.patch
>
>
> In preparation to the 5b1 release we should modify the version in the POM 
> files to 5.0.0-beta1.



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

Failed: OOZIE-3097 PreCommit Build #144

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 MB...]
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [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 [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [tools].
+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: 2047
Tests rerun: 63
Tests failed at first run: 
org.apache.oozie.command.coord.TestCoordActionsKillXCommand,org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.service.TestPartitionDependencyManagerEhcache,
+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/144/

  % 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  3803k  0 --:--:-- --:--:-- --:--:-- 16.0M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

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



###
## FAILED TESTS (if any) 
##
All tests passed

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


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

Hadoop QA commented on OOZIE-2897:
--

Testing JIRA OOZIE-2897

Cleaning local git workspace



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



> 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.0
>
> Attachments: OOZIE-2897-001.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)

Failed: OOZIE-2897 PreCommit Build #145

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 679.16 KB...]
Checking patch a/client/src/main/resources/oozie-common-1.0.xsd => 
b/client/src/main/resources/oozie-common-1.0.xsd...
error: a/client/src/main/resources/oozie-common-1.0.xsd: No such file or 
directory
Checking patch 
a/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java => 
b/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java...
error: 
a/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java: No 
such file or directory
Checking patch 
a/core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
=> 
b/core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java...
error: 
a/core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java: 
No such file or directory
Checking patch 
a/core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java => 
b/core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java...
error: 
a/core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java: No 
such file or directory
Checking patch 
a/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
=> 
b/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java...
error: 
a/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java:
 No such file or directory
Checking patch 
a/core/src/test/java/org/apache/oozie/service/TestSchemaService.java => 
b/core/src/test/java/org/apache/oozie/service/TestSchemaService.java...
error: a/core/src/test/java/org/apache/oozie/service/TestSchemaService.java: No 
such file or directory
Checking patch a/core/src/test/java/org/apache/oozie/test/XTestCase.java => 
b/core/src/test/java/org/apache/oozie/test/XTestCase.java...
error: a/core/src/test/java/org/apache/oozie/test/XTestCase.java: No such file 
or directory
Checking patch 
a/core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
 => 
b/core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java...
error: 
a/core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java:
 No such file or directory
Checking patch b/core/src/test/resources/fair-scheduler-alloc.xml...
Checking patch a/core/src/test/resources/wf-schema-global-launcherconf.xml => 
b/core/src/test/resources/wf-schema-global-launcherconf.xml...
error: a/core/src/test/resources/wf-schema-global-launcherconf.xml: No such 
file or directory
Checking patch client/src/main/resources/oozie-common-1.0.xsd...
Checking patch 
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java...
Hunk #1 succeeded at 64 (offset 1 line).
error: while searching for:
public static final String DEFAULT_LAUNCHER_MEMORY_MB = 
"oozie.launcher.default.memory.mb";
public static final String DEFAULT_LAUNCHER_PRIORITY = 
"oozie.launcher.default.priority";
public static final String DEFAULT_LAUNCHER_QUEUE = 
"oozie.launcher.default.queue";

public static final String MAX_EXTERNAL_STATS_SIZE = 
"oozie.external.stats.max.size";
public static final String ACL_VIEW_JOB = "mapreduce.job.acl-view-job";

error: patch failed: 
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java:150
error: 
core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java: 
patch does not apply
Checking patch 
core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java...
Checking patch 
core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java...
Checking patch 
core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java...
Checking patch 
core/src/test/java/org/apache/oozie/service/TestSchemaService.java...
Checking patch core/src/test/java/org/apache/oozie/test/XTestCase.java...
Checking patch 
core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java...
Checking patch core/src/test/resources/fair-scheduler-alloc.xml...
Checking patch core/src/test/resources/wf-schema-global-launcherconf.xml...
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  28960 0   4968  0  0:12:43 --:--:--  0:12:43  
4968100 3706k  100 3706k0 0  4714k  0 --:--:-- --:--:-- --:--:-- 
17.8M
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as

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

2017-10-27 Thread Satish Subhashrao Saley (JIRA)

Satish Subhashrao Saley created OOZIE-3101:
--

 Summary: 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


For web service APIs, currently Oozie adds error message in the response 
header. Oozie should also put error message in the response body.



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

[jira] [Commented] (OOZIE-3097) Change version in pom in master to 5.0.0-beta1


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

Peter Cseh commented on OOZIE-3097:
---

Thanks for picking this up so quickly! I've triggered a pre-commit build to 
make sure nothing broke.

> Change version in pom in master to 5.0.0-beta1
> --
>
> Key: OOZIE-3097
> URL: https://issues.apache.org/jira/browse/OOZIE-3097
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0b1
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-3097-00.patch
>
>
> In preparation to the 5b1 release we should modify the version in the POM 
> files to 5.0.0-beta1.



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

[jira] [Comment Edited] (OOZIE-3100) Upgrade javax.mail:mail to 1.4.7


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

Peter Cseh edited comment on OOZIE-3100 at 10/27/17 8:27 PM:
-

Jira run failed to comment, but here is the result:
https://builds.apache.org/job/PreCommit-OOZIE-Build/142/console
{code}

Testing JIRA OOZIE-3100

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [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 [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [tools].
+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: 2047
Tests rerun: 67
Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.util.TestMetricsInstrumentation,org.apache.oozie.service.TestPartitionDependencyManagerEhcache,
+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/142/

  % 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  16264  0  0:03:53 --:--:--  0:03:53 16264
100 3706k  100 3706k0 0  3633k  0  0:00:01  0:00:01 --:--:-- 16.5M
Adding comment to JIRA
Unable to log in to server: 
https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: hadoopqa.
 Cause: JIRA is currently being re-indexed. Depending on how large the database 
is, this may take a few minutes. JIRA will automatically become available as 
soon as this task is complete.   
{code}


was (Author: gezapeti):
Jira run failed to comment, but here is the result:
{code}

Testing JIRA OOZIE-3100

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [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 [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs

[jira] [Commented] (OOZIE-3100) Upgrade javax.mail:mail to 1.4.7


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

Peter Cseh commented on OOZIE-3100:
---

Jira run failed to comment, but here is the result:
{code}

Testing JIRA OOZIE-3100

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [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 [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [tools].
+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: 2047
Tests rerun: 67
Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.util.TestMetricsInstrumentation,org.apache.oozie.service.TestPartitionDependencyManagerEhcache,
+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/142/

  % 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  16264  0  0:03:53 --:--:--  0:03:53 16264
100 3706k  100 3706k0 0  3633k  0  0:00:01  0:00:01 --:--:-- 16.5M
Adding comment to JIRA
Unable to log in to server: 
https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: hadoopqa.
 Cause: JIRA is currently being re-indexed. Depending on how large the database 
is, this may take a few minutes. JIRA will automatically become available as 
soon as this task is complete.   
{code}

> Upgrade javax.mail:mail to 1.4.7
> 
>
> Key: OOZIE-3100
> URL: https://issues.apache.org/jira/browse/OOZIE-3100
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3100.001.patch
>
>
> We use a super old version {{1.4.0}} of {{javax.mail:mail}} that has security 
> vulnerabilities. Let's upgrade to the latest stable {{1.4.7}}.



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

Failed: OOZIE-3100 PreCommit Build #142

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

###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 1.60 MB...]
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
+1 There are no new bugs found in [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 [docs].
+1 There are no new bugs found in [examples].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/hcatalog].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [tools].
+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: 2047
Tests rerun: 67
Tests failed at first run:
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.util.TestMetricsInstrumentation,org.apache.oozie.service.TestPartitionDependencyManagerEhcache,
+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/142/

% 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 16264 0 0:03:53 --:--:-- 0:03:53
16264100 3706k 100 3706k0 0 3633k 0 0:00:01 0:00:01 --:--:--
16.5M
Adding comment to JIRA
Unable to log in to server:
https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: hadoopqa.
Cause: JIRA is currently being re-indexed. Depending on how large the database
is, this may take a few minutes. JIRA will automatically become available as
soon as this task is complete.

test-patch exit code: 1

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

###
## FAILED TESTS (if any)
##
All tests passed

[jira] [Commented] (OOZIE-3098) Allow to use the rest api to get the creation time of the Coordinator


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

Hadoop QA commented on OOZIE-3098:
--

Testing JIRA OOZIE-3098

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 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 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 [examples].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2047
.Tests rerun: 54
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}

{color:red}. There is at least one warning, please check{color}

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

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

> Allow to use the rest api to get the creation time of the Coordinator
> -
>
> Key: OOZIE-3098
> URL: https://issues.apache.org/jira/browse/OOZIE-3098
> Project: Oozie
>  Issue Type: Improvement
>  Components: coordinator
>Affects Versions: 4.3.0
>Reporter: Chi Wen
>Assignee: Chi Wen
> Fix For: 5.0.0
>
> Attachments: OOZIE-3098-001.patch
>
>
> It seems that the rest api cannot get the creation time of the Coordinator;
> RB link: https://reviews.apache.org/r/63296/



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

Success: OOZIE-3098 PreCommit Build #141

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 MB...]
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +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/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2047
Tests rerun: 54
Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s

 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/141/

  % 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  4569k  0 --:--:-- --:--:-- --:--:-- 4569k
Adding comment to JIRA
Comment added.

test-patch exit code: 0

[description-setter] Description set: OOZIE-3098
Archiving artifacts
[Fast Archiver] Compressed 1.81 MB of artifacts by 62.3% relative to #140
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script


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

Andras Piros commented on OOZIE-3084:
-

[~asasvari] any thoughts on the previous one?

> Add missing JVM properties to Jetty startup script
> --
>
> Key: OOZIE-3084
> URL: https://issues.apache.org/jira/browse/OOZIE-3084
> Project: Oozie
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, 
> OOZIE-3084.001.patch
>
>
> In OOZIE-2666, when Oozie has moved from Tomcat to Jetty, we also moved the 
> Tomcat related JVM options inside the startup script {{bin/oozied.sh}} to the 
> more specific {{bin/oozie-jetty-server.sh}}.
> It seems that not all the 
> [*{{catalina_opts}}*|https://github.com/apache/oozie/blob/branch-4.3/distro/src/main/bin/oozied.sh#L54-L74]
>  have been moved to 
> [*{{jetty_opts}}*|https://github.com/apache/oozie/blob/master/distro/src/main/bin/oozie-jetty-server.sh#L70-L86].
>  Such an example is {{oozie.instance.id}}, causing we don't have any server 
> name information within the Oozie server logs.
> So the task is to investigate startup scripts and put missing and needed 
> {{catalina_opts}} to {{jetty_opts}}.



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

[jira] [Updated] (OOZIE-3100) Upgrade javax.mail:mail to 1.4.7


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

Andras Piros updated OOZIE-3100:

Attachment: OOZIE-3100.001.patch

> Upgrade javax.mail:mail to 1.4.7
> 
>
> Key: OOZIE-3100
> URL: https://issues.apache.org/jira/browse/OOZIE-3100
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3100.001.patch
>
>
> We use a super old version {{1.4.0}} of {{javax.mail:mail}} that has security 
> vulnerabilities. Let's upgrade to the latest stable {{1.4.7}}.



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

[jira] [Updated] (OOZIE-3100) Upgrade javax.mail:mail to 1.4.7


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

Andras Piros updated OOZIE-3100:

Description: We use a super old version {{1.4.0}} of {{javax.mail:mail}} 
that has security vulnerabilities. Let's upgrade to the latest stable 
{{1.4.7}}.  (was: We use a super old version {{1.4.0}} of {{javax.mail:mail}} 
that has security vulnerabilities. Let's update to the latest stable {{1.4.7}}.)

> Upgrade javax.mail:mail to 1.4.7
> 
>
> Key: OOZIE-3100
> URL: https://issues.apache.org/jira/browse/OOZIE-3100
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
>
> We use a super old version {{1.4.0}} of {{javax.mail:mail}} that has security 
> vulnerabilities. Let's upgrade to the latest stable {{1.4.7}}.



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

[jira] [Created] (OOZIE-3100) Upgrade javax.mail:mail to 1.4.7

Andras Piros created OOZIE-3100:
---

 Summary: Upgrade javax.mail:mail to 1.4.7
 Key: OOZIE-3100
 URL: https://issues.apache.org/jira/browse/OOZIE-3100
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.0
Reporter: Andras Piros
Assignee: Andras Piros
 Fix For: 5.0.0


We use a super old version {{1.4.0}} of {{javax.mail:mail}} that has security 
vulnerabilities. Let's update to the latest stable {{1.4.7}}.



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

[jira] [Assigned] (OOZIE-2929) Coordinator SLA should support configuration variable

2017-10-27 Thread Robert Kanter (JIRA)


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

Robert Kanter reassigned OOZIE-2929:


Assignee: Chi Wen

> Coordinator SLA should support configuration variable
> -
>
> Key: OOZIE-2929
> URL: https://issues.apache.org/jira/browse/OOZIE-2929
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 4.3.0
>Reporter: Chi Wen
>Assignee: Chi Wen
> Attachments: OOZIE-2929-001.patch, OOZIE-2929-002.patch
>
>
> if coordinator.xml define SLA like this:
>   
> ${nominal_time}
> ${ 1 * HOURS}
> ${1 * MINUTES}
>   
> In job.properties define: nominal_time=${coord:nominalTime()}
> Then coordinator will run failed for "Coord Job Materialization Error: Could 
> not parse [${coord:nominalTime()}] using [-MM-dd'T'HH:mm+0800] mask";
> Oozie should support use define a variable for SLA;



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

[jira] [Assigned] (OOZIE-3098) Allow to use the rest api to get the creation time of the Coordinator

2017-10-27 Thread Robert Kanter (JIRA)


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

Robert Kanter reassigned OOZIE-3098:


Assignee: Chi Wen

Done.

> Allow to use the rest api to get the creation time of the Coordinator
> -
>
> Key: OOZIE-3098
> URL: https://issues.apache.org/jira/browse/OOZIE-3098
> Project: Oozie
>  Issue Type: Improvement
>  Components: coordinator
>Affects Versions: 4.3.0
>Reporter: Chi Wen
>Assignee: Chi Wen
> Fix For: 5.0.0
>
> Attachments: OOZIE-3098-001.patch
>
>
> It seems that the rest api cannot get the creation time of the Coordinator;
> RB link: https://reviews.apache.org/r/63296/



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

[jira] [Commented] (OOZIE-3098) Allow to use the rest api to get the creation time of the Coordinator


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

Andras Piros commented on OOZIE-3098:
-

Thanks for the patch [~chiwen]! +1 (pending Jenkins)

[~rkanter] can you please make [~chiwen] an Oozie JIRA member? Thanks!

> Allow to use the rest api to get the creation time of the Coordinator
> -
>
> Key: OOZIE-3098
> URL: https://issues.apache.org/jira/browse/OOZIE-3098
> Project: Oozie
>  Issue Type: Improvement
>  Components: coordinator
>Affects Versions: 4.3.0
>Reporter: Chi Wen
> Fix For: 5.0.0
>
> Attachments: OOZIE-3098-001.patch
>
>
> It seems that the rest api cannot get the creation time of the Coordinator;
> RB link: https://reviews.apache.org/r/63296/



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

Re: Review Request 63296: Allow rest api to get the creation time of the Coordinator


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


Ship it!




Ship It!

- András Piros


On Oct. 25, 2017, 1:22 p.m., Wen Chi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63296/
> ---
> 
> (Updated Oct. 25, 2017, 1:22 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-3098
> https://issues.apache.org/jira/browse/OOZIE-3098
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Allow to use the rest api to get the creation time of the Coordinator
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/client/CoordinatorJob.java 
> d98a6acc9efb0d787257143eabd4ef95b49cb759 
>   client/src/main/java/org/apache/oozie/client/rest/JsonTags.java 
> 3ec4cca9d4212c9e101cf97b1f2c952bc2a6342c 
>   client/src/main/java/org/apache/oozie/client/rest/JsonToBean.java 
> 4c653920fe234599e05d35fb09f2051c949342ac 
>   client/src/test/java/org/apache/oozie/client/rest/TestJsonToBean.java 
> a102699253a6a1e5952f830e3704bde3b5df83a8 
>   core/src/main/java/org/apache/oozie/CoordinatorJobBean.java 
> 7dda508d7bf7ad48aee045c370eca2fe06c091fa 
> 
> 
> Diff: https://reviews.apache.org/r/63296/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Wen Chi
> 
>

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

2017-10-27 Thread Peter Bacsko via Review Board



> On okt. 27, 2017, 1:47 du, András Piros wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
> > Lines 154-155 (patched)
> > 
> >
> > Should go to `LauncherAM#OOZIE_LAUNCHER_MODIFY_ACL`.

Initially I wanted to put them there. However, these variables are not 
referenced in LauncherAM, because you set up the ACLs in JavaActionExecutor.


> On okt. 27, 2017, 1:47 du, András Piros wrote:
> > core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java
> > Lines 1659-1687 (patched)
> > 
> >
> > In general, that's a good negative test. What about a positive one - 
> > killing succeeds w/ the given user? What about another one when 
> > `mapreduce.cluster.acls.enabled` is left `false` (the feature shouldn't 
> > work)?

I will add those scenarios as well.


> On okt. 27, 2017, 1:47 du, András Piros wrote:
> > core/src/test/java/org/apache/oozie/test/XTestCase.java
> > Lines 1031-1032 (patched)
> > 
> >
> > That's something I'd set per test case. I don't think we should in 
> > general override the default value for all the `? extends XTestCase`s.

This is theoretically possible. But it would mean that we have to stop the Mini 
YARN cluster for this test and then restart it for the rest of the test suite. 
I feel this could introduce some unwanted side-effects.


- Peter


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


On okt. 26, 2017, 12:24 du, Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63327/
> ---
> 
> (Updated okt. 26, 2017, 12:24 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 
> 76d0daa4f 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
> c36774239 
>   core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
> 43c71b0ad 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> a7bd357f8 
>   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/1/
> 
> 
> Testing
> ---
> 
> - Unit test added
> - Verified on a 4-node cluster
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

[jira] [Commented] (OOZIE-2929) Coordinator SLA should support configuration variable


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

Andras Piros commented on OOZIE-2929:
-

[~chiwen] {{TestMetricsInstrumentation#testJMXInstrumentation()}} is known to 
be flaky and unrelated.

[~rkanter] can you please make [~chiwen] an Oozie JIRA member?

> Coordinator SLA should support configuration variable
> -
>
> Key: OOZIE-2929
> URL: https://issues.apache.org/jira/browse/OOZIE-2929
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 4.3.0
>Reporter: Chi Wen
> Attachments: OOZIE-2929-001.patch, OOZIE-2929-002.patch
>
>
> if coordinator.xml define SLA like this:
>   
> ${nominal_time}
> ${ 1 * HOURS}
> ${1 * MINUTES}
>   
> In job.properties define: nominal_time=${coord:nominalTime()}
> Then coordinator will run failed for "Coord Job Materialization Error: Could 
> not parse [${coord:nominalTime()}] using [-MM-dd'T'HH:mm+0800] mask";
> Oozie should support use define a variable for SLA;



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

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


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




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


Should go to `LauncherAM#OOZIE_LAUNCHER_MODIFY_ACL`.



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


Should go to `LauncherAM#OOZIE_LAUNCHER_VIEW_ACL`.



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


I think we should take `mapreduce.cluster.acls.enabled` / 
`mapred.acls.enabled` into consideration, shouldn't we? Default is `false`, in 
that case we shouldn't set ACLs even if the user has employed 
`oozie.launcher.acl-view-job` / `oozie.launcher.acl-modify-job`.



core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java
Lines 34-35 (patched)


Please also extend `oozie-default.xml` with proper override key / value 
pairs like:
* `oozie.launcher.override.acl-view-job` -> `mapreduce.job.acl-view-job`
* `oozie.launcher.override.acl-modify-job` -> `mapreduce.job.acl-modify-job`

and extend unit test cases regarding that aspect, as well.



core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java
Lines 69 (patched)


Use `LauncherAM#OOZIE_LAUNCHER_VIEW_ACL`.



core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java
Lines 70 (patched)


Use `LauncherAM#OOZIE_LAUNCHER_MODIFY_ACL`.



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


Extract method `checkAndSleep(args)`.



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


Very good naming! :)



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


In general, that's a good negative test. What about a positive one - 
killing succeeds w/ the given user? What about another one when 
`mapreduce.cluster.acls.enabled` is left `false` (the feature shouldn't work)?



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


Would extract method `modifyUserAndKill(String userId)`.



core/src/test/java/org/apache/oozie/test/XTestCase.java
Lines 1031-1032 (patched)


That's something I'd set per test case. I don't think we should in general 
override the default value for all the `? extends XTestCase`s.



core/src/test/java/org/apache/oozie/test/XTestCase.java
Lines 1033-1034 (patched)


Please extract method / comment why it's needed.


- András Piros


On Oct. 26, 2017, 12:24 p.m., Peter Bacsko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63327/
> ---
> 
> (Updated Oct. 26, 2017, 12:24 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 
> 76d0daa4f 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LauncherConfigHandler.java 
> c36774239 
>   core/src/test/java/org/apache/oozie/action/hadoop/LauncherMainTester.java 
> 43c71b0ad 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> a7bd357f8 
>   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/1/
> 
> 
> Testing
> ---
> 
> - Unit test added
> - Verified on a 4-node cluster
> 
> 
> Thanks,
> 
> Peter Bacsko
> 
>

[jira] [Commented] (OOZIE-2896) Ensure compatibility for existing LauncherMapper settings


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

Andras Piros commented on OOZIE-2896:
-

Thanks [~gezapeti] and [~pbacsko] for the reviews! Committed to master.

> Ensure compatibility for existing LauncherMapper settings
> -
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2896.001.patch, OOZIE-2896.002.patch, 
> OOZIE-2896.002.patch, OOZIE-2896.003.patch, OOZIE-2896.004.patch, 
> OOZIE-2896.005.patch, OOZIE-2896.006.patch, OOZIE-2896.007.patch, 
> OOZIE-2896.008.patch
>
>
> There are a couple of LauncherMapper settings that we should support for 
> backward compatibility reasons.
> For example, {{oozie.launcher.mapreduce.map.memory.mb}}, 
> {{mapred.child.env}}, {{mapred.map.env}}, etc.
> We also have to discuss the list of properties we're going to support, since 
> there are many of them.
> List of hadoop properties under this task:
> mapreduce.job.queuename
> mapreduce.map.memory.mb
> mapreduce.map.java.opts
> mapreduce.map.env
> mapreduce.job.priority
> yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms
> yarn.app.mapreduce.am.resource.mb
> yarn.app.mapreduce.am.command-opts
> yarn.app.mapreduce.am.env
> ACL related properties should go under OOZIE-2897:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



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

Success: OOZIE-2896 PreCommit Build #140

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.97 MB...]
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [docs].
 +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/hive2].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/distcp].
 +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 [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2047
Tests rerun: 54
Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,
+1 DISTRO
+1 distro tarball builds with the patch 


+1 Overall result, good!, no -1s

 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/140/

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

test-patch exit code: 0

[description-setter] Description set: OOZIE-2896
Archiving artifacts
[Fast Archiver] Compressed 2.18 MB of artifacts by 53.0% relative to #137
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (OOZIE-2896) Ensure compatibility for existing LauncherMapper settings


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

Hadoop QA commented on OOZIE-2896:
--

Testing JIRA OOZIE-2896

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 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 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 [core].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [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/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {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 [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2047
.Tests rerun: 54
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}

{color:red}. There is at least one warning, please check{color}

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

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

> Ensure compatibility for existing LauncherMapper settings
> -
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2896.001.patch, OOZIE-2896.002.patch, 
> OOZIE-2896.002.patch, OOZIE-2896.003.patch, OOZIE-2896.004.patch, 
> OOZIE-2896.005.patch, OOZIE-2896.006.patch, OOZIE-2896.007.patch, 
> OOZIE-2896.008.patch
>
>
> There are a couple of LauncherMapper settings that we should support for 
> backward compatibility reasons.
> For example, {{oozie.launcher.mapreduce.map.memory.mb}}, 
> {{mapred.child.env}}, {{mapred.map.env}}, etc.
> We also have to discuss the list of properties we're going to support, since 
> there are many of them.
> List of hadoop properties under this task:
> mapreduce.job.queuename
> mapreduce.map.memory.mb
> mapreduce.map.java.opts
> mapreduce.map.env
> mapreduce.job.priority
> yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms
> yarn.app.mapreduce.am.resource.mb
> yarn.app.mapreduce.am.command-opts
> yarn.app.mapreduce.am.env
> ACL related properties should go under OOZIE-2897:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



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

[jira] [Comment Edited] (OOZIE-3098) Allow to use the rest api to get the creation time of the Coordinator

2017-10-27 Thread Chi Wen (JIRA)


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

Chi Wen edited comment on OOZIE-3098 at 10/27/17 12:07 PM:
---

Hi, [~andras.piros]:
There is no assign button which I think that I don't have the permission to 
assign;

In {noformat}WebServicesAPI.twiki{noformat}, it said that request 
{noformat}/oozie/v1/jobs?filter=user%3Dbansalm=1=50=GMT{noformat},
 the coordinator type will Response {noformat}createdTime{noformat}, but in my 
test there is no {noformat}createdTime{noformat}field, so I add it in this 
patch;


was (Author: chiwen):
Hi, [~andras.piros]:
There is no assign button which I think that I don't have the permission to 
assign;

In 
{noformat}
WebServicesAPI.twiki
{noformat},
 it said that request 
{noformat}
/oozie/v1/jobs?filter=user%3Dbansalm=1=50=GMT
{noformat}
 , the coordinator type will Response 
{noformat}
createdTime
{noformat}
, but in my test there is no 
{noformat}
createdTime
{noformat}
 field;

> Allow to use the rest api to get the creation time of the Coordinator
> -
>
> Key: OOZIE-3098
> URL: https://issues.apache.org/jira/browse/OOZIE-3098
> Project: Oozie
>  Issue Type: Improvement
>  Components: coordinator
>Reporter: Chi Wen
> Attachments: OOZIE-3098-001.patch
>
>
> It seems that the rest api cannot get the creation time of the Coordinator;
> RB link: https://reviews.apache.org/r/63296/



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

[jira] [Updated] (OOZIE-3098) Allow to use the rest api to get the creation time of the Coordinator

2017-10-27 Thread Chi Wen (JIRA)


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

Chi Wen updated OOZIE-3098:
---
Attachment: OOZIE-3098-001.patch

Hi, [~andras.piros]:
There is no assign button which I think that I don't have the permission to 
assign;

In 
{noformat}
WebServicesAPI.twiki
{noformat},
 it said that request 
{noformat}
/oozie/v1/jobs?filter=user%3Dbansalm=1=50=GMT
{noformat}
 , the coordinator type will Response 
{noformat}
createdTime
{noformat}
, but in my test there is no 
{noformat}
createdTime
{noformat}
 field;

> Allow to use the rest api to get the creation time of the Coordinator
> -
>
> Key: OOZIE-3098
> URL: https://issues.apache.org/jira/browse/OOZIE-3098
> Project: Oozie
>  Issue Type: Improvement
>  Components: coordinator
>Reporter: Chi Wen
> Attachments: OOZIE-3098-001.patch
>
>
> It seems that the rest api cannot get the creation time of the Coordinator;
> RB link: https://reviews.apache.org/r/63296/



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

[jira] [Commented] (OOZIE-2929) Coordinator SLA should support configuration variable

2017-10-27 Thread Chi Wen (JIRA)


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

Chi Wen commented on OOZIE-2929:


I think this warning is not my modify field, can anyone tell me how to solve it;

> Coordinator SLA should support configuration variable
> -
>
> Key: OOZIE-2929
> URL: https://issues.apache.org/jira/browse/OOZIE-2929
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 4.3.0
>Reporter: Chi Wen
> Attachments: OOZIE-2929-001.patch, OOZIE-2929-002.patch
>
>
> if coordinator.xml define SLA like this:
>   
> ${nominal_time}
> ${ 1 * HOURS}
> ${1 * MINUTES}
>   
> In job.properties define: nominal_time=${coord:nominalTime()}
> Then coordinator will run failed for "Coord Job Materialization Error: Could 
> not parse [${coord:nominalTime()}] using [-MM-dd'T'HH:mm+0800] mask";
> Oozie should support use define a variable for SLA;



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

Failed: OOZIE-2929 PreCommit Build #139

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.59 MB...]
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +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 [tools].
 +1 There are no new bugs found in [examples].
+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: 2042
Tests failed: 0
Tests errors: 1

The patch failed the following testcases:

  

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/139/

  % 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  57920 0   6461  0  0:09:47 --:--:--  0:09:47  
6461100 3706k  100 3706k0 0  3338k  0  0:00:01  0:00:01 --:--:-- 
16.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-2929
Archiving artifacts
[Fast Archiver] Compressed 1.80 MB of artifacts by 46.9% relative to #137
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 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 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at

[jira] [Commented] (OOZIE-2929) Coordinator SLA should support configuration variable


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

Hadoop QA commented on OOZIE-2929:
--

Testing JIRA OOZIE-2929

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 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 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 [core].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2042
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

.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/139/

> Coordinator SLA should support configuration variable
> -
>
> Key: OOZIE-2929
> URL: https://issues.apache.org/jira/browse/OOZIE-2929
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 4.3.0
>Reporter: Chi Wen
> Attachments: OOZIE-2929-001.patch, OOZIE-2929-002.patch
>
>
> if coordinator.xml define SLA like this:
>   
> ${nominal_time}
> ${ 1 * HOURS}
> ${1 * MINUTES}
>   
> In job.properties define: nominal_time=${coord:nominalTime()}
> Then coordinator will run failed for "Coord Job Materialization Error: Could 
> not parse [${coord:nominalTime()}] using [-MM-dd'T'HH:mm+0800] mask";
> Oozie should support use define a variable for SLA;



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

Re: Review Request 62936: OOZIE-2896 Ensure compatibility for existing LauncherMapper settings

2017-10-27 Thread Peter Bacsko via Review Board


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


Ship it!




- Peter Bacsko


On okt. 27, 2017, 10:01 de, András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62936/
> ---
> 
> (Updated okt. 27, 2017, 10:01 de)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Cseh, and Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2896 Ensure compatibility for existing LauncherMapper settings
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 76d0daa4f7528de6fb3c8993bae4dd28b6f7865b 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/LauncherConfigurationInjector.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/service/ConfigurationService.java 
> a51933022c14ea4ce06a65cc3c123bed8a8f7f34 
>   core/src/main/resources/oozie-default.xml 
> 9ba8fd4a0d9dd5f0bd6a64af3724c2f910d86457 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> a7bd357f8938d148a150db43135a7a8fe7f0da4c 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
>  PRE-CREATION 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
> ee1a32ac9b071009e1dbe78396520d778f58bddc 
> 
> 
> Diff: https://reviews.apache.org/r/62936/diff/6/
> 
> 
> Testing
> ---
> 
> JUnit tests:
> 
> * `TestJavaActionExecutor`
> * `TestLauncherConfigurationFilter`
> 
> Functional tests: submit and run `examples/apps/java-main/workflow.xml` in 
> three modes:
> 
> * only `oozie.launcher.` parameters are present: `oozie.launcher.` parameters 
> are passed through
> * `oozie.launcher.` and override (`yarn.`, `mapreduce.`, and `mapred.`) 
> parameters are also present: `oozie.launcher.` parameters are passed through
> * only override (`yarn.`, `mapreduce.`, and `mapred.`) parameters are 
> present: override parameters are passed through
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Commented] (OOZIE-2896) Ensure compatibility for existing LauncherMapper settings

2017-10-27 Thread Peter Bacsko (JIRA)


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

Peter Bacsko commented on OOZIE-2896:
-

+1

> Ensure compatibility for existing LauncherMapper settings
> -
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2896.001.patch, OOZIE-2896.002.patch, 
> OOZIE-2896.002.patch, OOZIE-2896.003.patch, OOZIE-2896.004.patch, 
> OOZIE-2896.005.patch, OOZIE-2896.006.patch, OOZIE-2896.007.patch, 
> OOZIE-2896.008.patch
>
>
> There are a couple of LauncherMapper settings that we should support for 
> backward compatibility reasons.
> For example, {{oozie.launcher.mapreduce.map.memory.mb}}, 
> {{mapred.child.env}}, {{mapred.map.env}}, etc.
> We also have to discuss the list of properties we're going to support, since 
> there are many of them.
> List of hadoop properties under this task:
> mapreduce.job.queuename
> mapreduce.map.memory.mb
> mapreduce.map.java.opts
> mapreduce.map.env
> mapreduce.job.priority
> yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms
> yarn.app.mapreduce.am.resource.mb
> yarn.app.mapreduce.am.command-opts
> yarn.app.mapreduce.am.env
> ACL related properties should go under OOZIE-2897:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



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

[jira] [Commented] (OOZIE-2896) Ensure compatibility for existing LauncherMapper settings

2017-10-27 Thread Peter Bacsko (JIRA)


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

Peter Bacsko commented on OOZIE-2896:
-

I'll do a final round of review and if it's OK, I'll +1 it too.

> Ensure compatibility for existing LauncherMapper settings
> -
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2896.001.patch, OOZIE-2896.002.patch, 
> OOZIE-2896.002.patch, OOZIE-2896.003.patch, OOZIE-2896.004.patch, 
> OOZIE-2896.005.patch, OOZIE-2896.006.patch, OOZIE-2896.007.patch, 
> OOZIE-2896.008.patch
>
>
> There are a couple of LauncherMapper settings that we should support for 
> backward compatibility reasons.
> For example, {{oozie.launcher.mapreduce.map.memory.mb}}, 
> {{mapred.child.env}}, {{mapred.map.env}}, etc.
> We also have to discuss the list of properties we're going to support, since 
> there are many of them.
> List of hadoop properties under this task:
> mapreduce.job.queuename
> mapreduce.map.memory.mb
> mapreduce.map.java.opts
> mapreduce.map.env
> mapreduce.job.priority
> yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms
> yarn.app.mapreduce.am.resource.mb
> yarn.app.mapreduce.am.command-opts
> yarn.app.mapreduce.am.env
> ACL related properties should go under OOZIE-2897:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



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

Failed: OOZIE-2296 PreCommit Build #138

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.60 MB...]
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +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/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/streaming].
 0 There are [3] new bugs found in [tools] that would be nice to have fixed.
 You can find the FindBugs diff here: tools/findbugs-new.html
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2056
Tests failed: 0
Tests errors: 1

The patch failed the following testcases:

  

Tests failing with errors:
  testStoreLastWorkflows(org.apache.oozie.tools.diag.TestAppInfoCollector)

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

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

test-patch exit code: 1

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



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.oozie.tools.diag.TestAppInfoCollector.testStoreLastWorkflows

Error Message:
null

Stack Trace:
java.lang.NullPointerException
at java.io.Writer.write(Writer.java:157)
at 
org.apache.oozie.tools.diag.DiagBundleEntryWriter.writeString(DiagBundleEntryWriter.java:85)
at 
org.apache.oozie.tools.diag.AppInfoCollector.persistWorkflowDefinition(AppInfoCollector.java:364)
at 
org.apache.oozie.tools.diag.AppInfoCollector.persistResolvedActionDefinition(AppInfoCollector.java:159)
at 
org.apache.oozie.tools.diag.AppInfoCollector.persistWorkflowJobInfo(AppInfoCollector.java:138)
at 
org.apache.oozie.tools.diag.AppInfoCollector.storeWorkflowJobDetails(AppInfoCollector.java:76)
at 
org.apache.oozie.tools.diag.AppInfoCollector.storeLastWorkflows(AppInfoCollector.java:376)
at 
org.apache.oozie.tools.diag.TestAppInfoCollector.testStoreLastWorkflows(TestAppInfoCollector.java:121)
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 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at

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


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

Hadoop QA commented on OOZIE-2296:
--

Testing JIRA OOZIE-2296

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 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} 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:orange}0{color} There are [3] new bugs found in total that would be nice 
to have fixed.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:orange}0{color} There are [3] new bugs found in [tools] that would be 
nice to have fixed.
. You can find the FindBugs diff here: tools/findbugs-new.html
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2056
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

.Tests failing with errors:
.  testStoreLastWorkflows(org.apache.oozie.tools.diag.TestAppInfoCollector)

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

> 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
>
>
> 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

[jira] [Commented] (OOZIE-2896) Ensure compatibility for existing LauncherMapper settings


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

Peter Cseh commented on OOZIE-2896:
---

+1 (pending jenkins) for patch 8

> Ensure compatibility for existing LauncherMapper settings
> -
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2896.001.patch, OOZIE-2896.002.patch, 
> OOZIE-2896.002.patch, OOZIE-2896.003.patch, OOZIE-2896.004.patch, 
> OOZIE-2896.005.patch, OOZIE-2896.006.patch, OOZIE-2896.007.patch, 
> OOZIE-2896.008.patch
>
>
> There are a couple of LauncherMapper settings that we should support for 
> backward compatibility reasons.
> For example, {{oozie.launcher.mapreduce.map.memory.mb}}, 
> {{mapred.child.env}}, {{mapred.map.env}}, etc.
> We also have to discuss the list of properties we're going to support, since 
> there are many of them.
> List of hadoop properties under this task:
> mapreduce.job.queuename
> mapreduce.map.memory.mb
> mapreduce.map.java.opts
> mapreduce.map.env
> mapreduce.job.priority
> yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms
> yarn.app.mapreduce.am.resource.mb
> yarn.app.mapreduce.am.command-opts
> yarn.app.mapreduce.am.env
> ACL related properties should go under OOZIE-2897:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



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

Re: Review Request 62936: OOZIE-2896 Ensure compatibility for existing LauncherMapper settings

2017-10-27 Thread Peter Cseh via Review Board


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


Ship it!




Ship It!

- Peter Cseh


On Oct. 27, 2017, 10:01 a.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62936/
> ---
> 
> (Updated Oct. 27, 2017, 10:01 a.m.)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Cseh, and Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2896 Ensure compatibility for existing LauncherMapper settings
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 76d0daa4f7528de6fb3c8993bae4dd28b6f7865b 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/LauncherConfigurationInjector.java
>  PRE-CREATION 
>   core/src/main/java/org/apache/oozie/service/ConfigurationService.java 
> a51933022c14ea4ce06a65cc3c123bed8a8f7f34 
>   core/src/main/resources/oozie-default.xml 
> 9ba8fd4a0d9dd5f0bd6a64af3724c2f910d86457 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> a7bd357f8938d148a150db43135a7a8fe7f0da4c 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
>  PRE-CREATION 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
> ee1a32ac9b071009e1dbe78396520d778f58bddc 
> 
> 
> Diff: https://reviews.apache.org/r/62936/diff/6/
> 
> 
> Testing
> ---
> 
> JUnit tests:
> 
> * `TestJavaActionExecutor`
> * `TestLauncherConfigurationFilter`
> 
> Functional tests: submit and run `examples/apps/java-main/workflow.xml` in 
> three modes:
> 
> * only `oozie.launcher.` parameters are present: `oozie.launcher.` parameters 
> are passed through
> * `oozie.launcher.` and override (`yarn.`, `mapreduce.`, and `mapred.`) 
> parameters are also present: `oozie.launcher.` parameters are passed through
> * only override (`yarn.`, `mapreduce.`, and `mapred.`) parameters are 
> present: override parameters are passed through
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Updated] (OOZIE-2896) Ensure compatibility for existing LauncherMapper settings


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

Andras Piros updated OOZIE-2896:

Attachment: OOZIE-2896.008.patch

Last (?) review round.

> Ensure compatibility for existing LauncherMapper settings
> -
>
> Key: OOZIE-2896
> URL: https://issues.apache.org/jira/browse/OOZIE-2896
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2896.001.patch, OOZIE-2896.002.patch, 
> OOZIE-2896.002.patch, OOZIE-2896.003.patch, OOZIE-2896.004.patch, 
> OOZIE-2896.005.patch, OOZIE-2896.006.patch, OOZIE-2896.007.patch, 
> OOZIE-2896.008.patch
>
>
> There are a couple of LauncherMapper settings that we should support for 
> backward compatibility reasons.
> For example, {{oozie.launcher.mapreduce.map.memory.mb}}, 
> {{mapred.child.env}}, {{mapred.map.env}}, etc.
> We also have to discuss the list of properties we're going to support, since 
> there are many of them.
> List of hadoop properties under this task:
> mapreduce.job.queuename
> mapreduce.map.memory.mb
> mapreduce.map.java.opts
> mapreduce.map.env
> mapreduce.job.priority
> yarn.app.mapreduce.am.scheduler.heartbeat.interval-ms
> yarn.app.mapreduce.am.resource.mb
> yarn.app.mapreduce.am.command-opts
> yarn.app.mapreduce.am.env
> ACL related properties should go under OOZIE-2897:
> mapreduce.job.acl-view-job
> mapreduce.job.acl-modfy-job



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

Re: Review Request 62936: OOZIE-2896 Ensure compatibility for existing LauncherMapper settings


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

(Updated Oct. 27, 2017, 10:01 a.m.)


Review request for oozie, Attila Sasvari, Peter Cseh, and Peter Bacsko.


Changes
---

Last (?) review round.


Repository: oozie-git


Description
---

OOZIE-2896 Ensure compatibility for existing LauncherMapper settings


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
76d0daa4f7528de6fb3c8993bae4dd28b6f7865b 
  
core/src/main/java/org/apache/oozie/action/hadoop/LauncherConfigurationInjector.java
 PRE-CREATION 
  core/src/main/java/org/apache/oozie/service/ConfigurationService.java 
a51933022c14ea4ce06a65cc3c123bed8a8f7f34 
  core/src/main/resources/oozie-default.xml 
9ba8fd4a0d9dd5f0bd6a64af3724c2f910d86457 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
a7bd357f8938d148a150db43135a7a8fe7f0da4c 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherConfigurationInjector.java
 PRE-CREATION 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
ee1a32ac9b071009e1dbe78396520d778f58bddc 


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

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


Testing
---

JUnit tests:

* `TestJavaActionExecutor`
* `TestLauncherConfigurationFilter`

Functional tests: submit and run `examples/apps/java-main/workflow.xml` in 
three modes:

* only `oozie.launcher.` parameters are present: `oozie.launcher.` parameters 
are passed through
* `oozie.launcher.` and override (`yarn.`, `mapreduce.`, and `mapred.`) 
parameters are also present: `oozie.launcher.` parameters are passed through
* only override (`yarn.`, `mapreduce.`, and `mapred.`) parameters are present: 
override parameters are passed through


Thanks,

András Piros

Re: Review Request 62936: OOZIE-2896 Ensure compatibility for existing LauncherMapper settings