[jira] Subscription: Oozie Patch Available

2017-07-28 Thread jira
Issue Subscription
Filter: Oozie Patch Available (110 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2987  Coord action missing dependencies should show URI template with 
unresolved dependencies
https://issues-test.apache.org/jira/browse/OOZIE-2987
OOZIE-2980  JAXB Proof of Concept
https://issues-test.apache.org/jira/browse/OOZIE-2980
OOZIE-2978  Remove code that handles Pig versions before 0.8 
https://issues-test.apache.org/jira/browse/OOZIE-2978
OOZIE-2977  error: self-closing element not allowed
https://issues-test.apache.org/jira/browse/OOZIE-2977
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues-test.apache.org/jira/browse/OOZIE-2975
OOZIE-2974  Change TestLiteWorkflowAppParser so that it works with Hadoop 3
https://issues-test.apache.org/jira/browse/OOZIE-2974
OOZIE-2969  Drop support for Java 1.7
https://issues-test.apache.org/jira/browse/OOZIE-2969
OOZIE-2964  getting at 
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
https://issues-test.apache.org/jira/browse/OOZIE-2964
OOZIE-2963  getting error in build ArtifactNotFoundException: Could not find 
artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
https://issues-test.apache.org/jira/browse/OOZIE-2963
OOZIE-2962  bump maven-javadoc-plugin to 2.10.4
https://issues-test.apache.org/jira/browse/OOZIE-2962
OOZIE-2961  build contains multiple warnings for is not a parameter name
https://issues-test.apache.org/jira/browse/OOZIE-2961
OOZIE-2960  many warnings for @return tag has no arguments
https://issues-test.apache.org/jira/browse/OOZIE-2960
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues-test.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues-test.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues-test.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues-test.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues-test.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues-test.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues-test.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues-test.apache.org/jira/browse/OOZIE-2934
OOZIE-2931  multiple warnings during build for "no @param for"
https://issues-test.apache.org/jira/browse/OOZIE-2931
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues-test.apache.org/jira/browse/OOZIE-2927
OOZIE-2916  Set a job name for the MR Action's child job
https://issues-test.apache.org/jira/browse/OOZIE-2916
OOZIE-2914  Consolidate Trim 
https://issues-test.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues-test.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues-test.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues-test.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues-test.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues-test.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues-test.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues-test.apache.org/jira/browse/OOZIE-2826
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues-test.apache.org/jira/browse/OOZIE-2812
OOZIE-

[jira] Subscription: Oozie Patch Available

2017-07-28 Thread jira
Issue Subscription
Filter: Oozie Patch Available (115 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3009  Number of Oozie tests executed dropped after OOZIE-2854
https://issues.apache.org/jira/browse/OOZIE-3009
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-3001  core library has many instances of warnings with trailing spaces 
and lines longer than 132 chars
https://issues.apache.org/jira/browse/OOZIE-3001
OOZIE-2999  minioozie can't compile
https://issues.apache.org/jira/browse/OOZIE-2999
OOZIE-2997  files contain trailing white spaces in client lib
https://issues.apache.org/jira/browse/OOZIE-2997
OOZIE-2996  add option for -UseGCOverheadLimit to maven opts as sometimes local 
testing fails
https://issues.apache.org/jira/browse/OOZIE-2996
OOZIE-2980  JAXB Proof of Concept
https://issues.apache.org/jira/browse/OOZIE-2980
OOZIE-2978  Remove code that handles Pig versions before 0.8 
https://issues.apache.org/jira/browse/OOZIE-2978
OOZIE-2977  error: self-closing element not allowed
https://issues.apache.org/jira/browse/OOZIE-2977
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2974  Change TestLiteWorkflowAppParser so that it works with Hadoop 3
https://issues.apache.org/jira/browse/OOZIE-2974
OOZIE-2969  Drop support for Java 1.7
https://issues.apache.org/jira/browse/OOZIE-2969
OOZIE-2964  getting at 
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
https://issues.apache.org/jira/browse/OOZIE-2964
OOZIE-2963  getting error in build ArtifactNotFoundException: Could not find 
artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
https://issues.apache.org/jira/browse/OOZIE-2963
OOZIE-2962  bump maven-javadoc-plugin to 2.10.4
https://issues.apache.org/jira/browse/OOZIE-2962
OOZIE-2961  build contains multiple warnings for is not a parameter name
https://issues.apache.org/jira/browse/OOZIE-2961
OOZIE-2960  many warnings for @return tag has no arguments
https://issues.apache.org/jira/browse/OOZIE-2960
OOZIE-2958  TestLauncherAM fails in Share Lib Oozie
https://issues.apache.org/jira/browse/OOZIE-2958
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2931  multiple warnings during build for "no @param for"
https://issues.apache.org/jira/browse/OOZIE-2931
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2916  Set a job name for the MR Action's child job
https://issues.apache.org/jira/browse/OOZIE-2916
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow hea

[jira] [Commented] (OOZIE-2977) error: self-closing element not allowed

2017-07-28 Thread Artem Ervits (JIRA)

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

Artem Ervits commented on OOZIE-2977:
-

[~gezapeti] I have multiple jiras open to address the issues you're referring 
to:

https://issues.apache.org/jira/browse/OOZIE-2931
https://issues.apache.org/jira/browse/OOZIE-3001
https://issues.apache.org/jira/browse/OOZIE-2997
https://issues.apache.org/jira/browse/OOZIE-2975
https://issues.apache.org/jira/browse/OOZIE-2964
https://issues.apache.org/jira/browse/OOZIE-2963
https://issues.apache.org/jira/browse/OOZIE-2962
https://issues.apache.org/jira/browse/OOZIE-2961
https://issues.apache.org/jira/browse/OOZIE-2960

would appreciate the reviews and +1s

> error: self-closing element not allowed
> ---
>
> Key: OOZIE-2977
> URL: https://issues.apache.org/jira/browse/OOZIE-2977
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2977-0.patch
>
>
> compiling with Java 1.8, javadoc throws the following errors
> {noformat}
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> {noformat}



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


[jira] [Commented] (OOZIE-2272) Use Hadoop's CredentialProvider for passwords in oozie-site

2017-07-28 Thread Robert Kanter (JIRA)

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

Robert Kanter commented on OOZIE-2272:
--

Oops, I guess I missed that spot.  Let's create a new JIRA and not an amendment 
patch because this issue was already in a release.

> Use Hadoop's CredentialProvider for passwords in oozie-site
> ---
>
> Key: OOZIE-2272
> URL: https://issues.apache.org/jira/browse/OOZIE-2272
> Project: Oozie
>  Issue Type: Improvement
>  Components: security
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2272.001.patch
>
>
> We have a few passwords in oozie-site:
> - {{oozie.email.smtp.password}}
> - {{oozie.service.JPAService.jdbc.password}}
> It would be good if we supported Hadoop's {{CredentialProvider}} so that the 
> passwords can be specified in an external encrypted file.  The file can be 
> prepared as described 
> [here|http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/CommandsManual.html#credential]
>  in the Hadoop docs.



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


[jira] [Commented] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2958:
--

Testing JIRA OOZIE-2958

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 78 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{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/oozie-trunk-precommit-build/4003/

> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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

Build failed in Jenkins: oozie-trunk-precommit-build #4003

2017-07-28 Thread Apache Jenkins Server
See 


Changes:

[gezapeti] OOZIE-2910 Re-add testChildKill and adapt it to OYA (pbacsko and

[gezapeti] OOZIE-2984 Parse spark-defaults.conf values with spaces without 
needing

--
[...truncated 1.51 MB...]
[INFO] Copying metrics-graphite-3.1.2.jar to 

[INFO] Copying hadoop-auth-2.6.0.jar to 

[INFO] Copying hive-webhcat-java-client-1.2.0.jar to 

[INFO] Copying javax.annotation-api-1.2.jar to 

[INFO] Copying slf4j-log4j12-1.6.6.jar to 

[INFO] Copying jackson-core-2.4.2.jar to 

[INFO] Copying postgresql-9.0-801.jdbc4.jar to 

[INFO] Copying datanucleus-rdbms-3.2.9.jar to 

[INFO] Copying jettison-1.1.jar to 

[INFO] Copying guice-servlet-3.0.jar to 

[INFO] Copying ant-launcher-1.9.1.jar to 

[INFO] Copying jpam-1.1.jar to 

[INFO] Copying hive-service-1.2.0.jar to 

[INFO] Copying hive-hcatalog-server-extensions-1.2.0.jar to 

[INFO] Copying hadoop-mapreduce-client-core-2.6.0.jar to 

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

[INFO] Copying jetty-util-9.2.19.v20160908.jar to 

[INFO] Copying apache-curator-2.6.0.pom to 

[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-server ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 5.0.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 


[jira] [Comment Edited] (OOZIE-3009) Number of Oozie tests executed dropped after OOZIE-2854

2017-07-28 Thread Andras Piros (JIRA)

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

Andras Piros edited comment on OOZIE-3009 at 7/28/17 3:37 PM:
--

It seems that running the tests w/ Oracle JDK 1.8 in the Apache cloud or 
locally, or OpenJDK 1.7 locally, or Oracle JDK 1.7 locally, all the tests are 
run correctly w/ the patch:
{noformat}
mvn clean test -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true 
-fae -Doozie.test.waitfor.ratio=3 -Dtest.timeout=7200
{noformat}

[~asasvari] can you please review?


was (Author: andras.piros):
It seems that running the tests w/ Oracle JDK 1.8, and OpenJDK 1.7, all the 
tests are run correctly w/ the patch:
{noformat}
mvn clean test -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true 
-fae -Doozie.test.waitfor.ratio=3 -Dtest.timeout=7200
{noformat}

[~asasvari] can you please review?

> Number of Oozie tests executed dropped after OOZIE-2854
> ---
>
> Key: OOZIE-3009
> URL: https://issues.apache.org/jira/browse/OOZIE-3009
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-3009.001.patch
>
>
> I noticed that the number of executed tests has been significantly dropped 
> after OOZIE-2854.
> - Tests run: *1080* https://issues.apache.org/jira/browse/OOZIE-2854
> Previous tests:
> - OOZIE-2371 - Tests run: *1965* 
> https://issues.apache.org/jira/browse/OOZIE-2371?focusedCommentId=16076996&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16076996
> - OOZIE-2911 - Tests run: *1966* 
> https://issues.apache.org/jira/browse/OOZIE-2911?focusedCommentId=16078078&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16078078
> In OOZIE-2854, we can also see that the number of test cases vary from patch 
> to patch.



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


[jira] [Commented] (OOZIE-3009) Number of Oozie tests executed dropped after OOZIE-2854

2017-07-28 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-3009:
-

It seems that running the tests w/ Oracle JDK 1.8, and OpenJDK 1.7, all the 
tests are run correctly w/ the patch:
{noformat}
mvn clean test -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true 
-fae -Doozie.test.waitfor.ratio=3 -Dtest.timeout=7200
{noformat}

[~asasvari] can you please review?

> Number of Oozie tests executed dropped after OOZIE-2854
> ---
>
> Key: OOZIE-3009
> URL: https://issues.apache.org/jira/browse/OOZIE-3009
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-3009.001.patch
>
>
> I noticed that the number of executed tests has been significantly dropped 
> after OOZIE-2854.
> - Tests run: *1080* https://issues.apache.org/jira/browse/OOZIE-2854
> Previous tests:
> - OOZIE-2371 - Tests run: *1965* 
> https://issues.apache.org/jira/browse/OOZIE-2371?focusedCommentId=16076996&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16076996
> - OOZIE-2911 - Tests run: *1966* 
> https://issues.apache.org/jira/browse/OOZIE-2911?focusedCommentId=16078078&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16078078
> In OOZIE-2854, we can also see that the number of test cases vary from patch 
> to patch.



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


Review Request 61216: Fix of a possible NPE found by AppChecker

2017-07-28 Thread Denes Bodo

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

Review request for oozie.


Bugs: OOZIE-2940
https://issues.apache.org/jira/browse/OOZIE-2940


Repository: oozie-git


Description
---

Possible NullPointerException


Diffs
-

  core/src/main/java/org/apache/oozie/WorkflowActionBean.java 974c52b 


Diff: https://reviews.apache.org/r/61216/diff/1/


Testing
---

To be provided.


Thanks,

Denes Bodo



[jira] [Commented] (OOZIE-2977) error: self-closing element not allowed

2017-07-28 Thread Artem Ervits (JIRA)

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

Artem Ervits commented on OOZIE-2977:
-

[~gezapeti] please provide steps to reproduce

> error: self-closing element not allowed
> ---
>
> Key: OOZIE-2977
> URL: https://issues.apache.org/jira/browse/OOZIE-2977
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2977-0.patch
>
>
> compiling with Java 1.8, javadoc throws the following errors
> {noformat}
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> {noformat}



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


Build failed in Jenkins: oozie-trunk-precommit-build #4002

2017-07-28 Thread Apache Jenkins Server
See 


Changes:

[asasvari] OOZIE-2995 In preparation for Java 8, remove MaxPermSize=512m (Artem

--
[...truncated 1.51 MB...]
[INFO] Copying metrics-graphite-3.1.2.jar to 

[INFO] Copying hadoop-auth-2.6.0.jar to 

[INFO] Copying hive-webhcat-java-client-1.2.0.jar to 

[INFO] Copying javax.annotation-api-1.2.jar to 

[INFO] Copying slf4j-log4j12-1.6.6.jar to 

[INFO] Copying jackson-core-2.4.2.jar to 

[INFO] Copying postgresql-9.0-801.jdbc4.jar to 

[INFO] Copying datanucleus-rdbms-3.2.9.jar to 

[INFO] Copying jettison-1.1.jar to 

[INFO] Copying guice-servlet-3.0.jar to 

[INFO] Copying ant-launcher-1.9.1.jar to 

[INFO] Copying jpam-1.1.jar to 

[INFO] Copying hive-service-1.2.0.jar to 

[INFO] Copying hive-hcatalog-server-extensions-1.2.0.jar to 

[INFO] Copying hadoop-mapreduce-client-core-2.6.0.jar to 

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

[INFO] Copying jetty-util-9.2.19.v20160908.jar to 

[INFO] Copying apache-curator-2.6.0.pom to 

[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-server ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 5.0.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 


[jira] [Commented] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2958:
--

Testing JIRA OOZIE-2958

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 78 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{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/oozie-trunk-precommit-build/4002/

> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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

[jira] [Assigned] (OOZIE-2940) Possible NullPointerException

2017-07-28 Thread Denes Bodo (JIRA)

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

Denes Bodo reassigned OOZIE-2940:
-

Assignee: Denes Bodo

> Possible NullPointerException
> -
>
> Key: OOZIE-2940
> URL: https://issues.apache.org/jira/browse/OOZIE-2940
> Project: Oozie
>  Issue Type: Bug
>  Components: workflow
>Affects Versions: 4.3.0
>Reporter: AppChecker
>Assignee: Denes Bodo
>  Labels: appchecker, static-analysis
>
> Hi.
> In [this 
> code|https://github.com/apache/oozie/blob/eb168360c550943828d9fe2c7bfdcd4f5e830003/core/src/main/java/org/apache/oozie/WorkflowActionBean.java#L600]:
> {code:java}
> if (status == null || (status != Status.OK && status != Status.ERROR 
> && status != Status.KILLED)) {
> throw new IllegalArgumentException("Action status must be OK, 
> ERROR or KILLED. Received ["
> + status.toString() + "]");
> }
> {code}
> if status is null, status.toString() will be executed, so 
> NullPointerException will be throw.
> This possible defect found by 
> [AppChecker|https://npo-echelon.ru/en/solutions/appchecker.php].



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


[jira] [Commented] (OOZIE-2977) error: self-closing element not allowed

2017-07-28 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2977:
---

The Java8 run in OOZIE-2969 says that there are 78 Javadoc warning(s) in the 
current head with Java8. Can you check on them?

> error: self-closing element not allowed
> ---
>
> Key: OOZIE-2977
> URL: https://issues.apache.org/jira/browse/OOZIE-2977
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2977-0.patch
>
>
> compiling with Java 1.8, javadoc throws the following errors
> {noformat}
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java:464:
>  error: self-closing element not allowed
> /Users/aervits/NetBeansProjects/OOZIE-JAVADOC/oozie/core/src/main/java/org/apache/oozie/util/DateUtils.java:209:
>  error: self-closing element not allowed
> {noformat}



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


[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

2017-07-28 Thread Artem Ervits (JIRA)

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

Artem Ervits commented on OOZIE-2969:
-

[~gezapeti] test is unrelated, passes locally.

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2969-0.patch, OOZIE-2969-0.patch, 
> OOZIE-2969-1.patch, OOZIE-2969-2.patch, screenshot-1.png
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



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


Re: Review Request 60963: OOZIE-2984 Parse spark-defaults.conf values with spaces without needing the quotes

2017-07-28 Thread Peter Bacsko

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


Ship it!




Ship It!

- Peter Bacsko


On júl. 27, 2017, 1:20 du, András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60963/
> ---
> 
> (Updated júl. 27, 2017, 1:20 du)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Cseh, Peter Bacsko, and 
> Robert Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Parse `spark-defaults.conf` values with spaces without needing the quotes. 
> That is, quotes should not be mandatory but optional to retain backwards 
> compatibility.
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/DG_SparkActionExtension.twiki 
> 863bd89cf576d2fb7be76c61ca139218c33a5f66 
>   
> sharelib/spark/src/main/java/org/apache/oozie/action/hadoop/SparkOptionsSplitter.java
>  30def6f05b7a17b8ce66ed766a9d64c171796ac5 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkArgsExtractor.java
>  7db26a6b81083d7664bef8ff14c8e14df4572fc1 
>   
> sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestSparkOptionsSplitter.java
>  02786a2476fc981af77688a22aa9c3a8fc0cce2a 
> 
> 
> Diff: https://reviews.apache.org/r/60963/diff/5/
> 
> 
> Testing
> ---
> 
> Following tests are run:
> 
> * `TestSparkOptionsSplitter`
> * `TestSparkArgsExtractor`
> * `TestSparkMain`
> 
> 
> Thanks,
> 
> András Piros
> 
>



[jira] [Commented] (OOZIE-2984) Parse spark-defaults.conf values with spaces without needing the quotes

2017-07-28 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2984:
---

I think we can ignore this findbugs warning.
+1


> Parse spark-defaults.conf values with spaces without needing the quotes
> ---
>
> Key: OOZIE-2984
> URL: https://issues.apache.org/jira/browse/OOZIE-2984
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Fahd Siddiqui
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-2984.001.patch, OOZIE-2984.002.patch, 
> OOZIE-2984.003.patch, OOZIE-2984.004.patch, OOZIE-2984.005.patch
>
>
> Oozie requires multiple java opts to be enclosed in quotes. For example:
> {code}
> spark.driver.extraJavaOptions="-Xmn2703m -XX:SurvivorRatio=2 
> -XX:ParallelGCThreads=20"
> {code}
> However the above breaks spark-shell. 
> {code}
> $ ./spark2-shell
> Invalid initial young generation size: -Xmn2212m -XX:SurvivorRatio=2 
> -XX:ParallelGCThreads=20
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> To fix spark-shell, we have to remove the quotes, which errors out Oozie:
> {code}
> Error: Unrecognized option '-XX:SurvivorRatio=2'
> ...
> --conf
> spark.executor.extraJavaOptions=-Xmn2703m 
> -Dlog4j.configuration=spark-log4j.properties
> -XX:SurvivorRatio=2
> {code}
> Oozie should be able to parse spark-defaults.conf values with spaces without 
> needing the quotes.



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


[jira] [Commented] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2958:
---

+1 (pending jenkins)

> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> 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 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at 
> org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
> at 
> org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
> 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:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> testActionThrowsJavaMainException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsJavaMainException(TestLauncherAM.java:270)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

[jira] [Commented] (OOZIE-2910) Re-add testChildKill and adapt it to OYA

2017-07-28 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2910:
---

Committed to master! Also, I've fixed the release-log.txt [~asasvari], don't 
forget to update that thing too next time

> Re-add testChildKill and adapt it to OYA
> 
>
> Key: OOZIE-2910
> URL: https://issues.apache.org/jira/browse/OOZIE-2910
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Fix For: 5.0.0
>
> Attachments: OOZIE-2910-001.patch, OOZIE-2910-002.patch, 
> OOZIE-2910-003.patch
>
>
> Removed by OOZIE-1770: [link to the original 
> code|https://github.com/apache/oozie/blob/e0b7cde711b1b9e1a03660ec635041eeb9755049/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java#L546]



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


[jira] [Resolved] (OOZIE-2910) Re-add testChildKill and adapt it to OYA

2017-07-28 Thread Peter Cseh (JIRA)

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

Peter Cseh resolved OOZIE-2910.
---
   Resolution: Fixed
Fix Version/s: 5.0.0

> Re-add testChildKill and adapt it to OYA
> 
>
> Key: OOZIE-2910
> URL: https://issues.apache.org/jira/browse/OOZIE-2910
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Fix For: 5.0.0
>
> Attachments: OOZIE-2910-001.patch, OOZIE-2910-002.patch, 
> OOZIE-2910-003.patch
>
>
> Removed by OOZIE-1770: [link to the original 
> code|https://github.com/apache/oozie/blob/e0b7cde711b1b9e1a03660ec635041eeb9755049/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java#L546]



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


[jira] [Commented] (OOZIE-2910) Re-add testChildKill and adapt it to OYA

2017-07-28 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2910:
---

+1 thanks good catch!

> Re-add testChildKill and adapt it to OYA
> 
>
> Key: OOZIE-2910
> URL: https://issues.apache.org/jira/browse/OOZIE-2910
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
> Attachments: OOZIE-2910-001.patch, OOZIE-2910-002.patch, 
> OOZIE-2910-003.patch
>
>
> Removed by OOZIE-1770: [link to the original 
> code|https://github.com/apache/oozie/blob/e0b7cde711b1b9e1a03660ec635041eeb9755049/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java#L546]



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


[jira] [Updated] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Peter Bacsko (JIRA)

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

Peter Bacsko updated OOZIE-2958:

Attachment: OOZIE-2968-001.patch

> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
> Attachments: OOZIE-2968-001.patch
>
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> 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 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at 
> org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
> at 
> org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
> 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:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> testActionThrowsJavaMainException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsJavaMainException(TestLauncherAM.java:270)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.Delegatin

[jira] [Assigned] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Peter Bacsko (JIRA)

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

Peter Bacsko reassigned OOZIE-2958:
---

Assignee: Peter Bacsko

> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>Priority: Minor
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> 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 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at 
> org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
> at 
> org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
> 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:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> testActionThrowsJavaMainException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsJavaMainException(TestLauncherAM.java:270)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.

[jira] [Updated] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Peter Bacsko (JIRA)

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

Peter Bacsko updated OOZIE-2958:

Priority: Major  (was: Minor)

> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Assignee: Peter Bacsko
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> 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 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at 
> org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
> at 
> org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
> 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:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> testActionThrowsJavaMainException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsJavaMainException(TestLauncherAM.java:270)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess

[jira] [Commented] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Peter Bacsko (JIRA)

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

Peter Bacsko commented on OOZIE-2958:
-

[~pravindsilva] great finding! Will check this out.

> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Priority: Minor
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> 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 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at 
> org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
> at 
> org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
> 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:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> testActionThrowsJavaMainException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsJavaMainException(TestLauncherAM.java:270)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> s

[jira] [Commented] (OOZIE-2995) In preparation for Java 8, remove MaxPermSize=512m

2017-07-28 Thread Attila Sasvari (JIRA)

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

Attila Sasvari commented on OOZIE-2995:
---

+ 1 Thanks [~dbist13].
Committed to master!

> In preparation for Java 8, remove MaxPermSize=512m
> --
>
> Key: OOZIE-2995
> URL: https://issues.apache.org/jira/browse/OOZIE-2995
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2995-0.patch
>
>
> message on the console when executing with Java 8
> {noformat}
> *Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0*
> Concurrency config is parallel='classes', perCoreThreadCount=false, 
> threadCount=1, useUnlimitedThreads=false
> objc[13102]: Class JavaLaunchHelper is implemented in both 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/bin/java 
> (0x1045f24c0) and 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/lib/libinstrument.dylib
>  (0x10d9c34e0). One of the two will be used. Which one is undefined.
> {noformat}



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


[jira] [Updated] (OOZIE-2995) In preparation for Java 8, remove MaxPermSize=512m

2017-07-28 Thread Attila Sasvari (JIRA)

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

Attila Sasvari updated OOZIE-2995:
--
Summary: In preparation for Java 8, remove MaxPermSize=512m  (was: in 
preparation for Java 8, remove MaxPermSize=512m)

> In preparation for Java 8, remove MaxPermSize=512m
> --
>
> Key: OOZIE-2995
> URL: https://issues.apache.org/jira/browse/OOZIE-2995
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2995-0.patch
>
>
> message on the console when executing with Java 8
> {noformat}
> *Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
> support was removed in 8.0*
> Concurrency config is parallel='classes', perCoreThreadCount=false, 
> threadCount=1, useUnlimitedThreads=false
> objc[13102]: Class JavaLaunchHelper is implemented in both 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/bin/java 
> (0x1045f24c0) and 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/lib/libinstrument.dylib
>  (0x10d9c34e0). One of the two will be used. Which one is undefined.
> {noformat}



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


[jira] [Commented] (OOZIE-2958) TestLauncherAM fails in Share Lib Oozie

2017-07-28 Thread Pravin Dsilva (JIRA)

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

Pravin Dsilva commented on OOZIE-2958:
--

The test failures in TestLauncherAM  seems to be occuring only when 
TestLauncherMain runs before it. This is because of the  use of 
cleanUpStreams() in TestLauncherMain which sets System.setOut(null)

I suppose the solution here would be:
1. Avoid the use of System.out.print in LauncherAM 
2. Use System.setOut  in setup method of  TestLauncherAM



> TestLauncherAM fails in Share Lib Oozie
> ---
>
> Key: OOZIE-2958
> URL: https://issues.apache.org/jira/browse/OOZIE-2958
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: 5.0.0
> Environment: $ uname -a
> Linux hj-ibmibm9397 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Parita Johari
>Priority: Minor
>
> {code:java}
> ---
> Test set: org.apache.oozie.action.hadoop.TestLauncherAM
> ---
> Tests run: 22, Failures: 4, Errors: 18, Skipped: 0, Time elapsed: 0.288 sec 
> <<< FAILURE!
> testActionThrowsLauncherException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0.001 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.testActionThrowsLauncherException(TestLauncherAM.java:284)
> 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.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)
> 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 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at 
> org.mockito.internal.runners.JUnit45AndHigherRunnerImpl.run(JUnit45AndHigherRunnerImpl.java:37)
> at 
> org.mockito.runners.MockitoJUnitRunner.run(MockitoJUnitRunner.java:62)
> 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:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> testActionThrowsJavaMainException(org.apache.oozie.action.hadoop.TestLauncherAM)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException
> at 
> org.apache.oozie.action.hadoop.LauncherAM.updateActionDataWithFailure(LauncherAM.java:532)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:216)
> at 
> org.apache.oozie.action.hadoop.TestLauncherAM.executeLauncher(TestLauncherAM.java:519)
>  

[jira] [Commented] (OOZIE-2272) Use Hadoop's CredentialProvider for passwords in oozie-site

2017-07-28 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-2272:
-

[~h_o] to me it seems that you're right, this occurrence could also be replaced 
by {{ConfigurationService.getPassword()}} call. Please feel free to reopen the 
issue for an amendment patch / create a new issue to track that.

> Use Hadoop's CredentialProvider for passwords in oozie-site
> ---
>
> Key: OOZIE-2272
> URL: https://issues.apache.org/jira/browse/OOZIE-2272
> Project: Oozie
>  Issue Type: Improvement
>  Components: security
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-2272.001.patch
>
>
> We have a few passwords in oozie-site:
> - {{oozie.email.smtp.password}}
> - {{oozie.service.JPAService.jdbc.password}}
> It would be good if we supported Hadoop's {{CredentialProvider}} so that the 
> passwords can be specified in an external encrypted file.  The file can be 
> prepared as described 
> [here|http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/CommandsManual.html#credential]
>  in the Hadoop docs.



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