[jira] Subscription: Oozie Patch Available

2017-06-15 Thread jira
Issue Subscription
Filter: Oozie Patch Available (105 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2946  Include find-sec-bugs plugin
https://issues.apache.org/jira/browse/OOZIE-2946
OOZIE-2943  Fix Findbugs warnings in oozie-sharelib-pig
https://issues.apache.org/jira/browse/OOZIE-2943
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-2936  Fix Javadoc warnings from build
https://issues.apache.org/jira/browse/OOZIE-2936
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-2924  ./bin/mkdistro.sh reports a number instances of no @throws for 
Exception
https://issues.apache.org/jira/browse/OOZIE-2924
OOZIE-2920  Document Distcp can copy files within a cluster
https://issues.apache.org/jira/browse/OOZIE-2920
OOZIE-2918  Delete LauncherMapper and its test
https://issues.apache.org/jira/browse/OOZIE-2918
OOZIE-2911  Re-add test testWfActionKillChildJob and adapt it to OYA
https://issues.apache.org/jira/browse/OOZIE-2911
OOZIE-2902  org.apache.oozie.action.hadoop.TestJavaActionExecutor fails after 
hadoop 2.6 upgrade
https://issues.apache.org/jira/browse/OOZIE-2902
OOZIE-2884  consolidate hadoop versions in pomfiles
https://issues.apache.org/jira/browse/OOZIE-2884
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-2854  Oozie should handle transient DB problems
https://issues.apache.org/jira/browse/OOZIE-2854
OOZIE-2849  Fix build warnings when assembling directories
https://issues.apache.org/jira/browse/OOZIE-2849
OOZIE-2848  Override sharelib.tgz in distro when rebuilding Oozie
https://issues.apache.org/jira/browse/OOZIE-2848
OOZIE-2846  TestSSLServerConnectorFactory fails with Jetty 9.3 and 9.4
https://issues.apache.org/jira/browse/OOZIE-2846
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.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.apache.org/jira/browse/OOZIE-2826
OOZIE-2815  Oozie not always display job log
https://issues.apache.org/jira/browse/OOZIE-2815
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2796  oozie.action.keep.action.dir not getting noticed
https://issues.apache.org/jira/browse/OOZIE-2796
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend FS action to allow setrep on a file
https://issues.apache.org/jira/browse/OOZIE-2769
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.hadoop.security.AccessControlException
https://issues.apache.org/jira/browse/OOZIE-2733
OOZIE-2726  Flaky test due to daylight saving changes
h

[jira] [Commented] (OOZIE-2931) multiple warnings during build for "no @param for"

2017-06-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2931:
--

Testing JIRA OOZIE-2931

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:red}-1 JAVADOC{color}
.{color:red}-1{color} the patch seems to introduce 1 new Javadoc warning(s)
.{color:red}WARNING{color}: the current HEAD has 6 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 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: 1966
.Tests rerun: 18
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestHdfsOperations,org.apache.oozie.jms.TestJMSJobEventListener,
{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/3898/

> multiple warnings during build for "no @param for"
> --
>
> Key: OOZIE-2931
> URL: https://issues.apache.org/jira/browse/OOZIE-2931
> Project: Oozie
>  Issue Type: Task
>  Components: action, client, core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2931-0.0.patch, OOZIE-2931-0.patch
>
>
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true
> {noformat}
> generates many warnings for "no @param for" message. 



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


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

2017-06-15 Thread Apache Jenkins Server
See 


--
[...truncated 359.79 KB...]
[INFO] Copying commons-jexl-2.1.1.jar to 

[INFO] Copying oozie-sharelib-hcatalog-5.0.0-SNAPSHOT.jar to 

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

[INFO] Copying gson-2.7.jar to 

[INFO] Copying oozie-core-5.0.0-SNAPSHOT.jar to 

[INFO] Copying commons-pool-1.5.4.jar to 

[INFO] Copying htrace-core-3.0.4.jar to 

[INFO] Copying jaxb-impl-2.2.3-1.jar to 

[INFO] Copying jets3t-0.9.0.jar to 

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

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

[INFO] Copying snappy-java-1.0.4.1.jar to 

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

[INFO] Copying commons-compiler-2.7.6.jar to 

[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

[INFO] Copying oozie-client-5.0.0-SNAPSHOT.jar to 

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

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

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

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

[INFO] Copying jetty-io-9.2.19.

Review Request 60146: Remove CoordJobDeleteJPAExecutor class

2017-06-15 Thread Artem Ervits

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

Review request for oozie.


Repository: oozie-git


Description
---

OOZIE-2061 Remove CoordJobDeleteJPAExecutor


Diffs
-

  
core/src/main/java/org/apache/oozie/executor/jpa/CoordJobDeleteJPAExecutor.java 
c73cffbc 
  
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobDeleteJPAExecutor.java
 5abf9559 


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


Testing
---

yes


Thanks,

Artem Ervits



[jira] [Commented] (OOZIE-2924) ./bin/mkdistro.sh reports a number instances of no @throws for Exception

2017-06-15 Thread Artem Ervits (JIRA)

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

Artem Ervits commented on OOZIE-2924:
-

[~gezapeti] the tests pass locally.

> ./bin/mkdistro.sh reports a number instances of no @throws for Exception
> 
>
> Key: OOZIE-2924
> URL: https://issues.apache.org/jira/browse/OOZIE-2924
> Project: Oozie
>  Issue Type: Improvement
>  Components: client, core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2924-0.patch
>
>




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


Jenkins build is back to normal : oozie-trunk-find-patches-available #161183

2017-06-15 Thread Apache Jenkins Server
See 




Build failed in Jenkins: oozie-trunk-find-patches-available #161182

2017-06-15 Thread Apache Jenkins Server
See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 5998c18fde1da769e91e3ef1bcca484723730c76 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 5998c18fde1da769e91e3ef1bcca484723730c76
 > git rev-list 5998c18fde1da769e91e3ef1bcca484723730c76 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson551586773297469615.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  175k0  175k0 0   190k  0 --:--:-- --:--:-- --:--:--  
190k100  887k0  887k0 0   446k  0 --:--:--  0:00:01 --:--:--  
446k100 1599k0 1599k0 0   552k  0 --:--:--  0:00:02 --:--:--  
552k100 1943k0 1943k0 0   534k  0 --:--:--  0:00:03 --:--:--  
534k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure


Review Request 60143: consolidate hadoop versions in poms

2017-06-15 Thread Artem Ervits

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

Review request for oozie, Peter Cseh and Robert Kanter.


Bugs: n/a
https://issues.apache.org/jira/browse/n/a


Repository: oozie-git


Description
---

OOZIE-2884 consolidate hadoop versions in pomfiles


Diffs
-

  docs/src/site/twiki/DG_QuickStart.twiki 8c3d664a 
  docs/src/site/twiki/ENG_Building.twiki 36d77b27 
  pom.xml fd574443 


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


Testing
---

tests failed due to https://issues.apache.org/jira/browse/OOZIE-2815


Thanks,

Artem Ervits



[jira] [Commented] (OOZIE-2902) org.apache.oozie.action.hadoop.TestJavaActionExecutor fails after hadoop 2.6 upgrade

2017-06-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2902:
--

Testing JIRA OOZIE-2902

Cleaning local git workspace



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



> org.apache.oozie.action.hadoop.TestJavaActionExecutor fails after hadoop 2.6 
> upgrade
> 
>
> Key: OOZIE-2902
> URL: https://issues.apache.org/jira/browse/OOZIE-2902
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2902-0.patch, OOZIE-2902-1.patch, 
> OOZIE-2902-2.patch
>
>
> after https://issues.apache.org/jira/browse/OOZIE-2780 jira, 
> {code}TestJavaActionExecutor{code} fails with
> {noformat}
> ---
>  T E S T S
> ---
> 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[81957]: Class JavaLaunchHelper is implemented in both 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/bin/java 
> (0x107ee74c0) and 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/libinstrument.dylib
>  (0x1112e84e0). One of the two will be used. Which one is undefined.
> Running org.apache.oozie.action.hadoop.TestJavaActionExecutor
> Tests run: 49, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 210.336 sec 
> <<< FAILURE!
> Results :
> Failed tests:   
> testUpdateConfForTimeLineServiceEnabled(org.apache.oozie.action.hadoop.TestJavaActionExecutor):
>  expected:<[tru]e> but was:<[fals]e>
> Tests run: 49, Failures: 1, Errors: 0, Skipped: 0
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. SUCCESS [  0.487 
> s]
> [INFO] Apache Oozie Hadoop Utils hadoop-2-4.4.0-SNAPSHOT .. SUCCESS [  2.005 
> s]
> [INFO] Apache Oozie Hadoop Distcp hadoop-2-4.4.0-SNAPSHOT . SUCCESS [  0.073 
> s]
> [INFO] Apache Oozie Hadoop Auth hadoop-2-4.4.0-SNAPSHOT Test SUCCESS [  0.271 
> s]
> [INFO] Apache Oozie Hadoop Libs ... SUCCESS [  0.015 
> s]
> [INFO] Apache Oozie Client  SUCCESS [  2.365 
> s]
> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  2.465 
> s]
> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  1.812 
> s]
> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  0.535 
> s]
> [INFO] Apache Oozie Core .. FAILURE [03:52 
> min]
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 04:03 min
> [INFO] Finished at: 2017-05-15T09:38:23-04:00
> [INFO] Final Memory: 150M/443M
> {noformat}



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


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

