Failed: OOZIE-3298 PreCommit Build #814

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 9.43 MB...]
[DEBUG] There are no new bugs found in [sharelib/git].
[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/sqoop].
[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 [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 [webapp].
[WARN] There are [4] new bugs found in total that would be nice to have fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2616 bytes
[TRACE] Full summary file size is 1601 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-3298

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 adds/modifies 6 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
0 There are [4] new bugs found in total that would be nice to have fixed.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 0 There are [4] new bugs found in [core] that would be nice to have fixed.
 You can find the FindBugs diff here: core/findbugs-new.html
 +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 [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [webapp].
+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
There were errors during execution. Check console output for details.
+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/814/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3298:
--


Testing JIRA OOZIE-3298

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 adds/modifies 6 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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:orange}0{color} There are [4] new bugs found in total that would be nice 
to have fixed.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:orange}0{color} There are [4] new bugs found in [core] that would be 
nice to have fixed.
. You can find the FindBugs diff here: core/findbugs-new.html
. {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 
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [webapp].
{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}
There were errors during execution. Check console output for details.
{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/814/



> 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, OOZIE-3298.004.patch, OOZIE-3298.005.patch, 
> OOZIE-3298.007.patch, OOZIE-3298.008.patch, OOZIE-3298.009.patch, 
> OOZIE-3298.010.patch, OOZIE-3298.011.patch, OOZIE-3298.012.patch, 
> OOZIE-3298.013.patch, OOZIE-3298.014.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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3298:
--

PreCommit-OOZIE-Build started


> 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, OOZIE-3298.004.patch, OOZIE-3298.005.patch, 
> OOZIE-3298.007.patch, OOZIE-3298.008.patch, OOZIE-3298.009.patch, 
> OOZIE-3298.010.patch, OOZIE-3298.011.patch, OOZIE-3298.012.patch, 
> OOZIE-3298.013.patch, OOZIE-3298.014.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

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3298:
-

Addressing last FindBugs error.

> 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, OOZIE-3298.004.patch, OOZIE-3298.005.patch, 
> OOZIE-3298.007.patch, OOZIE-3298.008.patch, OOZIE-3298.009.patch, 
> OOZIE-3298.010.patch, OOZIE-3298.011.patch, OOZIE-3298.012.patch, 
> OOZIE-3298.013.patch, OOZIE-3298.014.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)

Re: Review Request 68237: OOZIE-3298 OYA: external ID is not filled properly and failing MR job is treated as SUCCEEDED

[András Piros via Review Board]

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

(Updated Sept. 10, 2018, 3:37 p.m.)


Review request for oozie, Andras Salamon, Attila Sasvari, Kinga Marton, and 
Peter Bacsko.


Changes
---

Addressing last FindBugs error.


Repository: oozie-git


Description
---

OOZIE-3298 OYA: external ID is not filled properly and failing MR job is 
treated as SUCCEEDED


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
05fac3953eed5a5e2a16fa362656596f3a962a88 
  
core/src/main/java/org/apache/oozie/action/hadoop/MapReduceActionExecutor.java 
83a23f5220aa72ba15edc8b98ef80a74213fcee8 
  core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
f39bba2c691435354dac6da7794e5142b511d937 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
a31079a41d30677d35a253a4a69505c21aa585f6 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestYarnApplicationIdComparator.java
 PRE-CREATION 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestYarnApplicationIdFinder.java
 PRE-CREATION 
  
core/src/test/java/org/apache/oozie/action/oozie/TestSubWorkflowActionExecutor.java
 893405e38ad71d22460768b76ed03ac4d9a0b95d 
  sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
c9e2a914a4b88640ac1c370b8971355dc087a235 
  
sharelib/streaming/src/test/java/org/apache/oozie/action/hadoop/TestMapReduceActionExecutor.java
 f460b6bd11f60dfb397c6bba82be1427c2d1b570 


Diff: https://reviews.apache.org/r/68237/diff/11/

Changes: https://reviews.apache.org/r/68237/diff/10-11/


Testing
---

Tested on a real cluster, plus added test cases to 
`TestMapReduceActionExecutor` and new test classes.


Thanks,

András Piros

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

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3298:

Attachment: OOZIE-3298.014.patch

> 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, OOZIE-3298.004.patch, OOZIE-3298.005.patch, 
> OOZIE-3298.007.patch, OOZIE-3298.008.patch, OOZIE-3298.009.patch, 
> OOZIE-3298.010.patch, OOZIE-3298.011.patch, OOZIE-3298.012.patch, 
> OOZIE-3298.013.patch, OOZIE-3298.014.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

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3298:
-

Thanks [~pbacsko] for the review rounds! Uploading last (?) patch handling the 
last FindBugs error.

> 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, OOZIE-3298.004.patch, OOZIE-3298.005.patch, 
> OOZIE-3298.007.patch, OOZIE-3298.008.patch, OOZIE-3298.009.patch, 
> OOZIE-3298.010.patch, OOZIE-3298.011.patch, OOZIE-3298.012.patch, 
> OOZIE-3298.013.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

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3298:
-

+1 from me, just take care of that Findbugs error.

> 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, OOZIE-3298.004.patch, OOZIE-3298.005.patch, 
> OOZIE-3298.007.patch, OOZIE-3298.008.patch, OOZIE-3298.009.patch, 
> OOZIE-3298.010.patch, OOZIE-3298.011.patch, OOZIE-3298.012.patch, 
> OOZIE-3298.013.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)

Re: Review Request 68628: OOZIE-2734 - Switch docs from twiki to markdown

[András Piros via Review Board]

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



Reviewed following HTML / Markdown files:

 * `AG_ActionConfiguration`
 * `AG_HadoopConfiguration`
 * `AG_Install`
 * `AG_Monitoring`
 * `AG_OozieLogging`
 * `AG_OozieUpgrade`
 * `BundleFunctionalSpec`
 * `CoordinatorFunctionalSpec`


docs/src/site/twiki/AG_Install.twiki
Lines 243-245 (patched)


html



docs/src/site/twiki/BundleFunctionalSpec.twiki
Lines 93-101 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Lines 607-620 (original), 634-647 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Line 875 (original), 919 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Lines 890-900 (original), 934-944 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Lines 975-980 (original), 1019-1024 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Line 1009 (original), 1053 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Lines 1047-1075 (original), 1091-1119 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Lines 1886-1889 (original), 1956-1959 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Lines 3509-3511 (original), 3622-3624 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Lines 3514-3515 (original), 3627-3628 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Line 3609 (original), 3728 (patched)


html



docs/src/site/twiki/CoordinatorFunctionalSpec.twiki
Line 3630 (original), 3751 (patched)


html


- András Piros


On Sept. 5, 2018, 10 a.m., Andras Salamon wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68628/
> ---
> 
> (Updated Sept. 5, 2018, 10 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2734 - Switch docs from twiki to markdown
> 
> 
> Diffs
> -
> 
>   docs/pom.xml ae2e94c9c 
>   docs/src/site/markdown/AG_OozieLogging.md PRE-CREATION 
>   docs/src/site/markdown/ENG_Building.md PRE-CREATION 
>   docs/src/site/markdown/index.md PRE-CREATION 
>   docs/src/site/twiki/AG_ActionConfiguration.twiki 8c032a754 
>   docs/src/site/twiki/AG_HadoopConfiguration.twiki 528bf4a41 
>   docs/src/site/twiki/AG_Install.twiki b8031c82e 
>   docs/src/site/twiki/AG_Monitoring.twiki 425f55435 
>   docs/src/site/twiki/AG_OozieLogging.twiki ecdcfd33e 
>   docs/src/site/twiki/AG_OozieUpgrade.twiki 302406482 
>   docs/src/site/twiki/BundleFunctionalSpec.twiki 9749df597 
>   docs/src/site/twiki/CoordinatorFunctionalSpec.twiki cd416d4cd 
>   docs/src/site/twiki/DG_ActionAuthentication.twiki bbf2d57d3 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 8d33c508e 
>   docs/src/site/twiki/DG_CoordinatorRerun.twiki fbb1376d5 
>   docs/src/site/twiki/DG_CustomActionExecutor.twiki 783148495 
>   docs/src/site/twiki/DG_DistCpActionExtension.twiki 8bab3da44 
>   docs/src/site/twiki/DG_EmailActionExtension.twiki 4de290ccf 
>   docs/src/site/twiki/DG_Examples.twiki 5323a1773 
>   docs/src/site/twiki/DG_FluentJobAPI.twiki c8b764bb0 
>   docs/src/site/twiki/DG_HCatalogIntegration.twiki d3107b453 
>   docs/src/site/twiki/DG_Hive2ActionExtension.twiki efbe56dab 
>   docs/src/site/twiki/DG_HiveActionExtension.twiki aaa74fa7b 
>   docs/src/site/twiki/DG_JMSNotifications.twiki a4b0f0d1a 
>   docs/src/site/twiki/DG_Overview.twiki 3ec94a2f1 
>   docs/src/site/twiki/DG_QuickStart.twiki d6a0069ac 
>   docs/src/site/twiki/DG_SLAMonitoring.twiki c91c227dc 
>   docs/src/site/twiki/DG_ShellActionExtension.twiki 5894c280a 
>   docs/src/site/twiki/DG_SparkActionExtension.twiki ce80e45fc 
>   docs/src/site/twiki/DG_SqoopActionExtension.twiki 0317d0cec 
>   docs/src/site/twiki/DG_SshActionExtension.twiki 5a51d49c5 
>   docs/src/site/twiki/DG_WorkflowReRun.twiki 88d982b75 
>   docs/src/site/twiki/ENG_Building.twiki b86102683 
>   

Re: Review Request 68628: OOZIE-2734 - Switch docs from twiki to markdown

[Kinga Marton via Review Board]

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



Checked pages:

ENG_MiniOozie.html
ENG_Custom_Authentication.html
ENG_Building.html
DG_WorkflowReRun.html
DG_SshActionExtension.html
DG_SqoopActionExtension.html
DG_SparkActionExtension.html
DG_SLAMonitoring.html


docs/src/site/twiki/DG_SLAMonitoring.twiki
Line 361 (original), 386 (patched)


html - header level (indentation at the summary)



docs/src/site/twiki/DG_SLAMonitoring.twiki
Line 399 (original), 428 (patched)


html - header level (indentation at the summary)



docs/src/site/twiki/DG_SLAMonitoring.twiki
Line 405 (original), 434 (patched)


html - header level (indentation at the summary)



docs/src/site/twiki/DG_SLAMonitoring.twiki
Line 408 (original), 437 (patched)


html - header level (indentation at the summary)



docs/src/site/twiki/DG_WorkflowReRun.twiki
Lines 10-13 (original), 10-13 (patched)


html


- Kinga Marton


On Sept. 5, 2018, 10 a.m., Andras Salamon wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68628/
> ---
> 
> (Updated Sept. 5, 2018, 10 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2734 - Switch docs from twiki to markdown
> 
> 
> Diffs
> -
> 
>   docs/pom.xml ae2e94c9c 
>   docs/src/site/markdown/AG_OozieLogging.md PRE-CREATION 
>   docs/src/site/markdown/ENG_Building.md PRE-CREATION 
>   docs/src/site/markdown/index.md PRE-CREATION 
>   docs/src/site/twiki/AG_ActionConfiguration.twiki 8c032a754 
>   docs/src/site/twiki/AG_HadoopConfiguration.twiki 528bf4a41 
>   docs/src/site/twiki/AG_Install.twiki b8031c82e 
>   docs/src/site/twiki/AG_Monitoring.twiki 425f55435 
>   docs/src/site/twiki/AG_OozieLogging.twiki ecdcfd33e 
>   docs/src/site/twiki/AG_OozieUpgrade.twiki 302406482 
>   docs/src/site/twiki/BundleFunctionalSpec.twiki 9749df597 
>   docs/src/site/twiki/CoordinatorFunctionalSpec.twiki cd416d4cd 
>   docs/src/site/twiki/DG_ActionAuthentication.twiki bbf2d57d3 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 8d33c508e 
>   docs/src/site/twiki/DG_CoordinatorRerun.twiki fbb1376d5 
>   docs/src/site/twiki/DG_CustomActionExecutor.twiki 783148495 
>   docs/src/site/twiki/DG_DistCpActionExtension.twiki 8bab3da44 
>   docs/src/site/twiki/DG_EmailActionExtension.twiki 4de290ccf 
>   docs/src/site/twiki/DG_Examples.twiki 5323a1773 
>   docs/src/site/twiki/DG_FluentJobAPI.twiki c8b764bb0 
>   docs/src/site/twiki/DG_HCatalogIntegration.twiki d3107b453 
>   docs/src/site/twiki/DG_Hive2ActionExtension.twiki efbe56dab 
>   docs/src/site/twiki/DG_HiveActionExtension.twiki aaa74fa7b 
>   docs/src/site/twiki/DG_JMSNotifications.twiki a4b0f0d1a 
>   docs/src/site/twiki/DG_Overview.twiki 3ec94a2f1 
>   docs/src/site/twiki/DG_QuickStart.twiki d6a0069ac 
>   docs/src/site/twiki/DG_SLAMonitoring.twiki c91c227dc 
>   docs/src/site/twiki/DG_ShellActionExtension.twiki 5894c280a 
>   docs/src/site/twiki/DG_SparkActionExtension.twiki ce80e45fc 
>   docs/src/site/twiki/DG_SqoopActionExtension.twiki 0317d0cec 
>   docs/src/site/twiki/DG_SshActionExtension.twiki 5a51d49c5 
>   docs/src/site/twiki/DG_WorkflowReRun.twiki 88d982b75 
>   docs/src/site/twiki/ENG_Building.twiki b86102683 
>   docs/src/site/twiki/ENG_Custom_Authentication.twiki 3b8202d0d 
>   docs/src/site/twiki/ENG_MiniOozie.twiki 0b1628986 
>   docs/src/site/twiki/WebServicesAPI.twiki f9008a60b 
>   docs/src/site/twiki/WorkflowFunctionalSpec.twiki 46a454c3a 
>   docs/src/site/twiki/index.twiki 3003fa992 
>   pom.xml 423d19d97 
> 
> 
> Diff: https://reviews.apache.org/r/68628/diff/1/
> 
> 
> Testing
> ---
> 
> HTML generated
> 
> 
> Thanks,
> 
> Andras Salamon
> 
>

[jira] [Created] (OOZIE-3342) Missing examples archive from fluentjob examples

[Andras Salamon (JIRA)]

Andras Salamon created OOZIE-3342:
-

 Summary: Missing examples archive from fluentjob examples
 Key: OOZIE-3342
 URL: https://issues.apache.org/jira/browse/OOZIE-3342
 Project: Oozie
  Issue Type: Improvement
  Components: examples
Reporter: Andras Salamon
Assignee: Andras Salamon


When {{-runjar}} option is used to execute a fluentjob example, oozie sets the 
app path to a newly created (timestamped) directory and copies the freshly 
generated {{workflow.xml}} file to this directory:
{noformat}
/user/username/oozie-fluent-job-api-generated/gen_app_1536586664643{noformat}
This directory does not contain any other {{jar}} file, hence some of the 
examples are not working. 

For instance the 
[JavaMain|https://github.com/apache/oozie/blob/master/examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java]
 example cannot find the DemoJavaMain class:
{noformat}
180910095203189-oozie-andr-W] 
ACTION[020-180910095203189-oozie-andr-W@java-main] Launcher exception: 
java.lang.ClassNotFoundException: Class org.apache.oozie.example.DemoJavaMain 
not found
java.lang.RuntimeException: java.lang.ClassNotFoundException: Class 
org.apache.oozie.example.DemoJavaMain not found{noformat}
 
The examples should be modified to allow the user to specify the path of an 
archive which contains the necessary files.
 



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

Re: Review Request 68237: OOZIE-3298 OYA: external ID is not filled properly and failing MR job is treated as SUCCEEDED

[Peter Bacsko via Review Board]

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


Ship it!




Ship It!

- Peter Bacsko


On szept. 7, 2018, 8:08 de, András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68237/
> ---
> 
> (Updated szept. 7, 2018, 8:08 de)
> 
> 
> Review request for oozie, Andras Salamon, Attila Sasvari, Kinga Marton, and 
> Peter Bacsko.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3298 OYA: external ID is not filled properly and failing MR job is 
> treated as SUCCEEDED
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 05fac3953eed5a5e2a16fa362656596f3a962a88 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/MapReduceActionExecutor.java
>  83a23f5220aa72ba15edc8b98ef80a74213fcee8 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java 
> f39bba2c691435354dac6da7794e5142b511d937 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> a31079a41d30677d35a253a4a69505c21aa585f6 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestYarnApplicationIdComparator.java
>  PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestYarnApplicationIdFinder.java
>  PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/action/oozie/TestSubWorkflowActionExecutor.java
>  893405e38ad71d22460768b76ed03ac4d9a0b95d 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java 
> c9e2a914a4b88640ac1c370b8971355dc087a235 
>   
> sharelib/streaming/src/test/java/org/apache/oozie/action/hadoop/TestMapReduceActionExecutor.java
>  f460b6bd11f60dfb397c6bba82be1427c2d1b570 
> 
> 
> Diff: https://reviews.apache.org/r/68237/diff/10/
> 
> 
> Testing
> ---
> 
> Tested on a real cluster, plus added test cases to 
> `TestMapReduceActionExecutor` and new test classes.
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Created] (OOZIE-3341) Fix difference between command line help and command line documentation

[Andras Salamon (JIRA)]

Andras Salamon created OOZIE-3341:
-

 Summary: Fix difference between command line help and command line 
documentation
 Key: OOZIE-3341
 URL: https://issues.apache.org/jira/browse/OOZIE-3341
 Project: Oozie
  Issue Type: Improvement
Reporter: Andras Salamon
Assignee: Andras Salamon


The {{help}} command of the oozie CLI prints out usage information. It is also 
possible to print out only for the specified command, for instance:
{noformat}
oozie help job{noformat}
This information is also available in the 
[twiki|https://github.com/apache/oozie/blob/master/docs/src/site/twiki/DG_CommandLineTool.twiki]
 documentation and in the generated HTML.

There are several differences, the twiki (HTML) looks outdated. For instance 
for {{job}} command lists the fluent job options as {{apijarcheck}}, 
{{apijarsubmit}}, and {{apijarrun}} but these options has been renamed to 
{{validatejar}}, {{submitjar}}, and {{runjar}}. The CLI help shows the correct 
names.



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

[jira] [Updated] (OOZIE-3340) Fix FluentJob API Shell and MultipleShellActions example

[Andras Salamon (JIRA)]

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

Andras Salamon updated OOZIE-3340:
--
Description: 
The Shell and MultipleShellActions example of the Fluent Job API generates 
multiple actions with the same name ({{email-on-error}}) which gives {{E0705}} 
error code.

For MultipleShellActions the generated XML:
{noformat}
Workflow job definition generated from API jar: 




Action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]



someb...@apache.org
Workflow error
Shell action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]





...


   ...


...


...


...

...
{noformat}

The error message:

{noformat}
bin/oozie job -oozie http://localhost:11000/oozie -runjar fluenttest.jar 
-config job.properties -verbose
...
Error: E0705 : E0705: Nnode already defined, node [email-on-error]
{noformat}

The Shell example also creates an XML with multiple {{email-on-error}} actions.

  was:
The MultipleShellActions example of the Fluent Job API generates multiple 
actions with the same name ({{email-on-error}}) which gives {{E0705}} error 
code:

{noformat}Workflow job definition generated from API jar: 




Action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]



