date:20180807

[jira] [Commented] (OOZIE-3321) PySpark example fails

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3321:
--


Testing JIRA OOZIE-3321

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:red}-1{color} the patch contains 1 line(s) with trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2914
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}

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

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

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



> PySpark example fails
> -
>
> Key: OOZIE-3321
> URL: https://issues.apache.org/jira/browse/OOZIE-3321
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.0.0, 5.1.0
>Reporter: Daniel Becker
>Assignee: Daniel Becker
>Priority: Minor
> Attachments: OOZIE-3321.1.patch, OOZIE-3321.2.patch
>
>
> The PySpark example fails with the following exception:
> {noformat}
> ACTION[001-180806145017687-oozie-oozi-W@spark-node] Launcher exception: 
> Missing py4j and/or pyspark zip files. Please add them to the lib folder or 
> to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib.
>   at 
> org.apache.oozie.action.hadoop.SparkMain.getMatchingPyFile(SparkMain.java:151)
>   at 
> org.apache.oozie.action.hadoop.SparkMain.createPySparkLibFolder(SparkMain.java:132)
>   at org.apache.oozie.action.hadoop.SparkMain.run(SparkMain.java:77)
>   at 
> org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:101)
>   at org.apache.oozie.action.hadoop.SparkMain.main(SparkMain.java:60)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
>

Failed: OOZIE-3321 PreCommit Build #735

2018-08-07 Thread Apache Jenkins Server

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

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


Testing JIRA OOZIE-3321

Cleaning local git workspace



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


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

 There is at least one warning, please check

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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  31720 0  100  3172  0   3669 --:--:-- --:--:-- --:--:--  
3667{"self":"https://issues.apache.org/jira/rest/api/2/issue/13177130/comment/16572234","id":"16572234","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop

[jira] [Commented] (OOZIE-3321) PySpark example fails

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3321:
--

PreCommit-OOZIE-Build started


> PySpark example fails
> -
>
> Key: OOZIE-3321
> URL: https://issues.apache.org/jira/browse/OOZIE-3321
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.0.0, 5.1.0
>Reporter: Daniel Becker
>Assignee: Daniel Becker
>Priority: Minor
> Attachments: OOZIE-3321.1.patch, OOZIE-3321.2.patch
>
>
> The PySpark example fails with the following exception:
> {noformat}
> ACTION[001-180806145017687-oozie-oozi-W@spark-node] Launcher exception: 
> Missing py4j and/or pyspark zip files. Please add them to the lib folder or 
> to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib.
>   at 
> org.apache.oozie.action.hadoop.SparkMain.getMatchingPyFile(SparkMain.java:151)
>   at 
> org.apache.oozie.action.hadoop.SparkMain.createPySparkLibFolder(SparkMain.java:132)
>   at org.apache.oozie.action.hadoop.SparkMain.run(SparkMain.java:77)
>   at 
> org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:101)
>   at org.apache.oozie.action.hadoop.SparkMain.main(SparkMain.java:60)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:410)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.access$300(LauncherAM.java:55)
>   at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:223)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:217)
>   at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:153)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:141)
> {noformat}
> This is because py4j-0.9-src.zip and pyspark.zip are not available. They are 
> needed for the example to run, so we should either add them to the sharelib 
> or if they are not important enough to be in the sharelib, we should add them 
> to the example's lib directory. Currently these two files can be found in the 
> codebase under sharelib/spark/src/test/resources. We should also decide what 
> to do with these files there, to avoid duplication of resource files.
> If I add the files manually to either the sharelib or the lib directory of 
> the example, the example runs successfilly.



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

[jira] [Commented] (OOZIE-3321) PySpark example fails

2018-08-07 Thread Daniel Becker (JIRA)



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

Daniel Becker commented on OOZIE-3321:
--

With the second patch, the test that failed passes locally and the pyspark 
example succeeds.

> PySpark example fails
> -
>
> Key: OOZIE-3321
> URL: https://issues.apache.org/jira/browse/OOZIE-3321
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.0.0, 5.1.0
>Reporter: Daniel Becker
>Assignee: Daniel Becker
>Priority: Minor
> Attachments: OOZIE-3321.1.patch, OOZIE-3321.2.patch
>
>
> The PySpark example fails with the following exception:
> {noformat}
> ACTION[001-180806145017687-oozie-oozi-W@spark-node] Launcher exception: 
> Missing py4j and/or pyspark zip files. Please add them to the lib folder or 
> to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib.
>   at 
> org.apache.oozie.action.hadoop.SparkMain.getMatchingPyFile(SparkMain.java:151)
>   at 
> org.apache.oozie.action.hadoop.SparkMain.createPySparkLibFolder(SparkMain.java:132)
>   at org.apache.oozie.action.hadoop.SparkMain.run(SparkMain.java:77)
>   at 
> org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:101)
>   at org.apache.oozie.action.hadoop.SparkMain.main(SparkMain.java:60)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:410)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.access$300(LauncherAM.java:55)
>   at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:223)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:217)
>   at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:153)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:141)
> {noformat}
> This is because py4j-0.9-src.zip and pyspark.zip are not available. They are 
> needed for the example to run, so we should either add them to the sharelib 
> or if they are not important enough to be in the sharelib, we should add them 
> to the example's lib directory. Currently these two files can be found in the 
> codebase under sharelib/spark/src/test/resources. We should also decide what 
> to do with these files there, to avoid duplication of resource files.
> If I add the files manually to either the sharelib or the lib directory of 
> the example, the example runs successfilly.



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

[jira] [Updated] (OOZIE-3321) PySpark example fails

2018-08-07 Thread Daniel Becker (JIRA)



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

Daniel Becker updated OOZIE-3321:
-
Attachment: OOZIE-3321.2.patch