2017-06-15 Thread Apache Jenkins Server
See 


--
[...truncated 57.43 KB...]
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-zookeeper-security-tests ---
[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-zookeeper-security-tests ---
[INFO] Compiling 2 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ 
oozie-zookeeper-security-tests ---
[INFO] Tests are skipped.
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  0.811 s]
[INFO] Apache Oozie Client  SUCCESS [  5.270 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  6.515 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  2.508 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  0.937 s]
[INFO] Apache Oozie Core .. SUCCESS [ 27.491 s]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  6.865 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  3.226 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  6.276 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  4.086 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  2.097 s]
[INFO] Apache Oozie Examples .. SUCCESS [  3.820 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  5.438 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.014 s]
[INFO] Apache Oozie Docs .. SUCCESS [  0.355 s]
[INFO] Apache Oozie WebApp  SUCCESS [  2.952 s]
[INFO] Apache Oozie Tools . SUCCESS [  3.488 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  2.294 s]
[INFO] Apache Oozie Server  SUCCESS [  8.938 s]
[INFO] Apache Oozie Distro  SUCCESS [  1.320 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.193 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:39 min
[INFO] Finished at: 2017-06-16T02:57:42Z
[INFO] Final Memory: 116M/1618M
[INFO] 
  Running test-patch task FINDBUGS_DIFF
[TRACE] Verifying and saving FindBugs output in HEAD
[TRACE] mvn clean compile test-compile findbugs:check 
-Dfindbugs.failOnError=false -Dcheckstyle.failOnViolation=false -DskipTests  | 
tee 

 >> /dev/stdout
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Apache Oozie Main
[INFO] Apache Oozie Client
[INFO] Apache Oozie Share Lib Oozie
[INFO] Apache Oozie Share Lib HCatalog
[INFO] Apache Oozie Share Lib Distcp
[INFO] Apache Oozie Core
[INFO] Apache Oozie Share Lib Streaming
[INFO] Apache Oozie Share Lib Pig
[INFO] Apache Oozie Share Lib Hive
[INFO] Apache Oozie Share Lib Hive 2
[INFO] Apache Oozie Share Lib Sqoop
[INFO] Apache Oozie Examples
[INFO] Apache Oozie Share Lib Spark
[INFO] Apache Oozie Share Lib
[INFO] Apache Oozie Docs
[INFO] Apache Oozie WebApp
[INFO] Apache Oozie Tools
[INFO] Apache Oozie MiniOozie
[INFO] Apache Oozie Server
[INFO] Apache Oozie Distro
[INFO] Apache Oozie ZooKeeper Security Tests
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Main 5.0.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (clean) @ oozie-main ---
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oozie-main ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ oozie-main ---
[INFO]

[jira] [Updated] (OOZIE-2902) org.apache.oozie.action.hadoop.TestJavaActionExecutor fails after hadoop 2.6 upgrade

2017-06-15 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-2902:

Attachment: OOZIE-2902-2.patch

[~gezapeti] I think someone fixed the code before I was able to merge my fixes. 
Master doesn't have the offending code and doesn't have isYARN() check either. 
I looked at the latest few commits but I don't see it. Perhaps it was part of 
the larger OOZIE-1770 merge? 
https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java#L1778-L1784

btw, I searched the current master branch, I don't see any instance of isYARN 
anymore.

> org.apache.oozie.action.hadoop.TestJavaActionExecutor fails after hadoop 2.6 
> upgrade
> 
>
> Key: OOZIE-2902
> URL: https://issues.apache.org/jira/browse/OOZIE-2902
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2902-0.patch, OOZIE-2902-1.patch, 
> OOZIE-2902-2.patch
>
>
> after https://issues.apache.org/jira/browse/OOZIE-2780 jira, 
> {code}TestJavaActionExecutor{code} fails with
> {noformat}
> ---
>  T E S T S
> ---
> 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[81957]: Class JavaLaunchHelper is implemented in both 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/bin/java 
> (0x107ee74c0) and 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre/lib/libinstrument.dylib
>  (0x1112e84e0). One of the two will be used. Which one is undefined.
> Running org.apache.oozie.action.hadoop.TestJavaActionExecutor
> Tests run: 49, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 210.336 sec 
> <<< FAILURE!
> Results :
> Failed tests:   
> testUpdateConfForTimeLineServiceEnabled(org.apache.oozie.action.hadoop.TestJavaActionExecutor):
>  expected:<[tru]e> but was:<[fals]e>
> Tests run: 49, Failures: 1, Errors: 0, Skipped: 0
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. SUCCESS [  0.487 
> s]
> [INFO] Apache Oozie Hadoop Utils hadoop-2-4.4.0-SNAPSHOT .. SUCCESS [  2.005 
> s]
> [INFO] Apache Oozie Hadoop Distcp hadoop-2-4.4.0-SNAPSHOT . SUCCESS [  0.073 
> s]
> [INFO] Apache Oozie Hadoop Auth hadoop-2-4.4.0-SNAPSHOT Test SUCCESS [  0.271 
> s]
> [INFO] Apache Oozie Hadoop Libs ... SUCCESS [  0.015 
> s]
> [INFO] Apache Oozie Client  SUCCESS [  2.365 
> s]
> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  2.465 
> s]
> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  1.812 
> s]
> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  0.535 
> s]
> [INFO] Apache Oozie Core .. FAILURE [03:52 
> min]
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 04:03 min
> [INFO] Finished at: 2017-05-15T09:38:23-04:00
> [INFO] Final Memory: 150M/443M
> {noformat}



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