someb...@apache.org
Workflow error
Shell action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]





...


   ...


...


...


...

...
{noformat}

{noformat}bin/oozie job -oozie http://localhost:11000/oozie -runjar 
fluenttest.jar -config job.properties -verbose
...
Error: E0705 : E0705: Nnode already defined, node [email-on-error]
{noformat}




> Fix FluentJob API Shell and MultipleShellActions example
> 
>
> Key: OOZIE-3340
> URL: https://issues.apache.org/jira/browse/OOZIE-3340
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
>
> The Shell and MultipleShellActions example of the Fluent Job API generates 
> multiple actions with the same name ({{email-on-error}}) which gives 
> {{E0705}} error code.
> For MultipleShellActions the generated XML:
> {noformat}
> Workflow job definition generated from API jar: 
> 
>  xmlns:workflow="uri:oozie:workflow:1.0" 
> xmlns:shell="uri:oozie:shell-action:1.0" name="shell-example">
> 
> 
> Action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> someb...@apache.org
> Workflow error
> Shell action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> 
> 
> ...
> 
> 
>...
> 
> 
> ...
> 
> 
> ...
> 
> 
> ...
> 
> ...
> {noformat}
> The error message:
> {noformat}
> bin/oozie job -oozie http://localhost:11000/oozie -runjar fluenttest.jar 
> -config job.properties -verbose
> ...
> Error: E0705 : E0705: Nnode already defined, node [email-on-error]
> {noformat}
> The Shell example also creates an XML with multiple {{email-on-error}} 
> actions.



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

