[jira] [Assigned] (OOZIE-2854) Oozie should handle transient DB problems

[Andras Piros (JIRA)]

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

Andras Piros reassigned OOZIE-2854:
---

Assignee: Andras Piros  (was: Peter Bacsko)

> Oozie should handle transient DB problems
> -
>
> Key: OOZIE-2854
> URL: https://issues.apache.org/jira/browse/OOZIE-2854
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Piros
> Attachments: OOZIE-2854-001.patch, OOZIE-2854-002.patch, 
> OOZIE-2854-003.patch, OOZIE-2854-004.patch, OOZIE-2854-005.patch, 
> OOZIE-2854-POC-001.patch
>
>
> There can be problems when Oozie cannot update the database properly. 
> Recently, we have experienced erratic behavior with two setups:
> * MySQL with the Galera cluster manager. Galera uses cluster-wide optimistic 
> locking which might cause a transaction to rollback if there are two or more 
> parallel transaction running and one of them cannot complete because of a 
> conflict.
> * MySQL with Percona XtraDB Cluster. If one of the MySQL instances is killed, 
> Oozie might get "Communications link failure" exception during the failover.
> The problem is that failed DB transactions later might cause a workflow 
> (which are started/re-started by RecoveryService) to get stuck. It's not 
> clear to us how this happens but it has to do with the fact that certain DB 
> updates are not executed.
> The solution is to use some sort of retry logic with exponential backoff if 
> the DB update fails. We could start with a 100ms wait time which is doubled 
> at every retry. The operation can be considered a failure if it still fails 
> after 10 attempts. These values could be configurable. We should discuss 
> initial values in the scope of this JIRA.
> Note that this solution is to handle *transient* failures. If the DB is down 
> for a longer period of time, we have to accept that the internal state of 
> Oozie is corrupted.



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

[jira] [Assigned] (OOZIE-2794) Hive and Pig tests failing when multiple pre-commit jobs are running

[Peter Cseh (JIRA)]

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

Peter Cseh reassigned OOZIE-2794:
-

Assignee: Peter Cseh