[jira] [Updated] (OOZIE-2931) multiple warnings during build for "no @param for"

2017-06-15 Thread Artem Ervits (JIRA)

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

Artem Ervits updated OOZIE-2931:

Attachment: OOZIE-2931-0.0.patch

> multiple warnings during build for "no @param for"
> --
>
> Key: OOZIE-2931
> URL: https://issues.apache.org/jira/browse/OOZIE-2931
> Project: Oozie
>  Issue Type: Task
>  Components: action, client, core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2931-0.0.patch, OOZIE-2931-0.patch
>
>
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true
> {noformat}
> generates many warnings for "no @param for" message. 



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


[jira] [Commented] (OOZIE-2931) multiple warnings during build for "no @param for"

2017-06-15 Thread Artem Ervits (JIRA)

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

Artem Ervits commented on OOZIE-2931:
-

[~gezapeti] thanks for review, I'm using Java 8. Unfortunately the build is no 
longer available for review but I'd seen the message before

{noformat}
-1 JAVADOC
. -1 the patch seems to introduce 1 new Javadoc warning(s)
. WARNING: the current HEAD has 6 Javadoc warning(s)
{noformat}

I believe it was introduced with merge of OYA to master. I'll run the build 
again.

> multiple warnings during build for "no @param for"
> --
>
> Key: OOZIE-2931
> URL: https://issues.apache.org/jira/browse/OOZIE-2931
> Project: Oozie
>  Issue Type: Task
>  Components: action, client, core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0
>
> Attachments: OOZIE-2931-0.patch
>
>
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true
> {noformat}
> generates many warnings for "no @param for" message. 



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


Jenkins build is back to normal : oozie-trunk-find-patches-available #161171

2017-06-15 Thread Apache Jenkins Server
See 




Build failed in Jenkins: oozie-trunk-find-patches-available #161170

2017-06-15 Thread Apache Jenkins Server
See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 5998c18fde1da769e91e3ef1bcca484723730c76 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 5998c18fde1da769e91e3ef1bcca484723730c76
 > git rev-list 5998c18fde1da769e91e3ef1bcca484723730c76 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson7116329256621529055.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  159k0  159k0 0   190k  0 --:--:-- --:--:-- --:--:--  
190k100  823k0  823k0 0   435k  0 --:--:--  0:00:01 --:--:--  
435k100 1343k0 1343k0 0   491k  0 --:--:--  0:00:02 --:--:--  
491k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure


[jira] [Commented] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2918:
--