[jira] [Updated] (OOZIE-3340) Fix FluentJob API Shell and MultipleShellActions example

[Andras Salamon (JIRA)]

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

Andras Salamon updated OOZIE-3340:
--
Summary: Fix FluentJob API Shell and MultipleShellActions example  (was: 
Fix FluentJob API MultipleShellActions example)

> Fix FluentJob API Shell and MultipleShellActions example
> 
>
> Key: OOZIE-3340
> URL: https://issues.apache.org/jira/browse/OOZIE-3340
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
>
> The MultipleShellActions example of the Fluent Job API generates multiple 
> actions with the same name ({{email-on-error}}) which gives {{E0705}} error 
> code:
> {noformat}Workflow job definition generated from API jar: 
> 
>  xmlns:workflow="uri:oozie:workflow:1.0" 
> xmlns:shell="uri:oozie:shell-action:1.0" name="shell-example">
> 
> 
> Action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> someb...@apache.org
> Workflow error
> Shell action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> 
> 
> ...
> 
> 
>...
> 
> 
> ...
> 
> 
> ...
> 
> 
> ...
> 
> ...
> {noformat}
> {noformat}bin/oozie job -oozie http://localhost:11000/oozie -runjar 
> fluenttest.jar -config job.properties -verbose
> ...
> Error: E0705 : E0705: Nnode already defined, node [email-on-error]
> {noformat}



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