> PySpark example fails
> -
>
> Key: OOZIE-3321
> URL: https://issues.apache.org/jira/browse/OOZIE-3321
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.0.0, 5.1.0
>Reporter: Daniel Becker
>Assignee: Daniel Becker
>Priority: Minor
> Attachments: OOZIE-3321.1.patch, OOZIE-3321.2.patch
>
>
> The PySpark example fails with the following exception:
> {noformat}
> ACTION[001-180806145017687-oozie-oozi-W@spark-node] Launcher exception: 
> Missing py4j and/or pyspark zip files. Please add them to the lib folder or 
> to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib.
>   at 
> org.apache.oozie.action.hadoop.SparkMain.getMatchingPyFile(SparkMain.java:151)
>   at 
> org.apache.oozie.action.hadoop.SparkMain.createPySparkLibFolder(SparkMain.java:132)
>   at org.apache.oozie.action.hadoop.SparkMain.run(SparkMain.java:77)
>   at 
> org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:101)
>   at org.apache.oozie.action.hadoop.SparkMain.main(SparkMain.java:60)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:410)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.access$300(LauncherAM.java:55)
>   at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:223)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:217)
>   at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:153)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:141)
> {noformat}
> This is because py4j-0.9-src.zip and pyspark.zip are not available. They are 
> needed for the example to run, so we should either add them to the sharelib 
> or if they are not important enough to be in the sharelib, we should add them 
> to the example's lib directory. Currently these two files can be found in the 
> codebase under sharelib/spark/src/test/resources. We should also decide what 
> to do with these files there, to avoid duplication of resource files.
> If I add the files manually to either the sharelib or the lib directory of 
> the example, the example runs successfilly.



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

[jira] [Commented] (OOZIE-2877) Oozie Git Action

2018-08-07 Thread Clay B. (JIRA)



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

Clay B. commented on OOZIE-2877:


Thank you guys for all the help and reviews! Indeed, I am happy to hand off the 
code for the remaining necessary steps to see this go out as part of 5.1.0.

> Oozie Git Action
> 
>
> Key: OOZIE-2877
> URL: https://issues.apache.org/jira/browse/OOZIE-2877
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action
>Reporter: Clay B.
>Assignee: Clay B.
>Priority: Major
>  Labels: action
> Fix For: trunk
>
> Attachments: 0001-OOZIE-2877-Oozie-Git-Action.patch, 
> 0002-OOZIE-2877-Oozie-Git-Action.patch, 
> 0003-OOZIE-2877-Oozie-Git-Action.patch, 
> 0004-OOZIE-2877-Oozie-Git-Action.patch, 
> 0005-OOZIE-2877-Oozie-Git-Action.patch, 
> 0006-OOZIE-2877-Oozie-Git-Action.patch, 
> 0007-OOZIE-2877-Oozie-Git-Action.patch, 
> 0008-OOZIE-2877-Oozie-Git-Action.patch, 
> 0009-OOZIE-2877-Oozie-Git-Action.patch, OOZIE-2877.010.patch, 
> OOZIE-2877.011.patch, OOZIE-2877.012.patch, OOZIE-2877.013-1.patch, 
> OOZIE-2877.013.patch, OOZIE-2877.014-1.patch, OOZIE-2877.014-2.patch, 
> OOZIE-2877.014-3.patch
>
>
> To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for 
> a source-code management system. Git would be my preferred choice.
> Ideally, this could handle a user's key material e.g. for an ssh key to pull 
> down from a secured repository. This would free users from handling their own 
> key staging and clean-up on YARN nodes and only require them to store the key 
> secured in HDFS.



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

Failed: OOZIE-3321 PreCommit Build #734

2018-08-07 Thread Apache Jenkins Server

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

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


Testing JIRA OOZIE-3321

Cleaning local git workspace



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

The patch failed the following testcases:

testPyspark(org.apache.oozie.action.hadoop.TestPyspark)

Tests failing with errors:


+1 DISTRO
+1 distro tarball builds with the patch 


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

 There is at least one warning, please check

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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  33660 0  100  3366  0   3927 --:--:-- --:--:-- --:--:--  
3927{"self":"https://issues.apache.org/jira/rest/api/2/issue/13177130/comment/16571700","id":"16571700","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3321\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:red}-1 
RAW_PATCH_ANALYSIS{color}\n.{color:green}+1{color} the patch does not 
introduce any @author tags\n.{color:green}+1{color} the patch does not 
introduce any tabs\n.{color:green}+1{color} the patch does not introduce 
any trailing spaces\n.{color:green}+1{color} the patch does not

[jira] [Commented] (OOZIE-3321) PySpark example fails

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3321:
--


Testing JIRA OOZIE-3321

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

.The patch failed the following testcases:

testPyspark(org.apache.oozie.action.hadoop.TestPyspark)

.Tests failing with errors:


{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}

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

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

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



> PySpark example fails
> -
>
> Key: OOZIE-3321
> URL: https://issues.apache.org/jira/browse/OOZIE-3321
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.0.0, 5.1.0
>Reporter: Daniel Becker
>Assignee: Daniel Becker
>Priority: Minor
> Attachments: OOZIE-3321.1.patch
>
>
> The PySpark example fails with the following exception:
> {noformat}
> ACTION[001-180806145017687-oozie-oozi-W@spark-node] Launcher exception: 
> Missing py4j and/or pyspark zip files. Please add them to the lib folder or 
> to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib.
>   at 
> org.apache.oozie.action.hadoop.SparkMain.getMatchingPyFile(SparkMain.java:151)
>   at 
> org.apache.oozie.action.hadoop.SparkMain.createPySparkLibFolder(SparkMain.java:132)
>   at org.apache.oozie.action.hadoop.SparkMain.run(SparkMain.java:77)
>   at 
> org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:101)
>   at org.apache.oozie.action.hadoop.SparkMain.main(SparkMain.java:60)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
>