Testing JIRA OOZIE-2918

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 15 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 6 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 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: 1961
.Tests rerun: 18
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestHdfsOperations,org.apache.oozie.jms.TestJMSJobEventListener,
{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/oozie-trunk-precommit-build/3897/

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
> Attachments: OOZIE-2918-01.patch
>
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



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


[jira] [Updated] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari updated OOZIE-2918:
--
Attachment: OOZIE-2918-01.patch

Testing done:
- {{mvn clean test   -DtargetJavaVersion=1.8 -DjavaVersion=1.8  
-Dtest=TestDistcpMain,TestJavaMain,TestMapReduceMain,TestPipesMain,TestShellMain,TestHiveMain,TestHive2Main,TestLauncherMain,TestPigMain,TestPigMainWithOldAPI,TestDuplicateFilteringInSparkMain,TestSparkMain,TestSqoopMain,TestStreamingMain
   -Dhadoop.version-2.6.0}}

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
> Attachments: OOZIE-2918-01.patch
>
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



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


[jira] [Commented] (OOZIE-2946) Include find-sec-bugs plugin

2017-06-15 Thread Robert Kanter (JIRA)

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

Robert Kanter commented on OOZIE-2946:
--

Ok, that seems reasonable to me.  

One last question: any idea why the latest Jenkins run didn't find any new 
findbugs problems but the one from Yesterday found a ton (as expected)?

> Include find-sec-bugs plugin
> 
>
> Key: OOZIE-2946
> URL: https://issues.apache.org/jira/browse/OOZIE-2946
> Project: Oozie
>  Issue Type: Task
>  Components: build, security
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: OOZIE-2946-1.patch, OOZIE-2946-2.patch
>
>
> The [Find Security Bugs|http://find-sec-bugs.github.io/] plugin looks for 
> security bugs in Java web apps, such as Oozie. This plugin should be included 
> in the build process.



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


[jira] [Commented] (OOZIE-2927) Append new line character for Hive2 query using query tag

2017-06-15 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2927:
---

The test does not fail for me without the fix for it. Isn't this issue 
affecting only certain Beeline versions?

> Append new line character for Hive2 query using query tag
> -
>
> Key: OOZIE-2927
> URL: https://issues.apache.org/jira/browse/OOZIE-2927
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2927-00.patch, OOZIE-2927-01.patch
>
>
> Without the new line character in the query, beeline does not do anything. 
> Though hive2 action completes successfully but query is not executed.



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


[jira] [Commented] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2944:
--

Testing JIRA OOZIE-2944

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 9 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 6 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 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: 1966
.Tests rerun: 79
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM,
{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/oozie-trunk-precommit-build/3896/

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch, OOZIE-2944-02.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classlo

Jenkins build is back to normal : oozie-trunk-precommit-build #3896

2017-06-15 Thread Apache Jenkins Server
See 




[jira] [Commented] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2944:
---

+1 (pending Jenkins) on the second patch.
Thanks for the fix!

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch, OOZIE-2944-02.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of prepare actions successfully
> Failing Oozie Launcher, null
> Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://localhost:9000/user/asasvari/oozie-asas/002-170613150915408-oozie-asas-W/shell-node--shell/action-data.seq
> Stopping AM
> Callback notification attempts left 0
> Callback notification trying 
> http://0.0.0.0:11000/oozie/callback?id

[jira] [Commented] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari commented on OOZIE-2918:
---

It would make sense to review and commit OOZIE-2944 first.

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



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


[jira] [Assigned] (OOZIE-2918) Delete LauncherMapper and its test

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari reassigned OOZIE-2918:
-

Assignee: Attila Sasvari

> Delete LauncherMapper and its test
> --
>
> Key: OOZIE-2918
> URL: https://issues.apache.org/jira/browse/OOZIE-2918
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
>
> While LauncherMapper itself is not used anymore it contains a bunch of static 
> methods that are referenced from different places in the code.
> We should refactor out code and related test cases to where they belong.



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


[jira] [Commented] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2944:
---

failures are due to OOZIE-2794 i guess.

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch, OOZIE-2944-02.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of prepare actions successfully
> Failing Oozie Launcher, null
> Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://localhost:9000/user/asasvari/oozie-asas/002-170613150915408-oozie-asas-W/shell-node--shell/action-data.seq
> Stopping AM
> Callback notification attempts left 0
> Callback notification trying 
> http://0.0.0.0:11000/oozie/callback?id=002-1706131509154

[jira] [Updated] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari updated OOZIE-2944:
--
Attachment: OOZIE-2944-02.patch

[~gezapeti] thanks for the review! Please find updated patch attached.

I reran failed tests with {{mvn test   -DtargetJavaVersion=1.8 
-DjavaVersion=1.8  
-Dtest=TestDBLoadDump,TestHiveMain,TestPigMain,TestPigMainWithOldAPI,TestXConfiguration
   -Dhadoop.version-2.6.0}} and they passed locally.

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch, OOZIE-2944-02.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of prepare actions successfully
> Failing Oozie Launcher, null
> Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://localhost:9000/

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

2017-06-15 Thread Peter Cseh (JIRA)

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

Peter Cseh updated OOZIE-2910:
--
Attachment: OOZIE-2910-001.patch

Attaching a patch that contains the test case, but it's failing at the moment.
It looks like tagging is not working as expected.

> 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 Cseh
> Attachments: OOZIE-2910-001.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-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2944:
---

Please update the apidoc for the {{createJobConf}} as well and rename it to 
something along the lines of createConfiguration/createDefaultConfiguration.

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of prepare actions successfully
> Failing Oozie Launcher, null
> Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://localhost:9000/user/asasvari/oozie-asas/002-170613150915408-oozie-asas-W/shell-node--shell/action-data.seq
> Stopping AM
> Callback notification attempts left 0
>

[jira] [Commented] (OOZIE-2948) Misleading error message if workflow.xml is not found

2017-06-15 Thread Peter Bacsko (JIRA)

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

Peter Bacsko commented on OOZIE-2948:
-

It should print sth like {{Error: E0505 : E0505: workflow.xml does not exist in 
[hdfs://host.example.com:8020/user/testuser/sparktest]}}.

> Misleading error message if workflow.xml is not found
> -
>
> Key: OOZIE-2948
> URL: https://issues.apache.org/jira/browse/OOZIE-2948
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
>
> The following error message is printed if {{workflow.xml}} is not found under 
> a particular directory:
> {noformat}
> [root@host spark]# oozie job -run -oozie http://$(hostname -f):11000/oozie 
> -config job.properties
> Error: E0505 : E0505: App definition 
> [hdfs://host.example.com:8020/user/testuser/sparktest] does not exist
> {noformat}
> It's not immediately clear what "app definition" means. After looking at the 
> code, it becomes obvious that it's the workflow definition XML, but the error 
> message should state this explicitly.



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


[jira] [Created] (OOZIE-2948) Misleading error message if workflow.xml is not found

2017-06-15 Thread Peter Bacsko (JIRA)
Peter Bacsko created OOZIE-2948:
---

 Summary: Misleading error message if workflow.xml is not found
 Key: OOZIE-2948
 URL: https://issues.apache.org/jira/browse/OOZIE-2948
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Bacsko
Assignee: Peter Bacsko
Priority: Minor


The following error message is printed if {{workflow.xml}} is not found under a 
particular directory:

{noformat}
[root@host spark]# oozie job -run -oozie http://$(hostname -f):11000/oozie 
-config job.properties
Error: E0505 : E0505: App definition 
[hdfs://host.example.com:8020/user/testuser/sparktest] does not exist
{noformat}

It's not immediately clear what "app definition" means. After looking at the 
code, it becomes obvious that it's the workflow definition XML, but the error 
message should state this explicitly.



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


[jira] [Commented] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2944:
--

Testing JIRA OOZIE-2944

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 6 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 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: 1966
.Tests failed: 6
.Tests errors: 2

.The patch failed the following testcases:

.  testLoadDump(org.apache.oozie.tools.TestDBLoadDump)
.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)

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

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

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org

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

2017-06-15 Thread Apache Jenkins Server
See 


--
[...truncated 371.43 KB...]
[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

[INFO] Copying oozie-client-5.0.0-SNAPSHOT.jar to 

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

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

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

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

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

[INFO] Copying commons-beanutils-core-1.8.0.jar to 

[INFO] Copying antlr-2.7.7.jar to 

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

[INFO] Copying datanucleus-api-jdo-3.2.6.jar to 

[INFO] Copying jung-api-2.0.1.jar to 

[INFO] Copying jta-1.1.jar to 

[INFO] Copying apacheds-kerberos-codec-2.0.0-M15.jar to 

[INFO] Copying kryo-2.22.jar to 

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

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

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

[INFO] Copying hadoop-yarn-server-web-proxy-2.6.0.jar to 

[INFO] Copying hamcrest-core-1.3.jar to 

[INFO] Copying jetty-rewrite-9.2.19.v20160908.j

Re: [jira] [Commented] (OOZIE-2941) Old map-reduce workflow example can't work with OYA

2017-06-15 Thread Attila Sasvari
Dong Ying, I have not changed anything. I have built oozie from source with
- mvn  clean install  assembly:single -DskipTests  -Dhadoop.version-2.6.0
-Puber

Note: -Puber is used so that dependencies of the Oozie server are copied

Then
- cd distro/target/oozie-5.0.0-SNAPSHOT

- I made sure that my hadoop configuration (e.g. fs.defaultFS points to the
right namenode in core-site.xml in conf/hadoop-conf ) was correct (see
https://oozie.apache.org/docs/4.2.0/AG_HadoopConfiguration.html)

- Started  Oozie server
bin/oozied.sh start

- Installed Sharelib
bin/oozie-setup.sh sharelib create -fs hdfs://localhost:9000 -locallib
oozie-sharelib-5.0.0-SNAPSHOT.tar.gz   -concurrency 4

- Updated Sharelib
bin/oozie admin -sharelibupdate

- Extracted, uploaded examples to HDFS
- Submitted map-reduce example
bin/oozie job -oozie http://localhost:11000/oozie -config
examples/apps/map-reduce/job.properties -run
-DnameNode=hdfs://localhost:9000 -DjobTracker=localhost:8032

(I am working with a pseudo, single-node, Hadoop 2.6 cluster in my dev
environment)

JavaActionExecutor should add MR to classpath in case of a MapReduce action:

https://github.com/apache/oozie/blob/83d4ddf45aa16649bd9fae367fa915379d5781cd/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L1091

In my debugger I could see the following env was added to launcherJobConf:

{CLASSPATH=$PWD:$PWD/*:$HADOOP_CONF_DIR:$HADOOP_COMMON_HOME/share/hadoop/common/*:$HADOOP_COMMON_HOME/share/hadoop/common/lib/*:$HADOOP_HDFS_HOME/share/hadoop/hdfs/*:$HADOOP_HDFS_HOME/share/hadoop/hdfs/lib/*:$HADOOP_YARN_HOME/share/hadoop/yarn/*:$HADOOP_YARN_HOME/share/hadoop/yarn/lib/*}

It is later added to appContext used for submitting the application to YARN
-
https://github.com/apache/oozie/blob/83d4ddf45aa16649bd9fae367fa915379d5781cd/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L1028


On Wed, Jun 14, 2017 at 5:39 AM, Dongying Jiao 
wrote:
>
> Hi Attilia:
> I have Oozie share lib, it is setup during oozie installation, but oozie
> share lib doesn't have map-reduce folder. Did you modify anything to make
> the example map-reduce workflow run successfully?
>
> Peter:
> About the commit link you mentioned, I see MR jars are added from
> map-reduce property:“mapreduce.application.classpath”, the classpath in my
> cluster is:
>
/etc/hadoop/conf/:$PWD/mr-framework/hadoop/share/hadoop/mapreduce/*:$PWD/mr-framework/hadoop/share/hadoop/mapreduce/lib/*:$PWD/mr-framework/hadoop/share/hadoop/common/*:$PWD/mr-framework/hadoop/share/hadoop/common/lib/*:$PWD/mr-framework/hadoop/share/hadoop/yarn/*:$PWD/mr-framework/hadoop/share/hadoop/yarn/lib/*:$PWD/mr-framework/hadoop/share/hadoop/hdfs/*:$PWD/mr-framework/hadoop/share/hadoop/hdfs/lib/*:$PWD/mr-framework/hadoop/share/hadoop/tools/lib/*:/etc/hadoop/conf/secure:/usr/lib/hadoop-lzo/lib/*:/usr/iop/current/ext/hadoop/*
>
> Not sure if my map-reduce classpath is not corrcet.
> I used the 08/Jun build in oozie master branch.
>
> Thanks for help.
>
> Best Regards,
> Dong Ying
>
>
>
> 2017-06-13 23:27 GMT+08:00 Attila Sasvari (JIRA) :
>
> >
> > [ https://issues.apache.org/jira/browse/OOZIE-2941?page=
> > com.atlassian.jira.plugin.system.issuetabpanels:comment-
> > tabpanel&focusedCommentId=16048022#comment-16048022 ]
> >
> > Attila Sasvari commented on OOZIE-2941:
> > ---
> >
> > [~Dongying Jiao] I re-tested the mapreduce example in my local
> > environment, and the workflow successfully finished. Before running the
MR
> > workflow, you should first install Oozie sharelib and make sure jhs is
> > running. As per your previous commend, I suspect sharelib was not
installed
> > in your case. So I believe this issue is not the same as my experience
with
> > the shell action example.
> >
> > > Old map-reduce workflow example can't work with OYA
> > > ---
> > >
> > > Key: OOZIE-2941
> > > URL: https://issues.apache.org/jira/browse/OOZIE-2941
> > > Project: Oozie
> > >  Issue Type: Sub-task
> > >  Components: workflow
> > >Affects Versions: trunk
> > >Reporter: Dongying Jiao
> > > Attachments: RM_UI.jpg
> > >
> > >
> > > map-reduce workflow in Oozie examples run failed after OYA merged. The
> > exception in yarn log is:
> > > Exception in thread "main" java.lang.NoClassDefFoundError:
> > org/apache/hadoop/mapred/Mapper
> > >   at java.lang.ClassLoader.defineClass1(Native Method)
> > >   at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> > >   at java.security.SecureClassLoader.defineClass(
> > SecureClassLoader.java:142)
> > >   at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> > >   at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> > >   at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> > >   at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> > >   

[jira] [Commented] (OOZIE-2946) Include find-sec-bugs plugin

2017-06-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2946:
--

Testing JIRA OOZIE-2946

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 6 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 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: 1966
.Tests rerun: 64
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.action.hadoop.TestLauncherAM,
{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/3894/

> Include find-sec-bugs plugin
> 
>
> Key: OOZIE-2946
> URL: https://issues.apache.org/jira/browse/OOZIE-2946
> Project: Oozie
>  Issue Type: Task
>  Components: build, security
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: OOZIE-2946-1.patch, OOZIE-2946-2.patch
>
>
> The [Find Security Bugs|http://find-sec-bugs.github.io/] plugin looks for 
> security bugs in Java web apps, such as Oozie. This plugin should be included 
> in the build process.



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


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

2017-06-15 Thread Apache Jenkins Server
See 


--
[...truncated 360.90 KB...]
[INFO] Copying commons-jexl-2.1.1.jar to 

[INFO] Copying oozie-sharelib-hcatalog-5.0.0-SNAPSHOT.jar to 

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

[INFO] Copying gson-2.7.jar to 

[INFO] Copying oozie-core-5.0.0-SNAPSHOT.jar to 

[INFO] Copying commons-pool-1.5.4.jar to 

[INFO] Copying htrace-core-3.0.4.jar to 

[INFO] Copying jaxb-impl-2.2.3-1.jar to 

[INFO] Copying jets3t-0.9.0.jar to 

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

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

[INFO] Copying snappy-java-1.0.4.1.jar to 

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

[INFO] Copying commons-compiler-2.7.6.jar to 

[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

[INFO] Copying activemq-client-5.13.3.jar to 

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

[INFO] Copying oozie-client-5.0.0-SNAPSHOT.jar to 

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

[INFO] Copying leveldbjni-all-1.8.jar to 

[INFO] Copying jetty-util-6.1.26.jar to 

[INFO] Copying velocity-1.5.jar to 

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

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying netty-3.7.0.Final.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

[INFO] Copying jetty-io-9.2.19.

[jira] [Updated] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari updated OOZIE-2944:
--
Issue Type: Sub-task  (was: Bug)
Parent: OOZIE-2889

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of prepare actions successfully
> Failing Oozie Launcher, null
> Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://localhost:9000/user/asasvari/oozie-asas/002-170613150915408-oozie-asas-W/shell-node--shell/action-data.seq
> Stopping AM
> Callback notification attempts left 0
> Callback notification trying 
> http://0.0.0.0:11000/oozie/callback?id=002-170613150915408-oozie-asas-W@shell-node&status=FAILED
> Call

[jira] [Updated] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari updated OOZIE-2944:
--
Attachment: OOZIE-2944-01.patch

Tests:
- {{mvn test   -DtargetJavaVersion=1.8 -DjavaVersion=1.8  
-Dtest=TestLauncher,TestWorkflowActionKillXCommand,TestHadoopAccessorService   
-Dhadoop.version-2.6.0}} passed
- shell example succeeded
{code}
application_1497357254962_0071  asasvari
oozie:launcher:T=shell:W=shell-wf:A=shell-node:ID=002-170615122337884-oozie-asas-W
  Oozie Launcher  default Thu, 15 Jun 2017 10:26:30 GMT   Thu, 15 Jun 2017 
10:26:32 GMT   FINISHEDSUCCEEDED
{code}

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of 

[jira] [Commented] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari commented on OOZIE-2944:
---

[~pbacsko] [~rkanter] [~gezapeti] can you have a look at the patch? Thanks

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2944-01.patch
>
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of prepare actions successfully
> Failing Oozie Launcher, null
> Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://localhost:9000/user/asasvari/oozie-asas/002-170613150915408-oozie-asas-W/shell-node--shell/action-data.seq
> Stopping AM
> Callback notification attempts left 0
> Callback notification trying 
> http://0.0.0.0:11000/oozie/callback?id=

[jira] [Assigned] (OOZIE-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari reassigned OOZIE-2944:
-

Assignee: Attila Sasvari

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the execution of prepare actions successfully
> Failing Oozie Launcher, null
> Oozie Launcher, uploading action data to HDFS sequence file: 
> hdfs://localhost:9000/user/asasvari/oozie-asas/002-170613150915408-oozie-asas-W/shell-node--shell/action-data.seq
> Stopping AM
> Callback notification attempts left 0
> Callback notification trying 
> http://0.0.0.0:11000/oozie/callback?id=002-170613150915408-oozie-asas-W@shell-node&status=FAILED
> Callback notification to 
> http://0.0.0.0:11000/oozie/callback?id=002-1706131

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

2017-06-15 Thread Peter Cseh (JIRA)

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

Peter Cseh reassigned OOZIE-2910:
-

Assignee: Peter Cseh

> 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 Cseh
>
> 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-2944) Shell action example does not work with Oozie on Yarn on hadoop 2.6

2017-06-15 Thread Attila Sasvari (JIRA)

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

Attila Sasvari commented on OOZIE-2944:
---

Right now JavaActionExecutor creates jobConf at multiple places:
-[createBaseHadoopConf()|https://github.com/apache/oozie/blob/83d4ddf45aa16649bd9fae367fa915379d5781cd/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L249]
-[parseJobXmlAndConfiguration() 
|https://github.com/apache/oozie/blob/83d4ddf45aa16649bd9fae367fa915379d5781cd/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L342]

As a result, actionConf and launcherJobConf are JobConf objects in 
{{createAppSubmissionContext()}}.

> Shell action example does not work with Oozie on Yarn on hadoop 2.6
> ---
>
> Key: OOZIE-2944
> URL: https://issues.apache.org/jira/browse/OOZIE-2944
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>
> I tried to execute example shell action with a pseudo hadoop 2.6.0. The 
> workflow failed with the exception below :
> {code}
> $ ~/workspace/pseudo/hadoop-2.6.0/bin/yarn logs --applicationId 
> application_1497357254962_0005
> 17/06/13 15:59:09 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 17/06/13 15:59:09 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Container: container_1497357254962_0005_01_01 on 172.30.64.221_55437
> ==
> LogType:stderr
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:1397
> Log Contents:
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/mapred/Mapper
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> org.apache.oozie.action.hadoop.LauncherAM.getMainArguments(LauncherAM.java:540)
> at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:170)
> at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:148)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.mapred.Mapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 15 more
> LogType:stdout
> Log Upload Time:13-Jun-2017 15:58:45
> LogLength:2152
> Log Contents:
> Submitter user is: asasvari
> log4j: Trying to find [container-log4j.properties] using context classloader 
> sun.misc.Launcher$AppClassLoader@6bc7c054.
> log4j: Using URL 
> [jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties]
>  for automatic log4j configuration.
> log4j: Reading configuration from URL 
> jar:file:/Users/asasvari/workspace/pseudo/hadoop-2.6.0/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.6.0.jar!/container-log4j.properties
> log4j: Hierarchy threshold set to [ALL].
> log4j: Parsing for [root] with value=[INFO,CLA, EventCounter].
> log4j: Level token is [INFO].
> log4j: Category root set to INFO
> log4j: Parsing appender named "CLA".
> log4j: Parsing layout options for "CLA".
> log4j: Setting property [conversionPattern] to [%d{ISO8601} %p [%t] %c: %m%n].
> log4j: End of parsing for "CLA".
> log4j: Setting property [containerLogDir] to 
> [/Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01].
> log4j: Setting property [totalLogFileSize] to [0].
> log4j: setFile called: 
> /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1497357254962_0005/container_1497357254962_0005_01_01/syslog,
>  true
> log4j: setFile ended
> log4j: Parsed "CLA" options.
> log4j: Parsing appender named "EventCounter".
> log4j: Parsed "EventCounter" options.
> log4j: Finished configuring.
> Using login user for UGI
> Launcher AM configuration loaded
> Starting the execution of prepare actions
> Completed the exe

[jira] [Commented] (OOZIE-2943) Fix Findbugs warnings in oozie-sharelib-pig

2017-06-15 Thread Jan Hentschel (JIRA)

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

Jan Hentschel commented on OOZIE-2943:
--

Not sure, if the failing tests are flaky. Locally they are running fine.

> Fix Findbugs warnings in oozie-sharelib-pig
> ---
>
> Key: OOZIE-2943
> URL: https://issues.apache.org/jira/browse/OOZIE-2943
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
> Attachments: OOZIE-2943-1.patch, OOZIE-2943-2.patch
>
>
> Currently Findbugs complains about the following warnings in the 
> *oozie-sharelib-pig* module:
> {code}
> [INFO] 
> org.apache.oozie.action.hadoop.OoziePigStats.toJSONFromMultiStoreCounters(Map)
>  makes inefficient use of keySet iterator instead of entrySet iterator 
> [org.apache.oozie.action.hadoop.OoziePigStats] At OoziePigStats.java:[line 
> 130]
> [INFO] Dead store to klass in 
> org.apache.oozie.action.hadoop.PigMain.runPigJob(String[], String, boolean, 
> boolean) [org.apache.oozie.action.hadoop.PigMain] At PigMain.java:[line 335]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.PigMain.handleError(String): new 
> java.io.FileReader(String) [org.apache.oozie.action.hadoop.PigMain] At 
> PigMain.java:[line 307]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.PigMain.writeExternalData(String, File): new 
> java.io.FileWriter(File) [org.apache.oozie.action.hadoop.PigMain] At 
> PigMain.java:[line 408]
> [INFO] org.apache.oozie.action.hadoop.PigMain.run(String[]) may fail to clean 
> up java.io.OutputStream on checked exception 
> [org.apache.oozie.action.hadoop.PigMain, 
> org.apache.oozie.action.hadoop.PigMain] Obligation to clean up resource 
> created at PigMain.java:[line 130] is not dischargedPath continues at 
> PigMain.java:[line 131]
> [INFO] org.apache.oozie.action.hadoop.PigMain.handleError(String) may fail to 
> close stream on exception [org.apache.oozie.action.hadoop.PigMain] At 
> PigMain.java:[line 307]
> [INFO] org.apache.oozie.action.hadoop.PigMain.run(String[]) may fail to close 
> stream on exception [org.apache.oozie.action.hadoop.PigMain] At 
> PigMain.java:[line 130]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.PigMainWithOldAPI.getHadoopJobIds(String): new 
> java.io.FileReader(String) [org.apache.oozie.action.hadoop.PigMainWithOldAPI] 
> At PigMainWithOldAPI.java:[line 265]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.PigMainWithOldAPI.run(String[]): new 
> java.io.FileReader(String) [org.apache.oozie.action.hadoop.PigMainWithOldAPI, 
> org.apache.oozie.action.hadoop.PigMainWithOldAPI] At 
> PigMainWithOldAPI.java:[line 126]Another occurrence at 
> PigMainWithOldAPI.java:[line 219]
> [INFO] org.apache.oozie.action.hadoop.PigMainWithOldAPI.run(String[]) may 
> fail to clean up java.io.OutputStream on checked exception 
> [org.apache.oozie.action.hadoop.PigMainWithOldAPI, 
> org.apache.oozie.action.hadoop.PigMainWithOldAPI] Obligation to clean up 
> resource created at PigMainWithOldAPI.java:[line 101] is not dischargedPath 
> continues at PigMainWithOldAPI.java:[line 102]
> [INFO] 
> org.apache.oozie.action.hadoop.PigMainWithOldAPI.getHadoopJobIds(String) may 
> fail to close stream on exception 
> [org.apache.oozie.action.hadoop.PigMainWithOldAPI] At 
> PigMainWithOldAPI.java:[line 265]
> [INFO] org.apache.oozie.action.hadoop.PigMainWithOldAPI.run(String[]) may 
> fail to close stream on exception 
> [org.apache.oozie.action.hadoop.PigMainWithOldAPI, 
> org.apache.oozie.action.hadoop.PigMainWithOldAPI] At 
> PigMainWithOldAPI.java:[line 101]Another occurrence at 
> PigMainWithOldAPI.java:[line 242]
> [INFO] org.apache.oozie.action.hadoop.PigMainWithOldAPI.run(String[]) may 
> fail to close stream on exception 
> [org.apache.oozie.action.hadoop.PigMainWithOldAPI, 
> org.apache.oozie.action.hadoop.PigMainWithOldAPI] At 
> PigMainWithOldAPI.java:[line 126]Another occurrence at 
> PigMainWithOldAPI.java:[line 219]
> {code}
> They should be fixed to get the code more reliable.



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


[jira] [Commented] (OOZIE-2946) Include find-sec-bugs plugin

2017-06-15 Thread Jan Hentschel (JIRA)

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

Jan Hentschel commented on OOZIE-2946:
--

[~rkanter] I moved the version of findbugs-maven-plugin to the 
pluginManagement, but I was not able to move findsecbugs to it. It seems that 
Maven doesn't pick up the version for a dependency of a plugin (had the same 
problem with the findbugs dependency of the xml-maven-plugin) if you define it 
in the dependencyManagement or pluginManagement.

> Include find-sec-bugs plugin
> 
>
> Key: OOZIE-2946
> URL: https://issues.apache.org/jira/browse/OOZIE-2946
> Project: Oozie
>  Issue Type: Task
>  Components: build, security
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: OOZIE-2946-1.patch, OOZIE-2946-2.patch
>
>
> The [Find Security Bugs|http://find-sec-bugs.github.io/] plugin looks for 
> security bugs in Java web apps, such as Oozie. This plugin should be included 
> in the build process.



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


[jira] [Updated] (OOZIE-2946) Include find-sec-bugs plugin

2017-06-15 Thread Jan Hentschel (JIRA)

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

Jan Hentschel updated OOZIE-2946:
-
Attachment: OOZIE-2946-2.patch

> Include find-sec-bugs plugin
> 
>
> Key: OOZIE-2946
> URL: https://issues.apache.org/jira/browse/OOZIE-2946
> Project: Oozie
>  Issue Type: Task
>  Components: build, security
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: OOZIE-2946-1.patch, OOZIE-2946-2.patch
>
>
> The [Find Security Bugs|http://find-sec-bugs.github.io/] plugin looks for 
> security bugs in Java web apps, such as Oozie. This plugin should be included 
> in the build process.



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


[jira] [Commented] (OOZIE-1967) Fix checkstyle issues

2017-06-15 Thread Jan Hentschel (JIRA)

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

Jan Hentschel commented on OOZIE-1967:
--

Currently there are a lot of checkstyle issues in a lot of different files, 
especially in *oozie-core*. I would like to close this one and open sub-tasks 
in OOZIE-1965 to make it more granular.

> Fix checkstyle issues
> -
>
> Key: OOZIE-1967
> URL: https://issues.apache.org/jira/browse/OOZIE-1967
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Jan Hentschel
>




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