> Hive and Pig tests failing when multiple pre-commit jobs are running
> 
>
> Key: OOZIE-2794
> URL: https://issues.apache.org/jira/browse/OOZIE-2794
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2794.patch
>
>
> There are multiple cases when the following tests are failing together:
> {noformat}
> . testMain(org.apache.oozie.action.hadoop.TestHiveMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
> . testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
> . testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
> . testLoadDump(org.apache.oozie.tools.TestDBLoadDump)
> {noformat}
> This issue seems to occur when multiple pre-commit jobs are running. 



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

[jira] [Updated] (OOZIE-2794) Hive and Pig tests failing when multiple pre-commit jobs are running

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2794:
--
Attachment: OOZIE-2794.patch

Attaching a patch. Note, that I can't reproduce the issue locally.
I've looked into the tests and figured that each of them is writing to the 
testCaseDir and validating the output file's content. This could  cause issues 
if jenkins is using the same workspace for multiple jobs.

> Hive and Pig tests failing when multiple pre-commit jobs are running
> 
>
> Key: OOZIE-2794
> URL: https://issues.apache.org/jira/browse/OOZIE-2794
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
> Attachments: OOZIE-2794.patch
>
>
> There are multiple cases when the following tests are failing together:
> {noformat}
> . testMain(org.apache.oozie.action.hadoop.TestHiveMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
> . testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
> . testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
> . testLoadDump(org.apache.oozie.tools.TestDBLoadDump)
> {noformat}
> This issue seems to occur when multiple pre-commit jobs are running. 



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

[jira] [Commented] (OOZIE-2794) Hive and Pig tests failing when multiple pre-commit jobs are running

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2794:
-

+1

This is a small change. We can give it a try.

> Hive and Pig tests failing when multiple pre-commit jobs are running
> 
>
> Key: OOZIE-2794
> URL: https://issues.apache.org/jira/browse/OOZIE-2794
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2794.patch
>
>
> There are multiple cases when the following tests are failing together:
> {noformat}
> . testMain(org.apache.oozie.action.hadoop.TestHiveMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
> . testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
> . testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
> . testLoadDump(org.apache.oozie.tools.TestDBLoadDump)
> {noformat}
> This issue seems to occur when multiple pre-commit jobs are running. 



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

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

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2943:
---

+1

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



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

[jira] [Commented] (OOZIE-2848) Override sharelib.tgz in distro when rebuilding Oozie

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2848:
---

+1

> Override sharelib.tgz in distro when rebuilding Oozie
> -
>
> Key: OOZIE-2848
> URL: https://issues.apache.org/jira/browse/OOZIE-2848
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2848-01.patch
>
>
> Building Oozie with {{mvn package assembly:single -Dfindbugs.skip=true 
> -DskipTests -DjavaVersion=1.8 -DtargetVersion=1.7 -Puber}} twice in a row 
> results in the following error:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default-cli) on 
> project oozie-distro: Failed to create assembly: Error creating assembly 
> archive distro: Problem copying files : 
> /Users/asasvari/workspace/apache/oozie_dup/distro/target/oozie-4.4.0-SNAPSHOT-distro/oozie-4.4.0-SNAPSHOT/oozie-sharelib-4.4.0-SNAPSHOT.tar.gz
>  (Permission denied) -> [Help 1]
> {code}
> We can override the target like it is done for Oozie Client and TAR.GZ-s.



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

[jira] [Commented] (OOZIE-2662) DB migration fails if DB is too big

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2662:
-

[~andras.piros] could you pls update the RB review? It's possibly out of sync 
with your latest patch (btw why is it in "submitted"?)

> DB migration fails if DB is too big
> ---
>
> Key: OOZIE-2662
> URL: https://issues.apache.org/jira/browse/OOZIE-2662
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Andras Piros
> Attachments: OOZIE-2662.001.patch, OOZIE-2662.002.patch, 
> OOZIE-2662.002.wip.patch, OOZIE-2662.003.patch
>
>
> The initial version of the DB import tool commits all the workflows, actions 
> etc. in one huge commit. If it does not fits into the memory, AOOME is thrown.
> We should commit every 1k or 10k elements to prevent this.



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

Re: Review Request 52782: OOZIE-2662 DB migration fails if DB is too big

[András Piros]

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

(Updated June 27, 2017, 10:14 a.m.)


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


Changes
---

Syncing w/ upstream patch.


Repository: oozie-git


Description
---

We get each 1000 rows into a separate JPA `EntityTransaction` to reduce heap 
size. Furthermore, of at least one row inside that tx fails, we retry the whole 
batch into separate `EntityTransaction`s each.

Following error handling is implemented:

1. check if all necessary tables are present and empty
2. rows are imported till the end even if there are skipped rows in the 
meanwhile
3. if at least one row is skipped in the meanwhile for some 
`ConstraintViolationException`, we delete all rows of all necessary tables. 
That enables the user to have the log messages of all the erroneous rows in one 
run, and Oozie database is never in an inconsistent state of some rows present, 
some not present of an import


Diffs (updated)
-

  tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java 0e14a30 
  tools/src/test/java/org/apache/oozie/tools/TestDBLoadDump.java c43223e 
  tools/src/test/resources/dumpData/invalid/ooziedb_ac.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_bna.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_bnj.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_ca.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_cj.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_slareg.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_slasum.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_sysinfo.json PRE-CREATION 
  tools/src/test/resources/dumpData/invalid/ooziedb_wf.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_ac.json 22bbdc2 
  tools/src/test/resources/dumpData/ooziedb_bna.json e69de29 
  tools/src/test/resources/dumpData/ooziedb_bnj.json e69de29 
  tools/src/test/resources/dumpData/ooziedb_ca.json 2715b94 
  tools/src/test/resources/dumpData/ooziedb_cj.json 979c10e 
  tools/src/test/resources/dumpData/ooziedb_slareg.json e69de29 
  tools/src/test/resources/dumpData/ooziedb_slasum.json e69de29 
  tools/src/test/resources/dumpData/ooziedb_sysinfo.json 15de009 
  tools/src/test/resources/dumpData/ooziedb_wf.json 05e7e36 
  tools/src/test/resources/dumpData/valid/ooziedb_ac.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_bna.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_bnj.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_ca.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_cj.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_slareg.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_slasum.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_sysinfo.json PRE-CREATION 
  tools/src/test/resources/dumpData/valid/ooziedb_wf.json PRE-CREATION 


Diff: https://reviews.apache.org/r/52782/diff/3/

Changes: https://reviews.apache.org/r/52782/diff/2-3/


Testing
---

See `TestDBLoadDump` for further reference.


Thanks,

András Piros

[jira] [Commented] (OOZIE-2662) DB migration fails if DB is too big

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2662:
-

[~pbacsko] updated and reopened RB issue for review.

> DB migration fails if DB is too big
> ---
>
> Key: OOZIE-2662
> URL: https://issues.apache.org/jira/browse/OOZIE-2662
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Andras Piros
> Attachments: OOZIE-2662.001.patch, OOZIE-2662.002.patch, 
> OOZIE-2662.002.wip.patch, OOZIE-2662.003.patch
>
>
> The initial version of the DB import tool commits all the workflows, actions 
> etc. in one huge commit. If it does not fits into the memory, AOOME is thrown.
> We should commit every 1k or 10k elements to prevent this.



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

[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2849:
---

+1 
Decreasing the number of warnings in the build is a good thing. 

> Fix build warnings when assembling directories
> --
>
> Key: OOZIE-2849
> URL: https://issues.apache.org/jira/browse/OOZIE-2849
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
>Priority: Trivial
> Attachments: OOZIE-2849-01.patch, OOZIE-2849-02.patch
>
>
> When building oozie we can observe a lot of warning
> {code}
> [WARNING] Assembly file: 
> /Users/asasvari/workspace/apache/oozie_dup/tools/target/oozie-tools-4.4.0-SNAPSHOT-tools
>  is not a regular file (it may be a directory). It cannot be attached to the 
> project build for installation or deployment.
> {code}
> This behaviour can be explained by 
> https://issues.apache.org/jira/browse/MASSEMBLY-628



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

[jira] [Commented] (OOZIE-2585) Disable or remove test case TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and testMemoryUsageAndSpeed

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2585:
---

[~pbacsko], can you rebase patch-2? It does not apply to master anymore.

> Disable or remove test case 
> TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk 
> and testMemoryUsageAndSpeed
> ---
>
> Key: OOZIE-2585
> URL: https://issues.apache.org/jira/browse/OOZIE-2585
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2585-001.patch, OOZIE-2585-002.patch
>
>
> There is a problem with the test case testMemoryUsageAndSpeedOverflowToDisk.
> After 20k entries, data is spilled to the disk. However, Ehcache writes on a 
> separate thread asynchronously and all put operations return immediately. The 
> problem is that after storing the 60k entries, we try to read them back 
> instantly, with many of them are still being flushed to the storage. As long 
> as disk write in progress, these entries are unavailable.
> I didn't find a reliable way to wait for disk writes. Therefore I suggest 
> disabling this test or eliminate it altogether -- it's a performance test 
> that runs on all kinds of machines during a build, I don't think it makes too 
> much sense to keep it.
> Also testMemoryUsageAndSpeed might be prone to test failures too - these two 
> assertions might evaluate to false:
> {code}
> assertTrue((endTime - startTime) < insertTimeinMillis);
> ...
> assertTrue((System.currentTimeMillis() - endTime) < retrievalTimeinMillis);
> {code}



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

[jira] [Commented] (OOZIE-2004) Improve Oozie version info output

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2004:
---

Thanks for the contribution!
I think updating the admin servlet as well would be great!
Instead of returning only the build version, we could pass the whole properties 
object as a json in 
[BaseAdminServlet|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/servlet/BaseAdminServlet.java#L149]

> Improve Oozie version info output
> -
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
>Reporter: Chunjun Xiao
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-2004-0.patch
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of  Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r 
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul  6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}



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

[jira] [Commented] (OOZIE-2956) Fix Findbugs warnings related to reliance on default encoding in oozie-core

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2956:
--

Testing JIRA OOZIE-2956

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1968
.Tests failed: 0
.Tests errors: 63

.The patch failed the following testcases:

.  

.Tests failing with errors:
.  
testAuthorizationServiceForBundle(org.apache.oozie.service.TestAuthorizationService)
.  
testAdminUsersWithAdminFile(org.apache.oozie.service.TestAuthorizationService)
.  
testAdminUsersWithAdminGroup(org.apache.oozie.service.TestAuthorizationService)
.  
testAuthorizationServiceForCoord(org.apache.oozie.service.TestAuthorizationService)
.  
testAuthorizationServiceUseDefaultGroup(org.apache.oozie.service.TestAuthorizationService)
.  testDefaultGroup(org.apache.oozie.service.TestAuthorizationService)
.  testErrors(org.apache.oozie.service.TestAuthorizationService)
.  
testAuthorizationServiceUseACLs(org.apache.oozie.service.TestAuthorizationService)
.  testRerunFork(org.apache.oozie.command.wf.TestReRunXCommand)
.  
testPurgeMissingDependencies(org.apache.oozie.service.TestHAPartitionDependencyManagerEhCache)
.  
testDependencyCacheWithHA(org.apache.oozie.service.TestHAPartitionDependencyManagerEhCache)
.  
testCheckAfterActionDelete(org.apache.oozie.service.TestHAPartitionDependencyManagerEhCache)
.  
testActionInputCheckLatestActionCreationTimeWithPushDependency(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
.  
testActionInputCheckLatestCurrentTimeWithPushDependency(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
.  
testHCatCanonicalHostName(org.apache.oozie.service.TestPartitionDependencyManagerService)
.  
testActionCheckerService(org.apache.oozie.service.TestActionCheckerService)
.  
testActionCheckerServiceCoord(org.apache.oozie.service.TestActionCheckerService)
.  
testActionCheckerServiceDelay(org.apache.oozie.service.TestActionCheckerService)
.  testEndError(org.apache.oozie.command.wf.TestActionErrors)
.  
testStartNonTransientWithCoordActionUpdate(org.apache.oozie.command.wf.TestActionErrors)
.  
testKillNodeErrorMessageError(org.apache.oozie.command.wf.TestActionErrors)
.  testEndDataNotSet(org.apache.oozie.command.wf.TestActionErrors)
.  testStartErrorWithUserRetry(org.apache.oozie.command.wf.TestActionErrors)
.  
testKillNodeErrorMessageError2(org.apache.oozie.command.wf.TestActionErrors)
.  testStartTransient(org.apache.oozie.command.wf.TestActionErrors)
.  testKillNodeErrorMessage(org.apache.oozie.command.wf.TestActionErrors)
.  testStartNonTransient(org.apache.oozie.command.wf.TestActionErrors)
.  testEndNonTransient(org.apache.oozie.command.wf.TestActionErrors)
.  testExecutionDataNotSet(org.apache.oozie.command.wf.TestActionErrors)
.  testEndErrorWithUserRetry(org.apache.oozie.command.wf.TestActionErrors)
.  
testEndNonTransientWithCoordActionUpdate(org.apache.oozie.command.wf.TestActionErrors)
.  testEndTransient(org.apache.oozie.command.wf.TestActionErrors)
.  testStartError(org.apache.oozie.command.wf.TestActionErrors)
.  
testActionInputCheckLatestActionCreationTimeWithPushDependency(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
.  
testActionInputCheckLatestCurrentTimeWithPushDependency(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
.  
testPurgeMissingDependencies(org.apache.oozie.service.TestHAPartitionDependenc

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

[Apache Jenkins Server]

See 


--
[...truncated 402.22 KB...]
[INFO] Building Apache Oozie Distro 5.0.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

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

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

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-distro ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/distro.xml
[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] Building tar : 

[INFO] 
[INFO] 
[INFO] Building Apache Oozie ZooKeeper Security Tests 5.0.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

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

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ 
oozie-zookeeper-security-tests ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
oozie-zookeeper-security-tests ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  2.078 s]
[INFO] Apache Oozie Client  SUCCESS [ 22.968 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  3.012 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  1.934 s]
[INFO] Apac

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

[Apache Jenkins Server]

See 


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

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 058baab44f8fa4b9a64fbf93a2f996c916d7df9c 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 058baab44f8fa4b9a64fbf93a2f996c916d7df9c
 > git rev-list 058baab44f8fa4b9a64fbf93a2f996c916d7df9c # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson3444549259463637583.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0  0   
  00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0  0 0 
   0 00 0  0  0 --:--:--  0:00:05 --:--:-- 0  0 0   
 0 00 0  0  0 --:--:--  0:00:06 --:--:-- 0  0 0
0 00 0  0  0 --:--:--  0:00:07 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:08 --:--:-- 0  0 00   
  00 0  0  0 --:--:--  0:00:09 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:10 --:--:-- 0  0 00 0 
   0 0  0  0 --:--:--  0:00:11 --:--:-- 0  0 00 0   
 0 0  0  0 --:--:--  0:00:12 --:--:-- 0  0 00 0
0 0  0  0 --:--:--  0:00:13 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:14 --:--:-- 0  0 00 00   
  0  0  0 --:--:--  0:00:15 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:16 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:17 --:--:-- 0  0 00 00 0   
   0  0 --:--:--  0:00:18 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:19 --:--:-- 0  0 00 00 0  
0  0 --:--:--  0:00:20 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:21 --:--:-- 0  0 00 00 0  0   
   0 --:--:--  0:00:22 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:23 --:--:-- 0  0 00 00 0  0  
0 --:--:--  0:00:24 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:25 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:26 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:27 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:28 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:29 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:30 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:31 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:32 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:33 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:34 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:35 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:36 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:37 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:38 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:39 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:40 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:41 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:42 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:43 -

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

[Apache Jenkins Server]

See 

[jira] [Commented] (OOZIE-2964) getting at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2964:
-

[~gezapeti] please review

> getting at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> ---
>
> Key: OOZIE-2964
> URL: https://issues.apache.org/jira/browse/OOZIE-2964
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
> Environment: java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Mac OSX 10.12.5
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2964-0.patch
>
>
> steps to reproduce
> {noformat}
> ./bin/mkdistro.sh -DskipTests=true -DtargetJavaVersion=1.8 -DjavaVersion=1.8
> {noformat}
> Refer to the generated Javadoc files in 
> '/Users/aervits/NetBeansProjects/OOZIE-AbstractJavadocMojo/oozie/core/target/site/apidocs'
>  dir.
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
> at 
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:2075)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:130)
> at 
> org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:318)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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:497)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)



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

[jira] [Commented] (OOZIE-2963) getting error in build ArtifactNotFoundException: Could not find artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2963:
-

[~gezapeti] please review

> getting error in build ArtifactNotFoundException: Could not find artifact 
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
> ---
>
> Key: OOZIE-2963
> URL: https://issues.apache.org/jira/browse/OOZIE-2963
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
>  Labels: newbie
> Fix For: trunk
>
> Attachments: OOZIE-2963-0.patch, OOZIE-2963-1.patch
>
>
> getting the following message in build output
> {noformat}
> [ERROR] Artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde 
> not found.
> org.apache.maven.artifact.resolver.ArtifactNotFoundException: Could not find 
> artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in 
> repository.cloudera.com 
> (https://repository.cloudera.com/artifactory/ext-release-local)
> Try downloading the file manually from the project website.
> Then, install it using the command: 
> mvn install:install-file -DgroupId=org.pentaho 
> -DartifactId=pentaho-aggdesigner-algorithm -Dversion=5.1.5-jhyde 
> -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: 
> mvn deploy:deploy-file -DgroupId=org.pentaho 
> -DartifactId=pentaho-aggdesigner-algorithm -Dversion=5.1.5-jhyde 
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>   org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
> from the specified remote repositories:
>   repository.cloudera.com 
> (https://repository.cloudera.com/artifactory/ext-release-local, 
> releases=true, snapshots=false),
>   central (https://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false),
>   central (http://repo1.maven.org/maven2, releases=true, snapshots=false),
>   apache.snapshots.repo 
> (https://repository.apache.org/content/groups/snapshots, releases=true, 
> snapshots=true),
>   datanucleus (http://www.datanucleus.org/downloads/maven2, releases=true, 
> snapshots=false),
>   Nexus (http://repository.apache.org/snapshots, releases=false, 
> snapshots=true)
>   at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:221)
>   at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:154)
>   at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:562)
>   at 
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.resolve(RepositoryUtils.java:153)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.resolveAtrifacts(DependenciesRenderer.java:1280)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:513)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:240)
>   at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
>   at 
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:201)
>   at 
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
>   at 
> org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute(AbstractProjectInfoReport.java:234)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>   at org.apache.maven.Defa