[jira] [Created] (OOZIE-3340) Fix FluentJob API MultipleShellActions example

[Andras Salamon (JIRA)]

Andras Salamon created OOZIE-3340:
-

 Summary: Fix FluentJob API MultipleShellActions example
 Key: OOZIE-3340
 URL: https://issues.apache.org/jira/browse/OOZIE-3340
 Project: Oozie
  Issue Type: Improvement
  Components: examples
Reporter: Andras Salamon
Assignee: Andras Salamon


The MultipleShellActions example of the Fluent Job API generates multiple 
actions with the same name ({{email-on-error}}) which gives {{E0705}} error 
code:

{noformat}Workflow job definition generated from API jar: 




Action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]



someb...@apache.org
Workflow error
Shell action failed, error 
message[${wf:errorMessage(wf:lastErrorNode())}]





...


   ...


...


...


...

...
{noformat}

{noformat}bin/oozie job -oozie http://localhost:11000/oozie -runjar 
fluenttest.jar -config job.properties -verbose
...
Error: E0705 : E0705: Nnode already defined, node [email-on-error]
{noformat}





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

Failed: OOZIE-2734 PreCommit Build #813

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.83 MB...]
[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 [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 [core].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[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].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2488 bytes
[TRACE] Full summary file size is 1471 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-2734

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 contains 3 line(s) with tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 311 line(s) longer than 132 characters
-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 generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/git].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +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 [core].
 +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 [tools].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
There were errors during execution. Check console output for details.
+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/813/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32540 0  100  3254  0   5502 --:--:-- --:--:-- --:--:--  

[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2734:
--


Testing JIRA OOZIE-2734

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:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 311 line(s) longer than 132 
characters
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in 
[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 [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{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/813/



> Switch docs from twiki to markdown
> --
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, 
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, 
> OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch, 
> oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it 

[jira] [Created] (OOZIE-3339) Enhance proxy job submission documentation

[Andras Salamon (JIRA)]

Andras Salamon created OOZIE-3339:
-

 Summary: Enhance proxy job submission documentation
 Key: OOZIE-3339
 URL: https://issues.apache.org/jira/browse/OOZIE-3339
 Project: Oozie
  Issue Type: Improvement
  Components: docs
Reporter: Andras Salamon
Assignee: Andras Salamon


The documentation should make it clear that the proxy job submission methods 
can only be used for simple job submissions (e.g. no support for credentials) 
and the documentation should  suggest an alternative if someone wants a more 
complex workflow.



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

[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2734:
--

PreCommit-OOZIE-Build started


> Switch docs from twiki to markdown
> --
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, 
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, 
> OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch, 
> oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



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

[jira] [Created] (OOZIE-3338) Remove SVN references

[Andras Salamon (JIRA)]

Andras Salamon created OOZIE-3338:
-

 Summary: Remove SVN references
 Key: OOZIE-3338
 URL: https://issues.apache.org/jira/browse/OOZIE-3338
 Project: Oozie
  Issue Type: Improvement
  Components: build, docs
Affects Versions: trunk
Reporter: Andras Salamon
Assignee: Andras Salamon


Oozie 
[documentation|https://github.com/apache/oozie/blob/master/docs/src/site/twiki/ENG_MiniOozie.twiki#L20-L26]
 still refers to the SVN server:
{noformat}
https://svn.apache.org/repos/asf/incubator/oozie/trunk
{noformat}
which is no longer available.

The current address is the following:
{noformat}
https://svn.apache.org/repos/asf/oozie/
{noformat}
It only contains a README file and forwards to the git server.

We should remove the SVN references from the file.

 

It would also be useful to simplify 
[mkdistro.sh|https://github.com/apache/oozie/blob/master/bin/mkdistro.sh] and 
remove the SVN support.



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

[jira] [Updated] (OOZIE-2734) Switch docs from twiki to markdown

[Andras Salamon (JIRA)]

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

Andras Salamon updated OOZIE-2734:
--
Attachment: OOZIE-2734-8.patch

> Switch docs from twiki to markdown
> --
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, 
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, 
> OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch, 
> oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



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

[jira] [Updated] (OOZIE-2734) Switch docs from twiki to markdown

[Andras Salamon (JIRA)]

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

Andras Salamon updated OOZIE-2734:
--
Attachment: oozie_generated_html_markdown_20180910.zip

> Switch docs from twiki to markdown
> --
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Andras Salamon
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, 
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, 
> OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch, 
> oozie_generated_html_20180731.zip, 
> oozie_generated_html_markdown_20180802.zip, 
> oozie_generated_html_markdown_20180905.zip, 
> oozie_generated_html_markdown_20180910.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



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

[jira] [Resolved] (OOZIE-3174) Allow users to retain SQL file generated by OozieDBCLI

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton resolved OOZIE-3174.
---
Resolution: Won't Fix

> Allow users to retain SQL file generated by OozieDBCLI
> --
>
> Key: OOZIE-3174
> URL: https://issues.apache.org/jira/browse/OOZIE-3174
> Project: Oozie
>  Issue Type: Improvement
>  Components: tools
>Affects Versions: trunk
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
>
> OozieDBCLI writes SQL statements to a temporary file. It is deleted without 
> question at the end of the execution (see OOZIE-2727). We should allow the 
> user to decide if they want to delete it or not.



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

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (91 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3326  Sqoop Action should support tez delegation tokens for hive-import
https://issues.apache.org/jira/browse/OOZIE-3326
OOZIE-3320  Oozie ShellAction should support absolute bash file path
https://issues.apache.org/jira/browse/OOZIE-3320
OOZIE-3319  Log SSH action callback error output
https://issues.apache.org/jira/browse/OOZIE-3319
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-3277  [build] Check for star imports in patches in pre-commit
https://issues.apache.org/jira/browse/OOZIE-3277
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-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-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-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
https://issues.apache.org/jira/browse/OOZIE-2714
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693