Re: Review Request 68255: OOZIE 3314 - Remove findbugs-filter.xml and convert its contents to annotations

2018-08-07 Thread András Piros via Review Board


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




core/src/main/java/org/apache/oozie/command/XCommand.java
Lines 84 (patched)


Typo: eventService



core/src/main/java/org/apache/oozie/command/XCommand.java
Line 82 (original), 85 (patched)


Actually `eventService` is only written from inside one of the 
constructors, so it could - and should - be `static final`. Maybe can also be 
`private` and provide a getter for the ones wanting to reach it, or at least a 
`@VisibleForTesting`, when that's the case.



core/src/main/java/org/apache/oozie/util/Instrumentation.java
Lines 710-711 (patched)


Any other way to refactor?


- András Piros


On Aug. 7, 2018, 12:54 p.m., Andras Salamon wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68255/
> ---
> 
> (Updated Aug. 7, 2018, 12:54 p.m.)
> 
> 
> Review request for oozie, András Piros and Kinga Marton.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> 3 excptions replaced by annotations, the 4th one affects generated code, 
> still using a (simpified) XML for that.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/command/XCommand.java 7b8f47cc 
>   core/src/main/java/org/apache/oozie/util/Instrumentation.java 8bcb64c1 
>   findbugs-filter.xml 133178f0 
>   fluent-job/fluent-job-api/pom.xml 4c9b8533 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/GraphVisualization.java
>  437d6b3b 
>   fluent-job/pom.xml 5b24c911 
>   pom.xml 92358aa2 
> 
> 
> Diff: https://reviews.apache.org/r/68255/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Andras Salamon
> 
>

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

2018-08-07 Thread Andras Salamon (JIRA)



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

Andras Salamon commented on OOZIE-3314:
---