[jira] [Commented] (OOZIE-2960) many warnings for @return tag has no arguments

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2960:
-

[~gezapeti] please review

> many warnings for @return tag has no arguments
> --
>
> Key: OOZIE-2960
> URL: https://issues.apache.org/jira/browse/OOZIE-2960
> Project: Oozie
>  Issue Type: Task
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2960-0.patch, OOZIE-2960-1.patch
>
>
> in my latest build, I counted 66 instances of message 
> {code}@return tag has no arguments{code}



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

[jira] [Commented] (OOZIE-2961) build contains multiple warnings for is not a parameter name

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2961:
-

[~gezapeti] another attempt to reduce the number of warnings during build, 
please review

> build contains multiple warnings for is not a parameter name
> 
>
> Key: OOZIE-2961
> URL: https://issues.apache.org/jira/browse/OOZIE-2961
> Project: Oozie
>  Issue Type: Task
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>  Labels: newbie
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2961-0.patch
>
>




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

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

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2931:
-

[~gezapeti] please review

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



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

[jira] [Commented] (OOZIE-2884) consolidate hadoop versions in pomfiles

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2884:
-

[~gezapeti] please review

> consolidate hadoop versions in pomfiles
> ---
>
> Key: OOZIE-2884
> URL: https://issues.apache.org/jira/browse/OOZIE-2884
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2884-0.patch, OOZIE-2884-1.patch, 
> OOZIE-2884-2.patch
>
>
> There are some hadoop versions from the old days which can be set separately.
> -Dhadoop.auth.version= - defaults to hadoop version
> -Ddistcp.version= - defaults to hadoop version
> They could be consolidated down to hadoop.version



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

[jira] [Commented] (OOZIE-2061) Remove CoordJobDeleteJPAExecutor

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2061:
-

[~gezapeti] please review

> Remove CoordJobDeleteJPAExecutor
> 
>
> Key: OOZIE-2061
> URL: https://issues.apache.org/jira/browse/OOZIE-2061
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Shwetha G S
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: trunk, 5.0.0
>
> Attachments: OOZIE-2061-0.patch
>
>
> Looks like CoordJobDeleteJPAExecutor is not used anywhere. Remove if not 
> required



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

[jira] [Commented] (OOZIE-2794) Hive and Pig tests failing when multiple pre-commit jobs are running

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2794:
--

Testing JIRA OOZIE-2794

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1968
.Tests rerun: 79
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.jms.TestJMSJobEventListener,org.apache.oozie.action.hadoop.TestLauncherAM,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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

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

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

. https://builds.apache.org/job/oozie-trunk-precommit-build/3927/

> Hive and Pig tests failing when multiple pre-commit jobs are running
> 
>
> Key: OOZIE-2794
> URL: https://issues.apache.org/jira/browse/OOZIE-2794
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2794.patch
>
>
> There are multiple cases when the following tests are failing together:
> {noformat}
> . testMain(org.apache.oozie.action.hadoop.TestHiveMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
> . testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
> . testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
> . testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
> . testLoadDump(org.apache.oozie.tools.TestDBLoadDump)
> {noformat}
> This issue seems to occur when multiple pre-commit jobs are running. 



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

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

[Apache Jenkins Server]

See 

[jira] [Created] (OOZIE-2970) Coordinator calculates wrong year on January 1st when started in future

[Julian Endres (JIRA)]

Julian Endres created OOZIE-2970:


 Summary: Coordinator calculates wrong year on January 1st when 
started in future
 Key: OOZIE-2970
 URL: https://issues.apache.org/jira/browse/OOZIE-2970
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.2.0
 Environment: Hadoop HDP 2.5.3
Reporter: Julian Endres


In our coordinator application we use the function combination 
coord:formatTime(coord:nominalTime()) a lot to calculate some critical 
properties e.g. for SQL statements.

Sometimes we run the Coordinator with a start time and end time in the past (we 
are catching up some workflow instances / data sets). Usually this works well 
and the values of the properties get calculated correctly.

However, when I was just setting a Coordinator (Timezone is UTC) to start at 
2017-01-01T00:00Z, with a frequency of 60 minutes the whole first of January 
e.g. the function 

${coord:formatTime(coord:nominalTime(),"-MM-dd'T'HH")}

returned the wrong year for example *2016*-01-01T01, *2016*-01-01T02... and so 
on.

On the second of January all the calculations where correct with 2017-01-02T01 
etc.



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

[jira] [Updated] (OOZIE-2854) Oozie should handle transient database problems

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2854:

Summary: Oozie should handle transient database problems  (was: Oozie 
should handle transient DB problems)

> Oozie should handle transient database problems
> ---
>
> Key: OOZIE-2854
> URL: https://issues.apache.org/jira/browse/OOZIE-2854
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Piros
> Attachments: OOZIE-2854-001.patch, OOZIE-2854-002.patch, 
> OOZIE-2854-003.patch, OOZIE-2854-004.patch, OOZIE-2854-005.patch, 
> OOZIE-2854-POC-001.patch
>
>
> There can be problems when Oozie cannot update the database properly. 
> Recently, we have experienced erratic behavior with two setups:
> * MySQL with the Galera cluster manager. Galera uses cluster-wide optimistic 
> locking which might cause a transaction to rollback if there are two or more 
> parallel transaction running and one of them cannot complete because of a 
> conflict.
> * MySQL with Percona XtraDB Cluster. If one of the MySQL instances is killed, 
> Oozie might get "Communications link failure" exception during the failover.
> The problem is that failed DB transactions later might cause a workflow 
> (which are started/re-started by RecoveryService) to get stuck. It's not 
> clear to us how this happens but it has to do with the fact that certain DB 
> updates are not executed.
> The solution is to use some sort of retry logic with exponential backoff if 
> the DB update fails. We could start with a 100ms wait time which is doubled 
> at every retry. The operation can be considered a failure if it still fails 
> after 10 attempts. These values could be configurable. We should discuss 
> initial values in the scope of this JIRA.
> Note that this solution is to handle *transient* failures. If the DB is down 
> for a longer period of time, we have to accept that the internal state of 
> Oozie is corrupted.



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

[jira] [Moved] (OOZIE-2971) Print out current tokens in LauncherAM

[Peter Bacsko (JIRA)]

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

Peter Bacsko moved MAPREDUCE-6906 to OOZIE-2971:


Issue Type: Improvement  (was: Bug)
   Key: OOZIE-2971  (was: MAPREDUCE-6906)
   Project: Oozie  (was: Hadoop Map/Reduce)

> Print out current tokens in LauncherAM
> --
>
> Key: OOZIE-2971
> URL: https://issues.apache.org/jira/browse/OOZIE-2971
> Project: Oozie
>  Issue Type: Improvement
>Reporter: Peter Cseh
>
> We should print out the list of available tokens in the LauncherAM, similar 
> to what MapReduce does:
> https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java#L1709



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

[jira] [Updated] (OOZIE-2004) Improve Oozie version info output

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2004:

Attachment: OOZIE-2004-1.patch

added similar output to admin servlet version.

> Improve Oozie version info output
> -
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
>Reporter: Chunjun Xiao
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-2004-0.patch, OOZIE-2004-1.patch
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of  Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r 
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul  6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}



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