[~andras.piros] Created a review board for the request: 
[https://reviews.apache.org/r/68255/|http://example.com/]

> Remove findbugs-filter.xml and convert its contents to annotations
> --
>
> Key: OOZIE-3314
> URL: https://issues.apache.org/jira/browse/OOZIE-3314
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3314-1.patch
>
>
> In oozie-core, we have a file called "findbugs-filter.xml" which tells 
> findbugs that it shluld ignore certain problems in a couple of classes.
> However if we try to compile a sub-module or run findbugs directly (let's say 
> in a sharelib project), the build will fail because it won't be able to open 
> findbugs.xml. It's not straightforward how to define the path of the XML in a 
> way that it makes this xml accessible regardless of what module you're 
> compiling.
> It's better to just convert its contents to annotations - especially since we 
> already use this method too.



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

Review Request 68255: OOZIE 3314 - Remove findbugs-filter.xml and convert its contents to annotations

2018-08-07 Thread Andras Salamon


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

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


Repository: oozie-git


Description
---

3 excptions replaced by annotations, the 4th one affects generated code, still 
using a (simpified) XML for that.


Diffs
-

  core/src/main/java/org/apache/oozie/command/XCommand.java 7b8f47cc 
  core/src/main/java/org/apache/oozie/util/Instrumentation.java 8bcb64c1 
  findbugs-filter.xml 133178f0 
  fluent-job/fluent-job-api/pom.xml 4c9b8533 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/GraphVisualization.java
 437d6b3b 
  fluent-job/pom.xml 5b24c911 
  pom.xml 92358aa2 


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


Testing
---


Thanks,

Andras Salamon

[jira] [Commented] (OOZIE-2877) Oozie Git Action

2018-08-07 Thread Peter Bacsko (JIRA)



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

Peter Bacsko commented on OOZIE-2877:
-

I added some comments to patch 14.3. Now it looks much better and more 
readable. So good job [~clayb].

> Oozie Git Action
> 
>
> Key: OOZIE-2877
> URL: https://issues.apache.org/jira/browse/OOZIE-2877
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action
>Reporter: Clay B.
>Assignee: Clay B.
>Priority: Major
>  Labels: action
> Fix For: trunk
>
> Attachments: 0001-OOZIE-2877-Oozie-Git-Action.patch, 
> 0002-OOZIE-2877-Oozie-Git-Action.patch, 
> 0003-OOZIE-2877-Oozie-Git-Action.patch, 
> 0004-OOZIE-2877-Oozie-Git-Action.patch, 
> 0005-OOZIE-2877-Oozie-Git-Action.patch, 
> 0006-OOZIE-2877-Oozie-Git-Action.patch, 
> 0007-OOZIE-2877-Oozie-Git-Action.patch, 
> 0008-OOZIE-2877-Oozie-Git-Action.patch, 
> 0009-OOZIE-2877-Oozie-Git-Action.patch, OOZIE-2877.010.patch, 
> OOZIE-2877.011.patch, OOZIE-2877.012.patch, OOZIE-2877.013-1.patch, 
> OOZIE-2877.013.patch, OOZIE-2877.014-1.patch, OOZIE-2877.014-2.patch, 
> OOZIE-2877.014-3.patch
>
>
> To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for 
> a source-code management system. Git would be my preferred choice.
> Ideally, this could handle a user's key material e.g. for an ssh key to pull 
> down from a secured repository. This would free users from handling their own 
> key staging and clean-up on YARN nodes and only require them to store the key 
> secured in HDFS.



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

Re: Review Request 59620: This review board request is for an action to provide a Git action for Oozie

2018-08-07 Thread Peter Bacsko via Review Board


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




core/src/main/java/org/apache/oozie/action/hadoop/GitActionExecutor.java
Lines 182-183 (patched)


These nested ifs can be merged.



sharelib/git/src/main/java/org/apache/oozie/action/hadoop/GitMain.java
Lines 200-201 (patched)


Do we need this?



sharelib/git/src/main/java/org/apache/oozie/action/hadoop/GitOperations.java
Lines 92 (patched)


Typo: "Checkiging"



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/GitServer.java
Lines 52 (patched)


This solution is much better than the original.

Just one more thing: perhaps instead of hard-coding the port 9418, we could 
pick one dynamically. Or at least check if it's not occupied by some other 
process.



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitActionExecutor.java
Lines 57 (patched)


I'm just curious - how will Git know that it has to connect to the simple 
local server instead of Github?



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitActionExecutor.java
Lines 114 (patched)


Better error message would be "Expected ActionExecutorException"



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitActionExecutor.java
Lines 117 (patched)


Better error message would be "Unexpected exception message" or sth like 
that



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitActionExecutor.java
Lines 148-154 (patched)


What are we testing here exactly?

I can't see any assert() calls.



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitActionExecutor.java
Lines 183-188 (patched)


Same here



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitMain.java
Lines 101-104 (patched)


This should be replaced with a waitFor() method call - see Oozie codebase 
for examples.



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestIntegrationGitActionExecutor.java
Lines 30 (patched)


Unused import



sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestIntegrationGitActionExecutor.java
Lines 86 (patched)


readContent variable is unused


- Peter Bacsko


On aug. 3, 2018, 10 du, Clay B. wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59620/
> ---
> 
> (Updated aug. 3, 2018, 10 du)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Bugs: OOZIE-2877
> https://issues.apache.org/jira/browse/OOZIE-2877
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2877 - Oozie Git Action
> 
> 
> Diffs
> -
> 
>   client/src/main/resources/git-action-1.0.xsd PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/GitActionExecutor.java 
> PRE-CREATION 
>   core/src/main/resources/oozie-default.xml b69d2c9 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 661970d 
>   docs/src/site/twiki/WorkflowFunctionalSpec.twiki 76cbe21 
>   examples/src/main/apps/git/job.properties PRE-CREATION 
>   examples/src/main/apps/git/workflow.xml PRE-CREATION 
>   fluent-job/fluent-job-api/pom.xml 4c9b853 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/GitAction.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/GitActionBuilder.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/mapping/ExplicitNodeConverter.java
>  7bb82e5 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/mapping/GitConfigurationConverter.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/mapping/GitPrepareConverter.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/serialization/WorkflowMarshaller.java
>  ec56554 
>   fluent-job/fluent-job-api/src/main/resources/action_mappings.xml a5f890e 
>   fluent-job/fluent-job-api/src/main/xjb/bindings.xml 48f6890 
>   pom.xml 92358aa 
>   sharelib/git/pom.xml PRE-CREATION 
>

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

2018-08-07 Thread Andras Piros (JIRA)



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

Andras Piros commented on OOZIE-3314:
-

Thanks for the contribution [~asalamon74]! Can you please make a ReviewBoard 
review request? Thanks!

> Remove findbugs-filter.xml and convert its contents to annotations
> --
>
> Key: OOZIE-3314
> URL: https://issues.apache.org/jira/browse/OOZIE-3314
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3314-1.patch
>
>
> In oozie-core, we have a file called "findbugs-filter.xml" which tells 
> findbugs that it shluld ignore certain problems in a couple of classes.
> However if we try to compile a sub-module or run findbugs directly (let's say 
> in a sharelib project), the build will fail because it won't be able to open 
> findbugs.xml. It's not straightforward how to define the path of the XML in a 
> way that it makes this xml accessible regardless of what module you're 
> compiling.
> It's better to just convert its contents to annotations - especially since we 
> already use this method too.



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

[jira] [Commented] (OOZIE-3321) PySpark example fails

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3321:
--

PreCommit-OOZIE-Build started


> PySpark example fails
> -
>
> Key: OOZIE-3321
> URL: https://issues.apache.org/jira/browse/OOZIE-3321
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.0.0, 5.1.0
>Reporter: Daniel Becker
>Assignee: Daniel Becker
>Priority: Minor
> Attachments: OOZIE-3321.1.patch
>
>
> The PySpark example fails with the following exception:
> {noformat}
> ACTION[001-180806145017687-oozie-oozi-W@spark-node] Launcher exception: 
> Missing py4j and/or pyspark zip files. Please add them to the lib folder or 
> to the Spark sharelib.
> org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j 
> and/or pyspark zip files. Please add them to the lib folder or to the Spark 
> sharelib.
>   at 
> org.apache.oozie.action.hadoop.SparkMain.getMatchingPyFile(SparkMain.java:151)
>   at 
> org.apache.oozie.action.hadoop.SparkMain.createPySparkLibFolder(SparkMain.java:132)
>   at org.apache.oozie.action.hadoop.SparkMain.run(SparkMain.java:77)
>   at 
> org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:101)
>   at org.apache.oozie.action.hadoop.SparkMain.main(SparkMain.java:60)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:410)
>   at 
> org.apache.oozie.action.hadoop.LauncherAM.access$300(LauncherAM.java:55)
>   at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:223)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:217)
>   at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:153)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
>   at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:141)
> {noformat}
> This is because py4j-0.9-src.zip and pyspark.zip are not available. They are 
> needed for the example to run, so we should either add them to the sharelib 
> or if they are not important enough to be in the sharelib, we should add them 
> to the example's lib directory. Currently these two files can be found in the 
> codebase under sharelib/spark/src/test/resources. We should also decide what 
> to do with these files there, to avoid duplication of resource files.
> If I add the files manually to either the sharelib or the lib directory of 
> the example, the example runs successfilly.



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

Re: Review Request 59620: This review board request is for an action to provide a Git action for Oozie

2018-08-07 Thread Peter Bacsko via Review Board