[jira] [Commented] (OOZIE-2854) Oozie should handle transient database problems

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2854:
-

Taken over from [~pbacsko]. Walking that same path w/ following extensions.

h5. Failure injection
* subclass {{org.apache.commons.dbcp.BasicDataSource}} to have its 
{{createConnectionFactory()}} method fixed, to have 
{{Class.forName(driverClassName)}} a real effect. (See [*the fixed 
method*|https://github.com/apache/commons-dbcp/blob/DBCP_1_4_x_BRANCH/src/java/org/apache/commons/dbcp/BasicDataSource.java#L1588-L1660])
* introduce a JDBC driver extending {{com.mysql.jdbc.Driver}} that delegates 
its {{getConnection(String, Properties)}} method to a special wrapper
* let this {{java.sql.Connection}} wrapper do nothing but intercept the 
{{prepareStatement(String, int, int)}} call:
** investigate whether it's a DML statement
** investigate whether it's a statement handling an Oozie table
** if so, try to inject a {{PersistenceException}} w/ a relatively low database 
error percentage (5 %)

h5. Integration testing
* use {{FailingHSQLDBDriverWrapper}} extending {{org.hsqldb.jdbcDriver}} to 
intercept JDBC calls
* use integration test cases extending {{MiniOozieTestCase}} for following 
scenarios:
** parallel call on JPA queries can easily succeed despite of the injected 
errors
** workflows continue to pass w/o injected errors
** workflows pass w/ injected errors

h5. Functional testing
* use {{FailingMySQLDriverWrapper}} extending {{com.mysql.jdbc.Driver}} to 
intercept JDBC calls
* use following coordinator / workflow scenario:
** fired every minute
** executing for multiple days
** workflow consists of a {{}} action followed by two paths of 
consecutive {{}} and {{}} actions

> Oozie should handle transient database problems
> ---
>
> Key: OOZIE-2854
> URL: https://issues.apache.org/jira/browse/OOZIE-2854
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Andras Piros
> Attachments: OOZIE-2854-001.patch, OOZIE-2854-002.patch, 
> OOZIE-2854-003.patch, OOZIE-2854-004.patch, OOZIE-2854-005.patch, 
> OOZIE-2854-POC-001.patch
>
>
> There can be problems when Oozie cannot update the database properly. 
> Recently, we have experienced erratic behavior with two setups:
> * MySQL with the Galera cluster manager. Galera uses cluster-wide optimistic 
> locking which might cause a transaction to rollback if there are two or more 
> parallel transaction running and one of them cannot complete because of a 
> conflict.
> * MySQL with Percona XtraDB Cluster. If one of the MySQL instances is killed, 
> Oozie might get "Communications link failure" exception during the failover.
> The problem is that failed DB transactions later might cause a workflow 
> (which are started/re-started by RecoveryService) to get stuck. It's not 
> clear to us how this happens but it has to do with the fact that certain DB 
> updates are not executed.
> The solution is to use some sort of retry logic with exponential backoff if 
> the DB update fails. We could start with a 100ms wait time which is doubled 
> at every retry. The operation can be considered a failure if it still fails 
> after 10 attempts. These values could be configurable. We should discuss 
> initial values in the scope of this JIRA.
> Note that this solution is to handle *transient* failures. If the DB is down 
> for a longer period of time, we have to accept that the internal state of 
> Oozie is corrupted.



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

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

[Apache Jenkins Server]

See 


Changes:

[gezapeti] OOZIE-2794 Hive and Pig tests failing when multiple pre-commit jobs 
are

--
[...truncated 355.18 KB...]
[INFO] Copying htrace-core-3.0.4.jar to 

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

[INFO] Copying jets3t-0.9.0.jar to 

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

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

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

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

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

[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

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

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

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

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

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

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

[INFO] Copying velocity-1.5.jar to 

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

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

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

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

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

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

[INFO] Copying antlr-2.7.7.jar to 

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

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

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

[jira] [Commented] (OOZIE-2004) Improve Oozie version info output

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2004:
--

Testing JIRA OOZIE-2004

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1968
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  testServerBuildVersion(org.apache.oozie.client.TestWorkflowClient)

.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/oozie-trunk-precommit-build/3928/

> Improve Oozie version info output
> -
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
>Reporter: Chunjun Xiao
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-2004-0.patch, OOZIE-2004-1.patch
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of  Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r 
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul  6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}



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

[jira] [Updated] (OOZIE-2004) Improve Oozie version info output

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2004:

Attachment: HBASE-2004-2.patch

missed one test, re-uploading a patch with fix. Looks like we're testing for 
client and server version in 3 different classes. Is that even necessary?

> Improve Oozie version info output
> -
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
>Reporter: Chunjun Xiao
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: HBASE-2004-2.patch, OOZIE-2004-0.patch, 
> OOZIE-2004-1.patch
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of  Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r 
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul  6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}



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

[jira] [Commented] (OOZIE-2004) Improve Oozie version info output

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2004:
--

Testing JIRA OOZIE-2004

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 1 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1968
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

.Tests failing with errors:
.  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

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


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

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

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

. https://builds.apache.org/job/oozie-trunk-precommit-build/3929/

> Improve Oozie version info output
> -
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
>Reporter: Chunjun Xiao
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: HBASE-2004-2.patch, OOZIE-2004-0.patch, 
> OOZIE-2004-1.patch
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of  Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r 
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul  6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}



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

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

[Apache Jenkins Server]

See 


--
[...truncated 357.54 KB...]
[INFO] Copying htrace-core-3.0.4.jar to 

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

[INFO] Copying jets3t-0.9.0.jar to 

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

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

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

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

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

[INFO] Copying ant-1.9.1.jar to 

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

[INFO] Copying janino-2.7.6.jar to 

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

[INFO] Copying guice-3.0.jar to 

[INFO] Copying httpclient-4.3.6.jar to 

[INFO] Copying xz-1.0.jar to 

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

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

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

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

[INFO] Copying velocity-1.5.jar to 

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

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

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

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

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

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

[INFO] Copying antlr-2.7.7.jar to 

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

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

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

[INFO] Copying jta-1.1.jar to 

[jira] [Commented] (OOZIE-2884) consolidate hadoop versions in pomfiles

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2884:
---

+1
committed to master!
Thanks for the contribution!

> consolidate hadoop versions in pomfiles
> ---
>
> Key: OOZIE-2884
> URL: https://issues.apache.org/jira/browse/OOZIE-2884
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
> Fix For: 5.0.0
>
> Attachments: OOZIE-2884-0.patch, OOZIE-2884-1.patch, 
> OOZIE-2884-2.patch
>
>
> There are some hadoop versions from the old days which can be set separately.
> -Dhadoop.auth.version= - defaults to hadoop version
> -Ddistcp.version= - defaults to hadoop version
> They could be consolidated down to hadoop.version



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

[jira] [Commented] (OOZIE-2956) Fix Findbugs warnings related to reliance on default encoding in oozie-core

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2956:
---

Can you check on the test failures?