> On júl. 2, 2018, 12:46 du, Peter Bacsko wrote:
> > docs/src/site/twiki/WorkflowFunctionalSpec.twiki
> > Lines 1667-1669 (patched)
> > 
> >
> > Do we really need to access a different cluster other than the one 
> > we're running on?
> > 
> > If key is located on a separate cluster which is secure we won't be 
> > allowed to access that file without proper credentials. Basically it's the 
> > same problem that appears under disctp. It's really not self-explanatory to 
> > setup cross-cluster authentication.
> > 
> > Therefore I'm against it. Also, the name node is available from 
> > "fs.defaultFS" property.
> 
> Clay B. wrote:
> I could certainly see someone storing a credential on a secure object 
> store (e.g. S3-like FS).

In that case, we have to mention in the docs that access control on the remote 
side must be properly configured. Eg. if it's a hdfs:// URL that points to an 
non-secure cluster, appropriate HDFS permissions are still necessary.


- Peter


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


On aug. 3, 2018, 10 du, Clay B. wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59620/
> ---
> 
> (Updated aug. 3, 2018, 10 du)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Bugs: OOZIE-2877
> https://issues.apache.org/jira/browse/OOZIE-2877
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2877 - Oozie Git Action
> 
> 
> Diffs
> -
> 
>   client/src/main/resources/git-action-1.0.xsd PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/GitActionExecutor.java 
> PRE-CREATION 
>   core/src/main/resources/oozie-default.xml b69d2c9 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 661970d 
>   docs/src/site/twiki/WorkflowFunctionalSpec.twiki 76cbe21 
>   examples/src/main/apps/git/job.properties PRE-CREATION 
>   examples/src/main/apps/git/workflow.xml PRE-CREATION 
>   fluent-job/fluent-job-api/pom.xml 4c9b853 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/GitAction.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/GitActionBuilder.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/mapping/ExplicitNodeConverter.java
>  7bb82e5 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/mapping/GitConfigurationConverter.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/mapping/GitPrepareConverter.java
>  PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/serialization/WorkflowMarshaller.java
>  ec56554 
>   fluent-job/fluent-job-api/src/main/resources/action_mappings.xml a5f890e 
>   fluent-job/fluent-job-api/src/main/xjb/bindings.xml 48f6890 
>   pom.xml 92358aa 
>   sharelib/git/pom.xml PRE-CREATION 
>   sharelib/git/src/main/java/org/apache/oozie/action/hadoop/GitMain.java 
> PRE-CREATION 
>   
> sharelib/git/src/main/java/org/apache/oozie/action/hadoop/GitOperations.java 
> PRE-CREATION 
>   sharelib/git/src/test/java/org/apache/oozie/action/hadoop/GitServer.java 
> PRE-CREATION 
>   
> sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitActionExecutor.java
>  PRE-CREATION 
>   sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestGitMain.java 
> PRE-CREATION 
>   
> sharelib/git/src/test/java/org/apache/oozie/action/hadoop/TestIntegrationGitActionExecutor.java
>  PRE-CREATION 
>   sharelib/pom.xml 6a0864d 
>   src/main/assemblies/sharelib.xml 07dc69c 
>   webapp/pom.xml fd3f89f 
> 
> 
> Diff: https://reviews.apache.org/r/59620/diff/10/
> 
> 
> Testing
> ---
> 
> Tested using unit and integration tests. Still need to:
> * Test on a cluster
> * Test with an authenticated SSH hosted Git repo
> 
> Sumitted a request to the JGit community as their branch pulling code seems 
> to have an 
> [issue](https://dev.eclipse.org/mhonarc/lists/jgit-dev/msg03343.html).
> 
> Andras has tested against his patch 011 with results at 
> https://issues.apache.org/jira/browse/OOZIE-2877?focusedCommentId=16459523=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16459523
> 
> 
> File Attachments
> 
> 
> 0001-OOZIE-2877-Oozie-Git-Action.patch
>   
> https://reviews.apache.org/media/uploaded/files/2017/05/29/24f90a78-3dc1-49fe-bf29-5927a3cd5e72__0001-OOZIE-2877-Oozie-Git-Action.patch
> Patch
>   
>

[jira] [Commented] (OOZIE-3298) OYA: external ID is not filled properly and failing MR job is treated as SUCCEEDED

2018-08-07 Thread Andras Piros (JIRA)



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

Andras Piros commented on OOZIE-3298:
-

[~asasvari] sure thing, [*here u go*|https://reviews.apache.org/r/68237/].

> OYA: external ID is not filled properly and failing MR job is treated as 
> SUCCEEDED
> --
>
> Key: OOZIE-3298
> URL: https://issues.apache.org/jira/browse/OOZIE-3298
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3298.001.patch, OOZIE-3298.002.patch, 
> OOZIE-3298.003.patch
>
>
> When a MapReduce action is launched from Oozie (OYA), we don't properly fill 
> the external ID field. It gets populated with the YARN id of the LauncherAM, 
> not with the id of the actual MR job. If the MR job is succesfully submitted 
> then fails, it will be treated as a successfully executed action, which is 
> very misleading and can potentially confuse Oozie users.



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

[jira] [Commented] (OOZIE-3298) OYA: external ID is not filled properly and failing MR job is treated as SUCCEEDED

2018-08-07 Thread Attila Sasvari (JIRA)



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

Attila Sasvari commented on OOZIE-3298:
---

Can you file a reviewboard request?

> OYA: external ID is not filled properly and failing MR job is treated as 
> SUCCEEDED
> --
>
> Key: OOZIE-3298
> URL: https://issues.apache.org/jira/browse/OOZIE-3298
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Peter Bacsko
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3298.001.patch, OOZIE-3298.002.patch, 
> OOZIE-3298.003.patch
>
>
> When a MapReduce action is launched from Oozie (OYA), we don't properly fill 
> the external ID field. It gets populated with the YARN id of the LauncherAM, 
> not with the id of the actual MR job. If the MR job is succesfully submitted 
> then fails, it will be treated as a successfully executed action, which is 
> very misleading and can potentially confuse Oozie users.



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

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3314:
--


Testing JIRA OOZIE-3314

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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2914
.{color:orange}Tests failed at first run:{color}
TestBundleRerunXCommand#testBundleRerunInPausedWithError
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

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



> Remove findbugs-filter.xml and convert its contents to annotations
> --
>
> Key: OOZIE-3314
> URL: https://issues.apache.org/jira/browse/OOZIE-3314
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3314-1.patch
>
>
> In oozie-core, we have a file called "findbugs-filter.xml" which tells 
> findbugs that it shluld ignore certain problems in a couple of classes.
> However if we try to compile a sub-module or run findbugs directly (let's say 
> in a sharelib project), the build will fail because it won't be able to open 
> findbugs.xml. It's not straightforward how to define the path of the XML in a 
> way that it makes this xml accessible regardless of what module you're 
> compiling.
> It's better to just convert its contents to annotations - especially since we 
> already use this method too.



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

Failed: OOZIE-3314 PreCommit Build #733

2018-08-07 Thread Apache Jenkins Server

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

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


Testing JIRA OOZIE-3314

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2914
Tests failed at first run:
TestBundleRerunXCommand#testBundleRerunInPausedWithError
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


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


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

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

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

Failed: OOZIE-3320 PreCommit Build #732

2018-08-07 Thread Apache Jenkins Server

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

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


Testing JIRA OOZIE-3320

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/spark].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2914
Tests failed at first run:
TestCoordChangeXCommand#testCoordChangeEndTime3
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32810 0  100  3281  0   4814 --:--:-- --:--:-- --:--:--  
4810{"self":"https://issues.apache.org/jira/rest/api/2/issue/13176985/comment/16571435","id":"16571435","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3320:
--


Testing JIRA OOZIE-3320

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 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
{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: 2914
.{color:orange}Tests failed at first run:{color}
TestCoordChangeXCommand#testCoordChangeEndTime3
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

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



> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3320
> URL: https://issues.apache.org/jira/browse/OOZIE-3320
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Roey Shem Tov
>Assignee: Roey Shem Tov
>Priority: Major
>  Labels: patch
> Attachments: OOZIE-3086.patch
>
>
> bash files that saved on shared mount, cannot be execute by the ShellAction 
> in proper way.
> Example:
> Worker-1,Worker-2,Worker-3 have shared mount /mnt/hadoop
> on /mnt/hadoop there is a file script.sh
> Right now there is two options to submit it using ShellAction:
>  # Upload it to hdfs, add it as a file and submit script.sh
>  # use bash as exec and file location (/mnt/hadoop/script.sh) as argument 
> (e.g bash>/exec>/mnt/hadoop/script.sh
> Best option is that the  command will support shared mounted file :
> /mnt/hadoop/script.sh
>  
> This code is taking only the file name instead it full path:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); 
> String execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
> Best option to support shared mount file is to support file:// starting for 
> bash files that are local (or shared by mount), e.g:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim();

[jira] [Commented] (OOZIE-2877) Oozie Git Action

2018-08-07 Thread Andras Piros (JIRA)



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

Andras Piros commented on OOZIE-2877:
-

Thanks for the updated patches [~clayb]! Would love to see Git action as part 
of {{5.1.0}}.

If you don't mind I can address the remaining few issues like pre-commit, clean 
code, etc. to have a smooth and rapid way towards {{master}}, based on [*patch 
14-3*|https://issues.apache.org/jira/secure/attachment/12934336/OOZIE-2877.014-3.patch].

> Oozie Git Action
> 
>
> Key: OOZIE-2877
> URL: https://issues.apache.org/jira/browse/OOZIE-2877
> Project: Oozie
>  Issue Type: Sub-task
>  Components: action
>Reporter: Clay B.
>Assignee: Clay B.
>Priority: Major
>  Labels: action
> Fix For: trunk
>
> Attachments: 0001-OOZIE-2877-Oozie-Git-Action.patch, 
> 0002-OOZIE-2877-Oozie-Git-Action.patch, 
> 0003-OOZIE-2877-Oozie-Git-Action.patch, 
> 0004-OOZIE-2877-Oozie-Git-Action.patch, 
> 0005-OOZIE-2877-Oozie-Git-Action.patch, 
> 0006-OOZIE-2877-Oozie-Git-Action.patch, 
> 0007-OOZIE-2877-Oozie-Git-Action.patch, 
> 0008-OOZIE-2877-Oozie-Git-Action.patch, 
> 0009-OOZIE-2877-Oozie-Git-Action.patch, OOZIE-2877.010.patch, 
> OOZIE-2877.011.patch, OOZIE-2877.012.patch, OOZIE-2877.013-1.patch, 
> OOZIE-2877.013.patch, OOZIE-2877.014-1.patch, OOZIE-2877.014-2.patch, 
> OOZIE-2877.014-3.patch
>
>
> To aide in deploying ASCII artifacts to clusters, let's provide a tie-in for 
> a source-code management system. Git would be my preferred choice.
> Ideally, this could handle a user's key material e.g. for an ssh key to pull 
> down from a secured repository. This would free users from handling their own 
> key staging and clean-up on YARN nodes and only require them to store the key 
> secured in HDFS.



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

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3314:
--

PreCommit-OOZIE-Build started


> Remove findbugs-filter.xml and convert its contents to annotations
> --
>
> Key: OOZIE-3314
> URL: https://issues.apache.org/jira/browse/OOZIE-3314
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3314-1.patch
>
>
> In oozie-core, we have a file called "findbugs-filter.xml" which tells 
> findbugs that it shluld ignore certain problems in a couple of classes.
> However if we try to compile a sub-module or run findbugs directly (let's say 
> in a sharelib project), the build will fail because it won't be able to open 
> findbugs.xml. It's not straightforward how to define the path of the XML in a 
> way that it makes this xml accessible regardless of what module you're 
> compiling.
> It's better to just convert its contents to annotations - especially since we 
> already use this method too.



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

[jira] [Updated] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

2018-08-07 Thread Andras Salamon (JIRA)



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

Andras Salamon updated OOZIE-3314:
--
Attachment: (was: OOZIE-3314-1.patch)

> Remove findbugs-filter.xml and convert its contents to annotations
> --
>
> Key: OOZIE-3314
> URL: https://issues.apache.org/jira/browse/OOZIE-3314
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
>
> In oozie-core, we have a file called "findbugs-filter.xml" which tells 
> findbugs that it shluld ignore certain problems in a couple of classes.
> However if we try to compile a sub-module or run findbugs directly (let's say 
> in a sharelib project), the build will fail because it won't be able to open 
> findbugs.xml. It's not straightforward how to define the path of the XML in a 
> way that it makes this xml accessible regardless of what module you're 
> compiling.
> It's better to just convert its contents to annotations - especially since we 
> already use this method too.



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

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

2018-08-07 Thread Andras Piros (JIRA)



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

Andras Piros commented on OOZIE-3320:
-

Thanks for the contribution [~roeyshemtov24]!

Can you please extract the code to a method e.g. {{resolveExecutable()}}, and 
surround {{if-else}} with brackets? Thanks! And, please, also update the 
documentation {{DG_ShellActionExtension.twiki}}.

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3320
> URL: https://issues.apache.org/jira/browse/OOZIE-3320
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Roey Shem Tov
>Assignee: Roey Shem Tov
>Priority: Major
>  Labels: patch
> Attachments: OOZIE-3086.patch
>
>
> bash files that saved on shared mount, cannot be execute by the ShellAction 
> in proper way.
> Example:
> Worker-1,Worker-2,Worker-3 have shared mount /mnt/hadoop
> on /mnt/hadoop there is a file script.sh
> Right now there is two options to submit it using ShellAction:
>  # Upload it to hdfs, add it as a file and submit script.sh
>  # use bash as exec and file location (/mnt/hadoop/script.sh) as argument 
> (e.g bash>/exec>/mnt/hadoop/script.sh
> Best option is that the  command will support shared mounted file :
> /mnt/hadoop/script.sh
>  
> This code is taking only the file name instead it full path:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); 
> String execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
> Best option to support shared mount file is to support file:// starting for 
> bash files that are local (or shared by mount), e.g:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); String execName; 
> String localFilePrefix = "file://";
>  // When exec starts with 'file://' refer it as local file. 
> if (exec.startsWith(localFilePrefix)) 
> execName = exec.substring(localFilePrefix.length()); 
> else execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
>  
>  



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

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

2018-08-07 Thread Hadoop QA (JIRA)



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

Hadoop QA commented on OOZIE-3320:
--

PreCommit-OOZIE-Build started


> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3320
> URL: https://issues.apache.org/jira/browse/OOZIE-3320
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Roey Shem Tov
>Assignee: Roey Shem Tov
>Priority: Major
>  Labels: patch
> Attachments: OOZIE-3086.patch
>
>
> bash files that saved on shared mount, cannot be execute by the ShellAction 
> in proper way.
> Example:
> Worker-1,Worker-2,Worker-3 have shared mount /mnt/hadoop
> on /mnt/hadoop there is a file script.sh
> Right now there is two options to submit it using ShellAction:
>  # Upload it to hdfs, add it as a file and submit script.sh
>  # use bash as exec and file location (/mnt/hadoop/script.sh) as argument 
> (e.g bash>/exec>/mnt/hadoop/script.sh
> Best option is that the  command will support shared mounted file :
> /mnt/hadoop/script.sh
>  
> This code is taking only the file name instead it full path:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); 
> String execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
> Best option to support shared mount file is to support file:// starting for 
> bash files that are local (or shared by mount), e.g:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); String execName; 
> String localFilePrefix = "file://";
>  // When exec starts with 'file://' refer it as local file. 
> if (exec.startsWith(localFilePrefix)) 
> execName = exec.substring(localFilePrefix.length()); 
> else execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
>  
>  



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

[jira] [Assigned] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

2018-08-07 Thread Andras Piros (JIRA)



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

Andras Piros reassigned OOZIE-3320:
---

Assignee: Roey Shem Tov

> Oozie ShellAction should support absolute bash file path
> 
>
> Key: OOZIE-3320
> URL: https://issues.apache.org/jira/browse/OOZIE-3320
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Roey Shem Tov
>Assignee: Roey Shem Tov
>Priority: Major
>  Labels: patch
> Attachments: OOZIE-3086.patch
>
>
> bash files that saved on shared mount, cannot be execute by the ShellAction 
> in proper way.
> Example:
> Worker-1,Worker-2,Worker-3 have shared mount /mnt/hadoop
> on /mnt/hadoop there is a file script.sh
> Right now there is two options to submit it using ShellAction:
>  # Upload it to hdfs, add it as a file and submit script.sh
>  # use bash as exec and file location (/mnt/hadoop/script.sh) as argument 
> (e.g bash>/exec>/mnt/hadoop/script.sh
> Best option is that the  command will support shared mounted file :
> /mnt/hadoop/script.sh
>  
> This code is taking only the file name instead it full path:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); 
> String execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
> Best option to support shared mount file is to support file:// starting for 
> bash files that are local (or shared by mount), e.g:
> {code:java}
> String exec = actionXml.getChild("exec", ns).getTextTrim(); String execName; 
> String localFilePrefix = "file://";
>  // When exec starts with 'file://' refer it as local file. 
> if (exec.startsWith(localFilePrefix)) 
> execName = exec.substring(localFilePrefix.length()); 
> else execName = new Path(exec).getName(); 
> actionConf.set(ShellMain.CONF_OOZIE_SHELL_EXEC, execName);
> {code}
>  
>  
>  



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

[jira] [Commented] (OOZIE-3318) Fix Javadoc check in the pre-commit

2018-08-07 Thread Julia Kinga Marton (JIRA)



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

Julia Kinga Marton commented on OOZIE-3318:
---

The pre-patch is failing because for this phase, the original script is used, 
and is causing failure because of dependency issues. In the script I have fixed 
it both in pre and post part as well, and I expect it to work fine after the 
changeset integration.

> Fix Javadoc check in the pre-commit
> ---
>
> Key: OOZIE-3318
> URL: https://issues.apache.org/jira/browse/OOZIE-3318
> Project: Oozie
>  Issue Type: Sub-task
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3318.001.patch, OOZIE-3318.002.patch
>
>
> Javadoc check builds are broken in the pre-commit



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

[jira] [Commented] (OOZIE-3318) Fix Javadoc check in the pre-commit

2018-08-07 Thread Julia Kinga Marton (JIRA)



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

Julia Kinga Marton commented on OOZIE-3318:
---

Still not good. the pre-patch Javadoc generation failed. 

> Fix Javadoc check in the pre-commit
> ---
>
> Key: OOZIE-3318
> URL: https://issues.apache.org/jira/browse/OOZIE-3318
> Project: Oozie
>  Issue Type: Sub-task
>  Components: scripts
>Affects Versions: 5.0.0
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3318.001.patch, OOZIE-3318.002.patch
>
>
> Javadoc check builds are broken in the pre-commit



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

[jira] Subscription: Oozie Patch Available

2018-08-07 Thread jira

Issue Subscription
Filter: Oozie Patch Available (94 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3319  Log SSH action callback error output
https://issues.apache.org/jira/browse/OOZIE-3319
OOZIE-3318  Fix Javadoc check in the pre-commit
https://issues.apache.org/jira/browse/OOZIE-3318
OOZIE-3304  Parsing sharelib timestamps is not threadsafe
https://issues.apache.org/jira/browse/OOZIE-3304
OOZIE-3301  Update NOTICE file
https://issues.apache.org/jira/browse/OOZIE-3301
OOZIE-3298  OYA: external ID is not filled properly and failing MR job is 
treated as SUCCEEDED
https://issues.apache.org/jira/browse/OOZIE-3298
OOZIE-3274  Remove slf4j
https://issues.apache.org/jira/browse/OOZIE-3274
OOZIE-3266  Coord action rerun support RERUN_SKIP_NODES option
https://issues.apache.org/jira/browse/OOZIE-3266
OOZIE-3265  properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to 
appear together
https://issues.apache.org/jira/browse/OOZIE-3265
OOZIE-3256  refactor OozieCLI class
https://issues.apache.org/jira/browse/OOZIE-3256
OOZIE-3249  [tools] Instrumentation log parser
https://issues.apache.org/jira/browse/OOZIE-3249
OOZIE-3229  Improved filtering options in V2SLAServlet
https://issues.apache.org/jira/browse/OOZIE-3229
OOZIE-3218  Oozie Sqoop action with command splits the select clause into 
multiple parts due to delimiter being space
https://issues.apache.org/jira/browse/OOZIE-3218
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3196  Authorization: restrict world readability by user
https://issues.apache.org/jira/browse/OOZIE-3196
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3160  PriorityDelayQueue put()/take() can cause significant CPU load due 
to busy waiting
https://issues.apache.org/jira/browse/OOZIE-3160
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2734  Switch docs from twiki to markdown
https://issues.apache.org/jira/browse/OOZIE-2734
OOZIE-2714  Detect conflicting resources during class loading

[jira] [Commented] (OOZIE-3321) PySpark example fails

Failed: OOZIE-3321 PreCommit Build #735

[jira] [Commented] (OOZIE-3321) PySpark example fails

[jira] [Commented] (OOZIE-3321) PySpark example fails

[jira] [Updated] (OOZIE-3321) PySpark example fails

[jira] [Commented] (OOZIE-2877) Oozie Git Action

Failed: OOZIE-3321 PreCommit Build #734

[jira] [Commented] (OOZIE-3321) PySpark example fails

Re: Review Request 68255: OOZIE 3314 - Remove findbugs-filter.xml and convert its contents to annotations

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

Review Request 68255: OOZIE 3314 - Remove findbugs-filter.xml and convert its contents to annotations

[jira] [Commented] (OOZIE-2877) Oozie Git Action

Re: Review Request 59620: This review board request is for an action to provide a Git action for Oozie

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

[jira] [Commented] (OOZIE-3321) PySpark example fails

Re: Review Request 59620: This review board request is for an action to provide a Git action for Oozie

[jira] [Commented] (OOZIE-3298) OYA: external ID is not filled properly and failing MR job is treated as SUCCEEDED

[jira] [Commented] (OOZIE-3298) OYA: external ID is not filled properly and failing MR job is treated as SUCCEEDED

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

Failed: OOZIE-3314 PreCommit Build #733

Failed: OOZIE-3320 PreCommit Build #732

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

[jira] [Commented] (OOZIE-2877) Oozie Git Action

[jira] [Commented] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

[jira] [Updated] (OOZIE-3314) Remove findbugs-filter.xml and convert its contents to annotations

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

[jira] [Commented] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

[jira] [Assigned] (OOZIE-3320) Oozie ShellAction should support absolute bash file path

[jira] [Commented] (OOZIE-3318) Fix Javadoc check in the pre-commit

[jira] [Commented] (OOZIE-3318) Fix Javadoc check in the pre-commit

[jira] Subscription: Oozie Patch Available

31 matches

Site Navigation

Mail list logo

Footer information