> Fix Findbugs warnings related to reliance on default encoding in oozie-core
> ---
>
> Key: OOZIE-2956
> URL: https://issues.apache.org/jira/browse/OOZIE-2956
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, core
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
> Attachments: OOZIE-2956-1.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-core* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.StringBlob.getRawBlob(): String.getBytes() 
> [org.apache.oozie.StringBlob] At StringBlob.java:[line 119]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ActionExecutor.registerError(String, 
> ActionExecutorException$ErrorType, String): 
> java.io.ByteArrayOutputStream.toString() 
> [org.apache.oozie.action.ActionExecutor] At ActionExecutor.java:[line 354]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ActionExecutor.registerError(String, 
> ActionExecutorException$ErrorType, String): new 
> java.io.PrintStream(OutputStream) [org.apache.oozie.action.ActionExecutor] At 
> ActionExecutor.java:[line 353]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper.getRecoveryId(Configuration, 
> Path, String): new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.hadoop.LauncherHelper] At LauncherHelper.java:[line 
> 69]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper.getTag(String): 
> String.getBytes() [org.apache.oozie.action.hadoop.LauncherHelper] At 
> LauncherHelper.java:[line 160]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper$1.run(): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1] At LauncherHelper.java:[line 
> 271]Another occurrence at LauncherHelper.java:[line 277]Another occurrence at 
> LauncherHelper.java:[line 285]Another occurrence at LauncherHelper.java:[line 
> 293]Another occurrence at LauncherHelper.java:[line 299]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.MapReduceActionExecutor.end(ActionExecutor$Context,
>  WorkflowAction): String.getBytes() 
> [org.apache.oozie.action.hadoop.MapReduceActionExecutor] At 
> MapReduceActionExecutor.java:[line 250]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.SqoopActionExecutor.end(ActionExecutor$Context,
>  WorkflowAction): String.getBytes() 
> [org.apache.oozie.action.hadoop.SqoopActionExecutor] At 
> SqoopActionExecutor.java:[line 186]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ssh.SshActionExecutor.drainBuffers(Process, 
> StringBuffer, StringBuffer, int): new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.ssh.SshActionExecutor, 
> org.apache.oozie.action.ssh.SshActionExecutor] At 
> SshActionExecutor.java:[line 684]Another occurrence at 
> SshActionExecutor.java:[line 685]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ssh.SshActionExecutor.initSshScripts(): new 
> java.io.FileWriter(String) [org.apache.oozie.action.ssh.SshActionExecutor, 
> org.apache.oozie.action.ssh.SshActionExecutor] At 
> SshActionExecutor.java:[line 502]Another occurrence at 
> SshActionExecutor.java:[line 504]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.bundle.BundleSubmitXCommand.readDefinition(String): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.command.bundle.BundleSubmitXCommand] At 
> BundleSubmitXCommand.java:[line 322]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.coord.CoordSubmitXCommand.readDefinition(String): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.command.coord.CoordSubmitXCommand] At 
> CoordSubmitXCommand.java:[line 1193]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.coord.CoordUpdateXCommand.getDiffinGitFormat(String, 
> String): java.io.ByteArrayOutputStream.toString() 
> [org.apache.oozie.command.coord.CoordUpdateXCommand] At 
> CoordUpdateXCommand.java:[line 203]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.coord.CoordUpdateXCo

[jira] [Commented] (OOZIE-2004) Improve Oozie version info output

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2004:
-

failing test is unrelated

> Improve Oozie version info output
> -
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
>Reporter: Chunjun Xiao
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: HBASE-2004-2.patch, OOZIE-2004-0.patch, 
> OOZIE-2004-1.patch
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of  Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r 
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul  6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}



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

[jira] [Created] (OOZIE-2972) Server goes inconsistent when prepare war called with secure without SSL

[Prabhu Joseph (JIRA)]

Prabhu Joseph created OOZIE-2972:


 Summary: Server goes inconsistent when prepare war called with 
secure without SSL
 Key: OOZIE-2972
 URL: https://issues.apache.org/jira/browse/OOZIE-2972
 Project: Oozie
  Issue Type: Bug
  Components: security
Affects Versions: 4.3.0
Reporter: Prabhu Joseph


When prepare-war with secure is called by some user by mistake on a Oozie 
Server which is not configured with SSL causes inconsistent state. Oozie Server 
runs fine but the oozie clients are failed with Authentication failure status 
302. Checking curl verbose, Oozie Server redirects client to https port even 
though it is not listening. We need to validate the prepare-war command when 
SSL is not configured instead of going to inconsistent state.

Repro:
{code}
Oozie Server without SSL

/usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war -secure

 curl -ikv -L --negotiate -u: 
http://prabhuzeppelin2.openstacklocal:11000/oozie/v1/admin/status
* About to connect() to prabhuzeppelin2.openstacklocal port 11000 (#0)
*   Trying 172.26.93.73... connected
* Connected to prabhuzeppelin2.openstacklocal (172.26.93.73) port 11000 (#0)
> GET /oozie/v1/admin/status HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 
> zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: prabhuzeppelin2.openstacklocal:11000
> Accept: */*
> 
< HTTP/1.1 302 Found
HTTP/1.1 302 Found
< Server: Apache-Coyote/1.1
Server: Apache-Coyote/1.1
< Pragma: No-cache
Pragma: No-cache
< Cache-Control: no-cache
Cache-Control: no-cache
< Expires: Thu, 01 Jan 1970 00:00:00 UTC
Expires: Thu, 01 Jan 1970 00:00:00 UTC
< Location: https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status
Location: https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status
< Content-Length: 0
Content-Length: 0
< Date: Tue, 27 Jun 2017 11:05:45 GMT
Date: Tue, 27 Jun 2017 11:05:45 GMT

< 
* Connection #0 to host prabhuzeppelin2.openstacklocal left intact
* Issue another request to this URL: 
'https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status'
* About to connect() to prabhuzeppelin2.openstacklocal port 11443 (#1)
*   Trying 172.26.93.73... Connection refused
* couldn't connect to host
* Closing connection #1
curl: (7) couldn't connect to host
* Closing connection #0

{code}



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

[jira] [Updated] (OOZIE-2972) Server goes inconsistent when prepare war called with secure without SSL

[Prabhu Joseph (JIRA)]

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

Prabhu Joseph updated OOZIE-2972:
-
Description: 
When prepare-war with secure is called by some user by mistake on a Oozie 
Server which is not configured with SSL causes inconsistent state. Oozie Server 
runs fine but the oozie clients are failed with Authentication failure status 
302. Checking curl verbose, Oozie Server redirects client to https port even 
though it is not listening. We need to validate the prepare-war command when 
SSL is not configured instead of going to inconsistent state.

Repro:
{code}
Oozie Server without SSL

/usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war -secure

Start Oozie Server

 curl -ikv -L --negotiate -u: 
http://prabhuzeppelin2.openstacklocal:11000/oozie/v1/admin/status
* About to connect() to prabhuzeppelin2.openstacklocal port 11000 (#0)
*   Trying 172.26.93.73... connected
* Connected to prabhuzeppelin2.openstacklocal (172.26.93.73) port 11000 (#0)
> GET /oozie/v1/admin/status HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 
> zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: prabhuzeppelin2.openstacklocal:11000
> Accept: */*
> 
< HTTP/1.1 302 Found
HTTP/1.1 302 Found
< Server: Apache-Coyote/1.1
Server: Apache-Coyote/1.1
< Pragma: No-cache
Pragma: No-cache
< Cache-Control: no-cache
Cache-Control: no-cache
< Expires: Thu, 01 Jan 1970 00:00:00 UTC
Expires: Thu, 01 Jan 1970 00:00:00 UTC
< Location: https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status
Location: https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status
< Content-Length: 0
Content-Length: 0
< Date: Tue, 27 Jun 2017 11:05:45 GMT
Date: Tue, 27 Jun 2017 11:05:45 GMT

< 
* Connection #0 to host prabhuzeppelin2.openstacklocal left intact
* Issue another request to this URL: 
'https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status'
* About to connect() to prabhuzeppelin2.openstacklocal port 11443 (#1)
*   Trying 172.26.93.73... Connection refused
* couldn't connect to host
* Closing connection #1
curl: (7) couldn't connect to host
* Closing connection #0

{code}

  was:
When prepare-war with secure is called by some user by mistake on a Oozie 
Server which is not configured with SSL causes inconsistent state. Oozie Server 
runs fine but the oozie clients are failed with Authentication failure status 
302. Checking curl verbose, Oozie Server redirects client to https port even 
though it is not listening. We need to validate the prepare-war command when 
SSL is not configured instead of going to inconsistent state.

Repro:
{code}
Oozie Server without SSL

/usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war -secure

 curl -ikv -L --negotiate -u: 
http://prabhuzeppelin2.openstacklocal:11000/oozie/v1/admin/status
* About to connect() to prabhuzeppelin2.openstacklocal port 11000 (#0)
*   Trying 172.26.93.73... connected
* Connected to prabhuzeppelin2.openstacklocal (172.26.93.73) port 11000 (#0)
> GET /oozie/v1/admin/status HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 
> zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: prabhuzeppelin2.openstacklocal:11000
> Accept: */*
> 
< HTTP/1.1 302 Found
HTTP/1.1 302 Found
< Server: Apache-Coyote/1.1
Server: Apache-Coyote/1.1
< Pragma: No-cache
Pragma: No-cache
< Cache-Control: no-cache
Cache-Control: no-cache
< Expires: Thu, 01 Jan 1970 00:00:00 UTC
Expires: Thu, 01 Jan 1970 00:00:00 UTC
< Location: https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status
Location: https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status
< Content-Length: 0
Content-Length: 0
< Date: Tue, 27 Jun 2017 11:05:45 GMT
Date: Tue, 27 Jun 2017 11:05:45 GMT

< 
* Connection #0 to host prabhuzeppelin2.openstacklocal left intact
* Issue another request to this URL: 
'https://prabhuzeppelin2.openstacklocal:11443/oozie/v1/admin/status'
* About to connect() to prabhuzeppelin2.openstacklocal port 11443 (#1)
*   Trying 172.26.93.73... Connection refused
* couldn't connect to host
* Closing connection #1
curl: (7) couldn't connect to host
* Closing connection #0

{code}


> Server goes inconsistent when prepare war called with secure without SSL
> 
>
> Key: OOZIE-2972
> URL: https://issues.apache.org/jira/browse/OOZIE-2972
> Project: Oozie
>  Issue Type: Bug
>  Components: security
>Affects Versions: 4.3.0
>Reporter: Prabhu Joseph
>
> When prepare-war with secure is called by some user by mistake on a Oozie 
> Server which is not configured with SSL causes inconsistent state. Oozie 
> Server runs fine but the oozie clients are failed with Authentication failure 
> status 302. Checking curl verbose, Oozie Server redirects client to https 
> port even though i

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (106 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2964  getting at 
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:5163)
https://issues.apache.org/jira/browse/OOZIE-2964
OOZIE-2963  getting error in build ArtifactNotFoundException: Could not find 
artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
https://issues.apache.org/jira/browse/OOZIE-2963
OOZIE-2962  bump maven-javadoc-plugin to 2.10.4
https://issues.apache.org/jira/browse/OOZIE-2962
OOZIE-2961  build contains multiple warnings for is not a parameter name
https://issues.apache.org/jira/browse/OOZIE-2961
OOZIE-2960  many warnings for @return tag has no arguments
https://issues.apache.org/jira/browse/OOZIE-2960
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2931  multiple warnings during build for "no @param for"
https://issues.apache.org/jira/browse/OOZIE-2931
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2918  Delete LauncherMapper and its test
https://issues.apache.org/jira/browse/OOZIE-2918
OOZIE-2916  Set a job name for the MR Action's child job
https://issues.apache.org/jira/browse/OOZIE-2916
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2911  Re-add test testWfActionKillChildJob and adapt it to OYA
https://issues.apache.org/jira/browse/OOZIE-2911
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2854  Oozie should handle transient database problems
https://issues.apache.org/jira/browse/OOZIE-2854
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues.apache.org/jira/browse/OOZIE-2826
OOZIE-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-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.