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

[Apache Jenkins Server]

See 


--
[...truncated 1.59 MB...]
[INFO] Copying junit-4.11.jar to 

[INFO] Copying metrics-graphite-3.1.2.jar to 

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

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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2960:
--

Testing JIRA OOZIE-2960

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

> 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, 
> OOZIE-2960-2.patch, OOZIE-2960-3.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)

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

[Apache Jenkins Server]

See 


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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

[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 

[INFO] Building 

[jira] [Commented] (OOZIE-3021) Error on job or SLA event listening: WARN logs instead of DEBUG

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3021:
--

Testing JIRA OOZIE-3021

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 78 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {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/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [core].
{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: 2010
.Tests rerun: 43
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,
{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/4011/

> Error on job or SLA event listening: WARN logs instead of DEBUG
> ---
>
> Key: OOZIE-3021
> URL: https://issues.apache.org/jira/browse/OOZIE-3021
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3021.001.patch
>
>
> When handling a job or SLA event inside {{EventHandlingService}}, when a 
> {{Throwable}} happens when 
> [*{{EventWorker.run()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/EventHandlerService.java#L255-L265]
>  is called, only {{DEBUG}} level logs are printed.
> Since in general most users don't set Oozie log level to {{DEBUG}} while in 
> production, we should employ {{WARN}} level to get an idea when e.g. an SLA 
> event processing didn't succeed.



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

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

[Apache Jenkins Server]

See 

[jira] [Updated] (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:all-tabpanel
 ]

Artem Ervits updated OOZIE-2960:

Attachment: OOZIE-2960-3.patch

> 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, 
> OOZIE-2960-2.patch, OOZIE-2960-3.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)

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

[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 9b6f0c91eca1ef73332b82bec9198c2723c8c598 
(refs/remotes/origin/master)
Commit message: "OOZIE-3019 Remove getPasswordMethod in ConfigurationService 
(gezapeti)"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 9b6f0c91eca1ef73332b82bec9198c2723c8c598
 > git rev-list 9b6f0c91eca1ef73332b82bec9198c2723c8c598 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/jenkins7712754046426276252.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 --:--:-- --:--:-- --:--:-- 0100 
 167k0  167k0 0   125k  0 --:--:--  0:00:01 --:--:--  125k100  
495k0  495k0 0   213k  0 --:--:--  0:00:02 --:--:--  212k100  
751k0  751k0 0   225k  0 --:--:--  0:00:03 --:--:--  225k100 
1335k0 1335k0 0   294k  0 --:--:--  0:00:04 --:--:--  294k100 
1575k0 1575k0 0   295k  0 --:--:--  0:00:05 --:--:--  335k100 
1927k0 1927k0 0   304k  0 --:--:--  0:00:06 --:--:--  352k100 
2287k0 2287k0 0   312k  0 --:--:--  0:00:07 --:--:--  358k100 
2607k0 2607k0 0   311k  0 --:--:--  0:00:08 --:--:--  368k100 
2727k0 2727k0 0   280k  0 --:--:--  0:00:09 --:--:--  268k100 
2727k0 2727k0 0   254k  0 --:--:--  0:00:10 --:--:--  214k100 
2727k0 2727k0 0   232k  0 --:--:--  0:00:11 --:--:--  148k100 
2727k0 2727k0 0   230k  0 --:--:--  0:00:11 --:--:--   97k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Updated] (OOZIE-3021) Error on job or SLA event listening: WARN logs instead of DEBUG

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3021:

Attachment: (was: OOZIE-3021.001.patch)

> Error on job or SLA event listening: WARN logs instead of DEBUG
> ---
>
> Key: OOZIE-3021
> URL: https://issues.apache.org/jira/browse/OOZIE-3021
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3021.001.patch
>
>
> When handling a job or SLA event inside {{EventHandlingService}}, when a 
> {{Throwable}} happens when 
> [*{{EventWorker.run()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/EventHandlerService.java#L255-L265]
>  is called, only {{DEBUG}} level logs are printed.
> Since in general most users don't set Oozie log level to {{DEBUG}} while in 
> production, we should employ {{WARN}} level to get an idea when e.g. an SLA 
> event processing didn't succeed.



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

[jira] [Updated] (OOZIE-3021) Error on job or SLA event listening: WARN logs instead of DEBUG

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3021:

Attachment: OOZIE-3021.001.patch

> Error on job or SLA event listening: WARN logs instead of DEBUG
> ---
>
> Key: OOZIE-3021
> URL: https://issues.apache.org/jira/browse/OOZIE-3021
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3021.001.patch
>
>
> When handling a job or SLA event inside {{EventHandlingService}}, when a 
> {{Throwable}} happens when 
> [*{{EventWorker.run()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/EventHandlerService.java#L255-L265]
>  is called, only {{DEBUG}} level logs are printed.
> Since in general most users don't set Oozie log level to {{DEBUG}} while in 
> production, we should employ {{WARN}} level to get an idea when e.g. an SLA 
> event processing didn't succeed.



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

[jira] [Updated] (OOZIE-3021) Error on job or SLA event listening: WARN logs instead of DEBUG

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3021:

Attachment: OOZIE-3021.001.patch

> Error on job or SLA event listening: WARN logs instead of DEBUG
> ---
>
> Key: OOZIE-3021
> URL: https://issues.apache.org/jira/browse/OOZIE-3021
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3021.001.patch
>
>
> When handling a job or SLA event inside {{EventHandlingService}}, when a 
> {{Throwable}} happens when 
> [*{{EventWorker.run()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/EventHandlerService.java#L255-L265]
>  is called, only {{DEBUG}} level logs are printed.
> Since in general most users don't set Oozie log level to {{DEBUG}} while in 
> production, we should employ {{WARN}} level to get an idea when e.g. an SLA 
> event processing didn't succeed.



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

[jira] [Created] (OOZIE-3021) Error on job or SLA event listening: WARN logs instead of DEBUG

[Andras Piros (JIRA)]

Andras Piros created OOZIE-3021:
---

 Summary: Error on job or SLA event listening: WARN logs instead of 
DEBUG
 Key: OOZIE-3021
 URL: https://issues.apache.org/jira/browse/OOZIE-3021
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.0
Reporter: Andras Piros
Assignee: Andras Piros
 Fix For: 5.0.0


When handling a job or SLA event inside {{EventHandlingService}}, when a 
{{Throwable}} happens when 
[*{{EventWorker.run()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/EventHandlerService.java#L255-L265]
 is called, only {{DEBUG}} level logs are printed.

Since in general most users don't set Oozie log level to {{DEBUG}} while in 
production, we should employ {{WARN}} level to get an idea when e.g. an SLA 
event processing didn't succeed.



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

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

[Apache Jenkins Server]

See 


Changes:

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

[gezapeti] OOZIE-3018 Use Hadoop's CredentialProvider for passwords in

[gezapeti] OOZIE-2961 Build contains multiple warnings for is not a parameter 
name

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

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

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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

[jira] [Commented] (OOZIE-2670) Upgrade Hbase to 1.2

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2670:
--

Testing JIRA OOZIE-2670

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


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

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

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

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

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch, OOZIE-2670.004.patch, OOZIE-2670.005.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2960:
--

Testing JIRA OOZIE-2960

Cleaning local git workspace



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



> 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, 
> OOZIE-2960-2.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)

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

[Apache Jenkins Server]

See 


Changes:

[asasvari] OOZIE-3009 Number of Oozie tests executed dropped after OOZIE-2854

[gezapeti] OOZIE-3019 Remove getPasswordMethod in ConfigurationService 
(gezapeti)

--
[...truncated 687.98 KB...]
public List getJobIdsForThisServer(List ids) {

error: patch failed: 
core/src/main/java/org/apache/oozie/service/ZKJobsConcurrencyService.java:134
error: 
core/src/main/java/org/apache/oozie/service/ZKJobsConcurrencyService.java: 
patch does not apply
Checking patch 
core/src/main/java/org/apache/oozie/servlet/BaseJobServlet.java...
error: while searching for:
 *
 * @param request
 * @param response
 * @return JSONObject
 * @throws XServletException
 * @throws IOException TODO
 */

error: patch failed: 
core/src/main/java/org/apache/oozie/servlet/BaseJobServlet.java:420
error: core/src/main/java/org/apache/oozie/servlet/BaseJobServlet.java: patch 
does not apply
Checking patch core/src/main/java/org/apache/oozie/servlet/V0JobsServlet.java...
error: while searching for:
 * service implementation to bulk kill jobs
 * @param request
 * @param response
 * @throws XServletException
 * @throws IOException
 */

error: patch failed: 
core/src/main/java/org/apache/oozie/servlet/V0JobsServlet.java:121
error: core/src/main/java/org/apache/oozie/servlet/V0JobsServlet.java: patch 
does not apply
Checking patch core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java...
error: while searching for:
 * service implementation to bulk kill jobs
 * @param request
 * @param response
 * @return bulkModifyJobs implementation to bulk kill jobs
 * @throws XServletException
 * @throws IOException
 */

error: patch failed: 
core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java:434
error: core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java: patch 
does not apply
Checking patch core/src/main/java/org/apache/oozie/sla/SLACalculator.java...
error: while searching for:
 * Enable jobs sla alert.
 *
 * @param jobId the job ids
 * @return true if successful
 * @throws JPAExecutorException the JPA executor exception
 * @throws ServiceException the service exception
 */

error: patch failed: 
core/src/main/java/org/apache/oozie/sla/SLACalculator.java:58
error: core/src/main/java/org/apache/oozie/sla/SLACalculator.java: patch does 
not apply
Checking patch 
core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java...
error: while searching for:
 * Get SLACalcStatus from map if SLARegistration is not null, else create a 
new SLACalcStatus
 * This function deosn't update  slaMap
 * @param jobId
 * @return SLACalcStatus returns SLACalcStatus from map if SLARegistration 
is not null,
 * else create a new SLACalcStatus
 * @throws JPAExecutorException
 */
private SLACalcStatus getOrCreateSLACalcStatus(String jobId) throws 
JPAExecutorException {

error: patch failed: 
core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java:174
error: core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java: patch 
does not apply
Checking patch core/src/main/java/org/apache/oozie/store/OozieSchema.java...
error: while searching for:
 * Gets the query that will be used to validate the connection
 *
 * @param dbName
 * @return String returns the query that will be used to validate the 
connection
 */
public static String getValidationQuery(String dbName) {
return "select count(" + OozieColumn.VER_versionNumber.columnName() + 
") from " + dbName + "."

error: patch failed: 
core/src/main/java/org/apache/oozie/store/OozieSchema.java:209
error: core/src/main/java/org/apache/oozie/store/OozieSchema.java: patch does 
not apply
Checking patch 
core/src/main/java/org/apache/oozie/util/JaasConfiguration.java...
error: while searching for:
 * 
 * 
javax.security.auth.login.Configuration.setConfiguration(JaasConfiguration.getInstance());
 *
 * @return me return the singleton
 */
public static Configuration getInstance() {
if (me == null) {

error: patch failed: 
core/src/main/java/org/apache/oozie/util/JaasConfiguration.java:56
error: core/src/main/java/org/apache/oozie/util/JaasConfiguration.java: patch 
does not apply
Checking patch core/src/main/java/org/apache/oozie/util/MappingRule.java...
error: while searching for:

/**
 * Gets the from rule
 * @return fromString Gets the from rule
 */
public String getFromRule() {
return fromString;

error: patch failed: 
core/src/main/java/org/apache/oozie/util/MappingRule.java:53
error: core/src/main/java/org/apache/oozie/util/MappingRule.java: patch does 
not apply
Checking patch core/src/main/java/org/apache/oozie/util/StatusUtils.java...
error: while searching for:
 * Get the status of coordinator job for 

[jira] [Commented] (OOZIE-2608) Comma in oozie.service.JPAService.jdbc.password value results in authentication error

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2608:
---

On second thought, that might not be necessary as it would basically re-test 
{{MessageFormat}}.
So +1

> Comma in oozie.service.JPAService.jdbc.password value results in 
> authentication error
> -
>
> Key: OOZIE-2608
> URL: https://issues.apache.org/jira/browse/OOZIE-2608
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
> Environment: HDP 2.4 latest, Oozie 4.2.0.2.4.2.0-258
>Reporter: Nikolai Grigoriev
>Assignee: Peter Cseh
>Priority: Minor
> Attachments: OOZIE-2608-001.patch
>
>
> I have attempted to install Oozie with Postgres db backend via HDP 2.4. I was 
> able to test DB connection via Ambari, everything was correct. However, the 
> server failed to start with this error:
> {code}
> 2016-07-15 11:46:39,580  INFO URIHandlerService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] Loaded default urihandler 
> org.apache.oozie.dependency.FSURIHandler
> 2016-07-15 11:46:40,323  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] password key is 
> oozie.service.JPAService.jdbc.password
> 2016-07-15 11:46:40,331  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] credential provider path 
> is null
> 2016-07-15 11:46:40,337  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] password is null
> 2016-07-15 11:46:41,176 FATAL Services:514 - 
> SERVER[hadoop-master01.production.sociablelabs.net] Runtime Exception during 
> Services Load. Check your list of 'oozie.services' or 'o
> ozie.services.ext'
> 2016-07-15 11:46:41,194 FATAL Services:514 - 
> SERVER[hadoop-master01.production.sociablelabs.net] E0103: Could not load 
> service classes, Cannot create PoolableConnectionFactory (F
> ATAL: password authentication failed for user "oozie")
> org.apache.oozie.service.ServiceException: E0103: Could not load service 
> classes, Cannot create PoolableConnectionFactory (FATAL: password 
> authentication failed for user "oozie")
> at org.apache.oozie.service.Services.loadServices(Services.java:309)
> at org.apache.oozie.service.Services.init(Services.java:213)
> 
> Caused by: org.postgresql.util.PSQLException: FATAL: password authentication 
> failed for user "oozie"
> at 
> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
> at 
> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
> at 
> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
> ...
> {code}
> Schema verification at startup worked fine and I could not find any bugs 
> related to it. So, I started getting suspicious about my password value, 
> which was like "pO,e43DpjK" (not exactly but it was a bunch of letters, 
> number and one comma). I suspected that the comma was probably interpreted as 
> a value list separator so I have changed the password removing the comma. 
> Server started flawlessly.
> I am not 100% sure if it is Ambari that should be escaping (or validating?) 
> the value or Oozie that fails to read the value as single string.



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

[jira] [Updated] (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:all-tabpanel
 ]

Artem Ervits updated OOZIE-2960:

Attachment: OOZIE-2960-2.patch

[~gezapeti] rebased, pending Jenkins

> 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, 
> OOZIE-2960-2.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] [Updated] (OOZIE-3019) Remove getPasswordMethod in ConfigurationService

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-3019:
--
Summary: Remove getPasswordMethod in ConfigurationService  (was: remove 
getPasswordMethod in ConfigurationServiceR)

> Remove getPasswordMethod in ConfigurationService
> 
>
> Key: OOZIE-3019
> URL: https://issues.apache.org/jira/browse/OOZIE-3019
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-3019.001.patch
>
>
> getPasswordMethod in ConfigurationService is there to support Hadoop versions 
>  2.6.0. As the minimum version is 2.6.0, this can be removed now



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

[jira] [Updated] (OOZIE-3019) remove getPasswordMethod in ConfigurationServiceR

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-3019:
--
Summary: remove getPasswordMethod in ConfigurationServiceR  (was: remove 
getPasswordMethod in ConfigurationService)

> remove getPasswordMethod in ConfigurationServiceR
> -
>
> Key: OOZIE-3019
> URL: https://issues.apache.org/jira/browse/OOZIE-3019
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-3019.001.patch
>
>
> getPasswordMethod in ConfigurationService is there to support Hadoop versions 
>  2.6.0. As the minimum version is 2.6.0, this can be removed now



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

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

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-3009:
---

Thanks [~andras.piros]. Committed to master!

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



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

[jira] [Commented] (OOZIE-2670) Upgrade Hbase to 1.2

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2670:
--

Testing JIRA OOZIE-2670

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 78 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1089
.Tests rerun: 22
.Tests failed at first run: org.apache.oozie.action.hadoop.TestLauncherAM,
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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

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

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

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

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch, OOZIE-2670.004.patch, OOZIE-2670.005.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

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

[Apache Jenkins Server]

See 


--
[...truncated 1.55 MB...]
[INFO] Copying commons-beanutils-1.7.0.jar to 

[INFO] Copying junit-4.11.jar to 

[INFO] Copying metrics-graphite-3.1.2.jar to 

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

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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

[jira] [Commented] (OOZIE-3019) remove getPasswordMethod in ConfigurationService

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3019:
--

Testing JIRA OOZIE-3019

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 78 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [core].
. {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 [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {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/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/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 [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:green}+1 TESTS{color}
.Tests run: 342
.Tests rerun: 3
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestHdfsOperations,
{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/4008/

> remove getPasswordMethod in ConfigurationService
> 
>
> Key: OOZIE-3019
> URL: https://issues.apache.org/jira/browse/OOZIE-3019
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-3019.001.patch
>
>
> getPasswordMethod in ConfigurationService is there to support Hadoop versions 
>  2.6.0. As the minimum version is 2.6.0, this can be removed now



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

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

[Apache Jenkins Server]

See 


--
[...truncated 1.52 MB...]
[INFO] Copying commons-beanutils-1.7.0.jar to 

[INFO] Copying junit-4.11.jar to 

[INFO] Copying metrics-graphite-3.1.2.jar to 

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

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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

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

[Apache Jenkins Server]

See 


--
[...truncated 1.54 MB...]
[INFO] Copying commons-beanutils-1.7.0.jar to 

[INFO] Copying junit-4.11.jar to 

[INFO] Copying metrics-graphite-3.1.2.jar to 

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

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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

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

[Apache Jenkins Server]

See 


--
[...truncated 1.59 MB...]
[INFO] Copying commons-beanutils-1.7.0.jar to 

[INFO] Copying junit-4.11.jar to 

[INFO] Copying metrics-graphite-3.1.2.jar to 

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

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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3009:
--

Testing JIRA OOZIE-3009

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:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 8 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
.{color:red}WARNING{color}: the current HEAD has 78 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {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 [tools].
. {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 [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/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {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/hcatalog].
{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: 2010
.Tests rerun: 95
.Tests failed at first run: 
org.apache.oozie.service.TestPartitionDependencyManagerEhcache,org.apache.oozie.service.TestPartitionDependencyManagerService,org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.service.TestStatusTransitService,org.apache.oozie.action.hadoop.TestHdfsOperations,
{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/4006/

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



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

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

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2960:
---

[~dbist13], can you rebase the patch please?

> 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

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2961:
---

+1 Committed to master!

> 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-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-3018:
---

+1

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3018.001.patch
>
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within [*{{SchemaCheckerService.init()}}*| 
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
>  Addressing this issue.



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

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

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2272:
-

[~rkanter] [~h_o] opened OOZIE-3018 to track this one remaining place.

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



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

[jira] [Commented] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3018:
-

[~gezapeti] can you pls. review?

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3018.001.patch
>
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within [*{{SchemaCheckerService.init()}}*| 
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
>  Addressing this issue.



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

[jira] [Created] (OOZIE-3020) Improve Oozie action retry functionality documentation

[Peter Cseh (JIRA)]

Peter Cseh created OOZIE-3020:
-

 Summary: Improve Oozie action retry functionality documentation
 Key: OOZIE-3020
 URL: https://issues.apache.org/jira/browse/OOZIE-3020
 Project: Oozie
  Issue Type: Improvement
Reporter: Peter Cseh


Oozie supports retry functionality and it is mentioned in the following 
documentation: 
https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html#a18_User-Retry_for_Workflow_Actions_since_Oozie_3.1
The current documentation mentions some config values, but does not explain 
them properly:

oozie.service.LiteWorkflowStoreService.user.retry.error.code.ext 
oozie.action.retry.interval
...
Once the above is done, user needs to configure retry in the workflow action.


It would be good to document this in a consolidated manner. What are the 
possible error codes? What is the unit of the retry-interval? etc.



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

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

[Apache Jenkins Server]

See 


Changes:

[gezapeti] OOZIE-2662 DB migration fails if database is too big (andras.piros 
via

--
[...truncated 1.55 MB...]
[INFO] Copying junit-4.11.jar to 

[INFO] Copying metrics-graphite-3.1.2.jar to 

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

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

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

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

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

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

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

[INFO] Copying jettison-1.1.jar to 

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

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

[INFO] Copying jpam-1.1.jar to 

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

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

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

[INFO] Copying json-20090211.jar to 

[INFO] Copying avro-1.7.4.jar to 

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

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

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

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

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

[jira] [Commented] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3018:
--

Testing JIRA OOZIE-3018

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 78 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1601
.Tests rerun: 3
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestHdfsOperations,
{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/4004/

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3018.001.patch
>
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within [*{{SchemaCheckerService.init()}}*| 
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
>  Addressing this issue.



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

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

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2958:
-

Committed to master, thanks everyone.

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

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

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2958:
---

+1, go ahead and commit [~pbacsko]

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

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

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2958:
-

"-1 TESTS - patch does not compile, cannot run testcases"

In fact, the patch is compilable, the test execution just didn't finish because 
of OOZIE-3009.

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

[jira] [Commented] (OOZIE-3019) remove getPasswordMethod in ConfigurationService

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3019:
-

+1

> remove getPasswordMethod in ConfigurationService
> 
>
> Key: OOZIE-3019
> URL: https://issues.apache.org/jira/browse/OOZIE-3019
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-3019.001.patch
>
>
> getPasswordMethod in ConfigurationService is there to support Hadoop versions 
>  2.6.0. As the minimum version is 2.6.0, this can be removed now



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

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

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-3009:
---

+1

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



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

[jira] [Updated] (OOZIE-2670) Upgrade Hbase to 1.2

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2670:
--
Attachment: OOZIE-2670.005.patch

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch, OOZIE-2670.004.patch, OOZIE-2670.005.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

[jira] [Commented] (OOZIE-2670) Upgrade Hbase to 1.2

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2670:
---

[~gezapeti] thanks a lot.

nit in {{HbaseCredentials.java}} :
{{Connection connection =ConnectionFactory.createConnection(jobConf)}}

Please add a space after the *=* sign 

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch, OOZIE-2670.004.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

[jira] [Commented] (OOZIE-2608) Comma in oozie.service.JPAService.jdbc.password value results in authentication error

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2608:
---

Can you add a unit test that covers this?

> Comma in oozie.service.JPAService.jdbc.password value results in 
> authentication error
> -
>
> Key: OOZIE-2608
> URL: https://issues.apache.org/jira/browse/OOZIE-2608
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
> Environment: HDP 2.4 latest, Oozie 4.2.0.2.4.2.0-258
>Reporter: Nikolai Grigoriev
>Assignee: Peter Cseh
>Priority: Minor
> Attachments: OOZIE-2608-001.patch
>
>
> I have attempted to install Oozie with Postgres db backend via HDP 2.4. I was 
> able to test DB connection via Ambari, everything was correct. However, the 
> server failed to start with this error:
> {code}
> 2016-07-15 11:46:39,580  INFO URIHandlerService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] Loaded default urihandler 
> org.apache.oozie.dependency.FSURIHandler
> 2016-07-15 11:46:40,323  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] password key is 
> oozie.service.JPAService.jdbc.password
> 2016-07-15 11:46:40,331  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] credential provider path 
> is null
> 2016-07-15 11:46:40,337  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] password is null
> 2016-07-15 11:46:41,176 FATAL Services:514 - 
> SERVER[hadoop-master01.production.sociablelabs.net] Runtime Exception during 
> Services Load. Check your list of 'oozie.services' or 'o
> ozie.services.ext'
> 2016-07-15 11:46:41,194 FATAL Services:514 - 
> SERVER[hadoop-master01.production.sociablelabs.net] E0103: Could not load 
> service classes, Cannot create PoolableConnectionFactory (F
> ATAL: password authentication failed for user "oozie")
> org.apache.oozie.service.ServiceException: E0103: Could not load service 
> classes, Cannot create PoolableConnectionFactory (FATAL: password 
> authentication failed for user "oozie")
> at org.apache.oozie.service.Services.loadServices(Services.java:309)
> at org.apache.oozie.service.Services.init(Services.java:213)
> 
> Caused by: org.postgresql.util.PSQLException: FATAL: password authentication 
> failed for user "oozie"
> at 
> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
> at 
> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
> at 
> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
> ...
> {code}
> Schema verification at startup worked fine and I could not find any bugs 
> related to it. So, I started getting suspicious about my password value, 
> which was like "pO,e43DpjK" (not exactly but it was a bunch of letters, 
> number and one comma). I suspected that the comma was probably interpreted as 
> a value list separator so I have changed the password removing the comma. 
> Server started flawlessly.
> I am not 100% sure if it is Ambari that should be escaping (or validating?) 
> the value or Oozie that fails to read the value as single string.



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

[jira] [Updated] (OOZIE-2670) Upgrade Hbase to 1.2

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2670:
--
Attachment: OOZIE-2670.004.patch

7 lines shorter :)

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch, OOZIE-2670.004.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

[jira] [Commented] (OOZIE-2670) Upgrade Hbase to 1.2

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2670:
---

In {{HbaseCredentials.java}} you could use try with resources. Otherwise it 
looks good to me.


> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

[jira] [Updated] (OOZIE-3019) remove getPasswordMethod in ConfigurationService

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-3019:
--
Attachment: OOZIE-3019.001.patch

> remove getPasswordMethod in ConfigurationService
> 
>
> Key: OOZIE-3019
> URL: https://issues.apache.org/jira/browse/OOZIE-3019
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-3019.001.patch
>
>
> getPasswordMethod in ConfigurationService is there to support Hadoop versions 
>  2.6.0. As the minimum version is 2.6.0, this can be removed now



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

[jira] [Assigned] (OOZIE-3019) remove getPasswordMethod in ConfigurationService

[Peter Cseh (JIRA)]

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

Peter Cseh reassigned OOZIE-3019:
-

Assignee: Peter Cseh

> remove getPasswordMethod in ConfigurationService
> 
>
> Key: OOZIE-3019
> URL: https://issues.apache.org/jira/browse/OOZIE-3019
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>
> getPasswordMethod in ConfigurationService is there to support Hadoop versions 
>  2.6.0. As the minimum version is 2.6.0, this can be removed now



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

[jira] [Created] (OOZIE-3019) remove getPasswordMethod in ConfigurationService

[Peter Cseh (JIRA)]

Peter Cseh created OOZIE-3019:
-

 Summary: remove getPasswordMethod in ConfigurationService
 Key: OOZIE-3019
 URL: https://issues.apache.org/jira/browse/OOZIE-3019
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh


getPasswordMethod in ConfigurationService is there to support Hadoop versions  
2.6.0. As the minimum version is 2.6.0, this can be removed now



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

Re: Review Request 61142: OOZIE-3009 Number of Oozie tests executed dropped

[Attila Sasvari]

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


Ship it!




Ship It!

- Attila Sasvari


On July 31, 2017, 10:26 a.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61142/
> ---
> 
> (Updated July 31, 2017, 10:26 a.m.)
> 
> 
> Review request for oozie, Attila Sasvari and Peter Cseh.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3009 Number of Oozie tests executed dropped
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/service/JPAService.java 
> 93fe9da1564b734831e7b988ffe760f808af49fa 
>   core/src/main/java/org/apache/oozie/sla/SLARegistrationBean.java 
> 1b8370f01e5097300ee20e903ac745c23c999ce3 
>   
> core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
>  b742ca78520bdea804234460c36925beb105c5cb 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobsDeleteJPAExecutor.java
>  9077970fb11e10f158b1b742e6abbf4d056f92a8 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordActionsDeleteJPAExecutor.java
>  c7e0c38426d08c824b373409a9860a420e158821 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobsDeleteJPAExecutor.java
>  bff5836f209e1ec43de1b32203689909591896b7 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestWorkflowJobsDeleteJPAExecutor.java
>  c4ca61bf0ce678ae6bd0f6309a586f287e05537c 
>   core/src/test/java/org/apache/oozie/service/TestConfigurationService.java 
> 4cb2530cae634517ab833676b68deba068c7560b 
>   core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java 
> 34011f6b6f7f7ee4c57d63a1e62af4acb0fe32ba 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 
> 0ef4a4be6998744914e2ab56697cc2ae517070b9 
>   
> core/src/test/java/org/apache/oozie/util/db/TestPersistenceExceptionSubclassFilterRetryPredicate.java
>  76d2edc0e538732e65556d9255f49d4d1c0980b7 
> 
> 
> Diff: https://reviews.apache.org/r/61142/diff/2/
> 
> 
> Testing
> ---
> 
> Following test cases have been executed:
> ```
> TestOperationRetryHandler
> TestPersistenceExceptionSubclassFilterRetryPredicate
> TestParallelJPAOperationRetries
> TestWorkflow
> TestWorkflowRetries
> TestJPAService
> TestRetryAttemptState
> TestSLACalculatorMemory
> TestWorkflowJobsDeleteJPAExecutor
> TestPurgeService
> TestCoordJobsDeleteJPAExecutor
> TestBundleJobsDeleteJPAExecutor
> TestPurgeXCommand
> ```
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Commented] (OOZIE-2670) Upgrade Hbase to 1.2

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2670:
-

+1

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

[jira] [Updated] (OOZIE-2670) Upgrade Hbase to 1.2

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2670:
--
Attachment: OOZIE-2670.003.patch

rebasing patch 2. [~pbacsko], [~asasvari] please review

> Upgrade Hbase to 1.2
> 
>
> Key: OOZIE-2670
> URL: https://issues.apache.org/jira/browse/OOZIE-2670
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2670.001.patch, OOZIE-2670.002.patch, 
> OOZIE-2670.003.patch
>
>
> We should upgrade Hbase to a newer version, say 1.2



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

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

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3009:

Attachment: OOZIE-3009.002.patch

Addressing review comments.

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



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

Re: Review Request 61142: OOZIE-3009 Number of Oozie tests executed dropped

[András Piros]

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

(Updated July 31, 2017, 10:26 a.m.)


Review request for oozie, Attila Sasvari and Peter Cseh.


Changes
---

Addressing review comments.


Repository: oozie-git


Description
---

OOZIE-3009 Number of Oozie tests executed dropped


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/service/JPAService.java 
93fe9da1564b734831e7b988ffe760f808af49fa 
  core/src/main/java/org/apache/oozie/sla/SLARegistrationBean.java 
1b8370f01e5097300ee20e903ac745c23c999ce3 
  
core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
 b742ca78520bdea804234460c36925beb105c5cb 
  
core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobsDeleteJPAExecutor.java
 9077970fb11e10f158b1b742e6abbf4d056f92a8 
  
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordActionsDeleteJPAExecutor.java
 c7e0c38426d08c824b373409a9860a420e158821 
  
core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobsDeleteJPAExecutor.java
 bff5836f209e1ec43de1b32203689909591896b7 
  
core/src/test/java/org/apache/oozie/executor/jpa/TestWorkflowJobsDeleteJPAExecutor.java
 c4ca61bf0ce678ae6bd0f6309a586f287e05537c 
  core/src/test/java/org/apache/oozie/service/TestConfigurationService.java 
4cb2530cae634517ab833676b68deba068c7560b 
  core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java 
34011f6b6f7f7ee4c57d63a1e62af4acb0fe32ba 
  core/src/test/java/org/apache/oozie/test/XTestCase.java 
0ef4a4be6998744914e2ab56697cc2ae517070b9 
  
core/src/test/java/org/apache/oozie/util/db/TestPersistenceExceptionSubclassFilterRetryPredicate.java
 76d2edc0e538732e65556d9255f49d4d1c0980b7 


Diff: https://reviews.apache.org/r/61142/diff/2/

Changes: https://reviews.apache.org/r/61142/diff/1-2/


Testing
---

Following test cases have been executed:
```
TestOperationRetryHandler
TestPersistenceExceptionSubclassFilterRetryPredicate
TestParallelJPAOperationRetries
TestWorkflow
TestWorkflowRetries
TestJPAService
TestRetryAttemptState
TestSLACalculatorMemory
TestWorkflowJobsDeleteJPAExecutor
TestPurgeService
TestCoordJobsDeleteJPAExecutor
TestBundleJobsDeleteJPAExecutor
TestPurgeXCommand
```


Thanks,

András Piros

[jira] [Commented] (OOZIE-2608) Comma in oozie.service.JPAService.jdbc.password value results in authentication error

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2608:
---

[~asasvari], please review

> Comma in oozie.service.JPAService.jdbc.password value results in 
> authentication error
> -
>
> Key: OOZIE-2608
> URL: https://issues.apache.org/jira/browse/OOZIE-2608
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
> Environment: HDP 2.4 latest, Oozie 4.2.0.2.4.2.0-258
>Reporter: Nikolai Grigoriev
>Assignee: Peter Cseh
>Priority: Minor
> Attachments: OOZIE-2608-001.patch
>
>
> I have attempted to install Oozie with Postgres db backend via HDP 2.4. I was 
> able to test DB connection via Ambari, everything was correct. However, the 
> server failed to start with this error:
> {code}
> 2016-07-15 11:46:39,580  INFO URIHandlerService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] Loaded default urihandler 
> org.apache.oozie.dependency.FSURIHandler
> 2016-07-15 11:46:40,323  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] password key is 
> oozie.service.JPAService.jdbc.password
> 2016-07-15 11:46:40,331  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] credential provider path 
> is null
> 2016-07-15 11:46:40,337  INFO HadoopAccessorService:520 - 
> SERVER[hadoop-master01.production.sociablelabs.net] password is null
> 2016-07-15 11:46:41,176 FATAL Services:514 - 
> SERVER[hadoop-master01.production.sociablelabs.net] Runtime Exception during 
> Services Load. Check your list of 'oozie.services' or 'o
> ozie.services.ext'
> 2016-07-15 11:46:41,194 FATAL Services:514 - 
> SERVER[hadoop-master01.production.sociablelabs.net] E0103: Could not load 
> service classes, Cannot create PoolableConnectionFactory (F
> ATAL: password authentication failed for user "oozie")
> org.apache.oozie.service.ServiceException: E0103: Could not load service 
> classes, Cannot create PoolableConnectionFactory (FATAL: password 
> authentication failed for user "oozie")
> at org.apache.oozie.service.Services.loadServices(Services.java:309)
> at org.apache.oozie.service.Services.init(Services.java:213)
> 
> Caused by: org.postgresql.util.PSQLException: FATAL: password authentication 
> failed for user "oozie"
> at 
> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
> at 
> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
> at 
> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
> ...
> {code}
> Schema verification at startup worked fine and I could not find any bugs 
> related to it. So, I started getting suspicious about my password value, 
> which was like "pO,e43DpjK" (not exactly but it was a bunch of letters, 
> number and one comma). I suspected that the comma was probably interpreted as 
> a value list separator so I have changed the password removing the comma. 
> Server started flawlessly.
> I am not 100% sure if it is Ambari that should be escaping (or validating?) 
> the value or Oozie that fails to read the value as single string.



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

Re: Review Request 61142: OOZIE-3009 Number of Oozie tests executed dropped

[András Piros]

> On July 31, 2017, 9:58 a.m., Peter Bacsko wrote:
> > core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
> > Lines 59 (patched)
> > 
> >
> > I suggest adding a short comment about what these list are about.

Thinking about the same.


- András


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


On July 26, 2017, 5:28 p.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61142/
> ---
> 
> (Updated July 26, 2017, 5:28 p.m.)
> 
> 
> Review request for oozie, Attila Sasvari and Peter Cseh.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3009 Number of Oozie tests executed dropped
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/service/JPAService.java 
> 93fe9da1564b734831e7b988ffe760f808af49fa 
>   core/src/main/java/org/apache/oozie/sla/SLARegistrationBean.java 
> 1b8370f01e5097300ee20e903ac745c23c999ce3 
>   
> core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
>  b742ca78520bdea804234460c36925beb105c5cb 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobsDeleteJPAExecutor.java
>  9077970fb11e10f158b1b742e6abbf4d056f92a8 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordActionsDeleteJPAExecutor.java
>  c7e0c38426d08c824b373409a9860a420e158821 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobsDeleteJPAExecutor.java
>  bff5836f209e1ec43de1b32203689909591896b7 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestWorkflowJobsDeleteJPAExecutor.java
>  c4ca61bf0ce678ae6bd0f6309a586f287e05537c 
>   core/src/test/java/org/apache/oozie/service/TestConfigurationService.java 
> 4cb2530cae634517ab833676b68deba068c7560b 
>   core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java 
> 34011f6b6f7f7ee4c57d63a1e62af4acb0fe32ba 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 
> 0ef4a4be6998744914e2ab56697cc2ae517070b9 
>   
> core/src/test/java/org/apache/oozie/util/db/TestPersistenceExceptionSubclassFilterRetryPredicate.java
>  76d2edc0e538732e65556d9255f49d4d1c0980b7 
> 
> 
> Diff: https://reviews.apache.org/r/61142/diff/1/
> 
> 
> Testing
> ---
> 
> Following test cases have been executed:
> ```
> TestOperationRetryHandler
> TestPersistenceExceptionSubclassFilterRetryPredicate
> TestParallelJPAOperationRetries
> TestWorkflow
> TestWorkflowRetries
> TestJPAService
> TestRetryAttemptState
> TestSLACalculatorMemory
> TestWorkflowJobsDeleteJPAExecutor
> TestPurgeService
> TestCoordJobsDeleteJPAExecutor
> TestBundleJobsDeleteJPAExecutor
> TestPurgeXCommand
> ```
> 
> 
> Thanks,
> 
> András Piros
> 
>

Re: Review Request 61142: OOZIE-3009 Number of Oozie tests executed dropped

[Peter Bacsko]

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




core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
Lines 59 (patched)


I suggest adding a short comment about what these list are about.


- Peter Bacsko


On júl. 26, 2017, 5:28 du, András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61142/
> ---
> 
> (Updated júl. 26, 2017, 5:28 du)
> 
> 
> Review request for oozie, Attila Sasvari and Peter Cseh.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3009 Number of Oozie tests executed dropped
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/service/JPAService.java 
> 93fe9da1564b734831e7b988ffe760f808af49fa 
>   core/src/main/java/org/apache/oozie/sla/SLARegistrationBean.java 
> 1b8370f01e5097300ee20e903ac745c23c999ce3 
>   
> core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
>  b742ca78520bdea804234460c36925beb105c5cb 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobsDeleteJPAExecutor.java
>  9077970fb11e10f158b1b742e6abbf4d056f92a8 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordActionsDeleteJPAExecutor.java
>  c7e0c38426d08c824b373409a9860a420e158821 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobsDeleteJPAExecutor.java
>  bff5836f209e1ec43de1b32203689909591896b7 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestWorkflowJobsDeleteJPAExecutor.java
>  c4ca61bf0ce678ae6bd0f6309a586f287e05537c 
>   core/src/test/java/org/apache/oozie/service/TestConfigurationService.java 
> 4cb2530cae634517ab833676b68deba068c7560b 
>   core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java 
> 34011f6b6f7f7ee4c57d63a1e62af4acb0fe32ba 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 
> 0ef4a4be6998744914e2ab56697cc2ae517070b9 
>   
> core/src/test/java/org/apache/oozie/util/db/TestPersistenceExceptionSubclassFilterRetryPredicate.java
>  76d2edc0e538732e65556d9255f49d4d1c0980b7 
> 
> 
> Diff: https://reviews.apache.org/r/61142/diff/1/
> 
> 
> Testing
> ---
> 
> Following test cases have been executed:
> ```
> TestOperationRetryHandler
> TestPersistenceExceptionSubclassFilterRetryPredicate
> TestParallelJPAOperationRetries
> TestWorkflow
> TestWorkflowRetries
> TestJPAService
> TestRetryAttemptState
> TestSLACalculatorMemory
> TestWorkflowJobsDeleteJPAExecutor
> TestPurgeService
> TestCoordJobsDeleteJPAExecutor
> TestBundleJobsDeleteJPAExecutor
> TestPurgeXCommand
> ```
> 
> 
> Thanks,
> 
> András Piros
> 
>

Re: Review Request 61142: OOZIE-3009 Number of Oozie tests executed dropped

[Attila Sasvari]

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




core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
Lines 59 (patched)


Could you please rename it and ``CAUSE_BLACKLIST`` so that they better 
resolve their purpose? As I understand we examine exceptions without a cause in 
case of ``ROOT_BLACKLIST``.


- Attila Sasvari


On July 26, 2017, 5:28 p.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61142/
> ---
> 
> (Updated July 26, 2017, 5:28 p.m.)
> 
> 
> Review request for oozie, Attila Sasvari and Peter Cseh.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3009 Number of Oozie tests executed dropped
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/service/JPAService.java 
> 93fe9da1564b734831e7b988ffe760f808af49fa 
>   core/src/main/java/org/apache/oozie/sla/SLARegistrationBean.java 
> 1b8370f01e5097300ee20e903ac745c23c999ce3 
>   
> core/src/main/java/org/apache/oozie/util/db/PersistenceExceptionSubclassFilterRetryPredicate.java
>  b742ca78520bdea804234460c36925beb105c5cb 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestBundleJobsDeleteJPAExecutor.java
>  9077970fb11e10f158b1b742e6abbf4d056f92a8 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordActionsDeleteJPAExecutor.java
>  c7e0c38426d08c824b373409a9860a420e158821 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobsDeleteJPAExecutor.java
>  bff5836f209e1ec43de1b32203689909591896b7 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestWorkflowJobsDeleteJPAExecutor.java
>  c4ca61bf0ce678ae6bd0f6309a586f287e05537c 
>   core/src/test/java/org/apache/oozie/service/TestConfigurationService.java 
> 4cb2530cae634517ab833676b68deba068c7560b 
>   core/src/test/java/org/apache/oozie/sla/TestSLACalculatorMemory.java 
> 34011f6b6f7f7ee4c57d63a1e62af4acb0fe32ba 
>   core/src/test/java/org/apache/oozie/test/XTestCase.java 
> 0ef4a4be6998744914e2ab56697cc2ae517070b9 
>   
> core/src/test/java/org/apache/oozie/util/db/TestPersistenceExceptionSubclassFilterRetryPredicate.java
>  76d2edc0e538732e65556d9255f49d4d1c0980b7 
> 
> 
> Diff: https://reviews.apache.org/r/61142/diff/1/
> 
> 
> Testing
> ---
> 
> Following test cases have been executed:
> ```
> TestOperationRetryHandler
> TestPersistenceExceptionSubclassFilterRetryPredicate
> TestParallelJPAOperationRetries
> TestWorkflow
> TestWorkflowRetries
> TestJPAService
> TestRetryAttemptState
> TestSLACalculatorMemory
> TestWorkflowJobsDeleteJPAExecutor
> TestPurgeService
> TestCoordJobsDeleteJPAExecutor
> TestBundleJobsDeleteJPAExecutor
> TestPurgeXCommand
> ```
> 
> 
> Thanks,
> 
> András Piros
> 
>

[jira] [Updated] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3018:

Affects Version/s: 4.3.0

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3018.001.patch
>
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within [*{{SchemaCheckerService.init()}}*| 
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
>  Addressing this issue.



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

[jira] [Updated] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3018:

Fix Version/s: 5.0.0

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Andras Piros
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-3018.001.patch
>
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within [*{{SchemaCheckerService.init()}}*| 
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
>  Addressing this issue.



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

[jira] [Updated] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3018:

Description: In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
{{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to use 
Hadoop's {{CredentialProvider}} class. Only one place [*was 
left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
 within [*{{SchemaCheckerService.init()}}*| 
https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
 Addressing this issue.  (was: In the [*previous JIRA*|OOZIE-2272] almost all 
the cases where {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were 
modified to use Hadoop's {{CredentialProvider}} class. Only one place [*was 
left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
 within {{SchemaCheckerService.init()}}. Addressing this issue.)

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Piros
>Assignee: Andras Piros
> Attachments: OOZIE-3018.001.patch
>
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within [*{{SchemaCheckerService.init()}}*| 
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
>  Addressing this issue.



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

[jira] [Updated] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3018:

Attachment: OOZIE-3018.001.patch

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Piros
>Assignee: Andras Piros
> Attachments: OOZIE-3018.001.patch
>
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within [*{{SchemaCheckerService.init()}}*| 
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/SchemaCheckerService.java#L52].
>  Addressing this issue.



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

[jira] [Updated] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3018:

Description: In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
{{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to use 
Hadoop's {{CredentialProvider}} class. Only one place [*was 
left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
 within {{SchemaCheckerService.init()}}. Addressing this issue.  (was: In the 
[*previous JIRA*|OOZIE-2272] almost all the cases where 
{{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to use 
Hadoop's {{Credentials}} class. Only one place has been left, within 
{{SchemaCheckerService.init()}}. Addressing this issue.)

> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> -
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
>  Issue Type: Bug
>Reporter: Andras Piros
>Assignee: Andras Piros
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
> {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to 
> use Hadoop's {{CredentialProvider}} class. Only one place [*was 
> left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281],
>  within {{SchemaCheckerService.init()}}. Addressing this issue.



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

[jira] [Created] (OOZIE-3018) Use Hadoop's CredentialProvider for passwords in SchemaCheckerService

[Andras Piros (JIRA)]

Andras Piros created OOZIE-3018:
---

 Summary: Use Hadoop's CredentialProvider for passwords in 
SchemaCheckerService
 Key: OOZIE-3018
 URL: https://issues.apache.org/jira/browse/OOZIE-3018
 Project: Oozie
  Issue Type: Bug
Reporter: Andras Piros
Assignee: Andras Piros


In the [*previous JIRA*|OOZIE-2272] almost all the cases where 
{{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to use 
Hadoop's {{Credentials}} class. Only one place has been left, within 
{{SchemaCheckerService.init()}}. Addressing this issue.



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

[jira] [Created] (OOZIE-3017) API for workflows: other action types

[Daniel Becker (JIRA)]

Daniel Becker created OOZIE-3017:


 Summary: API for workflows: other action types
 Key: OOZIE-3017
 URL: https://issues.apache.org/jira/browse/OOZIE-3017
 Project: Oozie
  Issue Type: Sub-task
Reporter: Daniel Becker
Assignee: Daniel Becker






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

[jira] [Updated] (OOZIE-2988) Investigate Apache Airflow

[Daniel Becker (JIRA)]

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

Daniel Becker updated OOZIE-2988:
-
Summary: Investigate Apache Airflow  (was: Inestigate Apache Airflow)

> Investigate Apache Airflow
> --
>
> Key: OOZIE-2988
> URL: https://issues.apache.org/jira/browse/OOZIE-2988
> Project: Oozie
>  Issue Type: Sub-task
>  Components: client
>Reporter: Andras Piros
>Assignee: Daniel Becker
>   Original Estimate: 16h
>  Time Spent: 16h
>  Remaining Estimate: 0h
>
> Investigate current version of [*Apache 
> Airflow*|https://airflow.incubator.apache.org/concepts.html] regarding 
> following:
> * how to define a DAG
> ** nodes
> ** edges
> ** transitions
> ** decision and fork / join nodes
> ** checks on DAGness, and on completeness
> * how are connections between DAGs handled
> ** state of one running / already finished DAG is respected by another DAG
> * creation / running process
> ** what to define w/ Python code
> ** and what using templates
> ** inheritance in Python
> ** third party libs in Python code while creating a DAG
> ** how are DAGs stored and submitted / run
> ** what patterns are used under the hood (builder, delegate, ...)
> ** how is logic considered (Oozie EL functions)
> * how to schedule a DAG (Oozie Coordinators)
> * how to bundle these together (Oozie Bundles)



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

[jira] [Created] (OOZIE-3016) Documentation: blog entry

[Daniel Becker (JIRA)]

Daniel Becker created OOZIE-3016:


 Summary: Documentation: blog entry
 Key: OOZIE-3016
 URL: https://issues.apache.org/jira/browse/OOZIE-3016
 Project: Oozie
  Issue Type: Sub-task
Reporter: Daniel Becker






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

[jira] [Created] (OOZIE-3015) Documentation: public part (TWiki and KnowledgeBase)

[Daniel Becker (JIRA)]

Daniel Becker created OOZIE-3015:


 Summary: Documentation: public part (TWiki and KnowledgeBase)
 Key: OOZIE-3015
 URL: https://issues.apache.org/jira/browse/OOZIE-3015
 Project: Oozie
  Issue Type: Sub-task
Reporter: Daniel Becker
Assignee: Daniel Becker






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

[jira] [Created] (OOZIE-3014) Documentation: Javadoc

[Daniel Becker (JIRA)]

Daniel Becker created OOZIE-3014:


 Summary: Documentation: Javadoc
 Key: OOZIE-3014
 URL: https://issues.apache.org/jira/browse/OOZIE-3014
 Project: Oozie
  Issue Type: Sub-task
Reporter: Daniel Becker
Assignee: Daniel Becker


Classes, test classes, public methods.



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

[jira] [Assigned] (OOZIE-3005) Refactor the latest oozie-workflow.xsd so that it uses xs:include on XSDs for actions that have their own, so JAXB can find these

[Daniel Becker (JIRA)]

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

Daniel Becker reassigned OOZIE-3005:


Assignee: Andras Piros

> Refactor the latest oozie-workflow.xsd so that it uses xs:include on XSDs for 
> actions that have their own, so JAXB can find these
> -
>
> Key: OOZIE-3005
> URL: https://issues.apache.org/jira/browse/OOZIE-3005
> Project: Oozie
>  Issue Type: Sub-task
>  Components: client
>Reporter: Daniel Becker
>Assignee: Andras Piros
>




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

[jira] [Assigned] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas

[Daniel Becker (JIRA)]

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

Daniel Becker reassigned OOZIE-2339:


Assignee: Andras Piros  (was: Daniel Becker)

> Provide an API for writing jobs based on the XSD schemas
> 
>
> Key: OOZIE-2339
> URL: https://issues.apache.org/jira/browse/OOZIE-2339
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Kanter
>Assignee: Andras Piros
>
> Users often complain about the XML they have to write for Oozie jobs.  It 
> would be nice if they could write them in something like Java, but we don't 
> want to have to maintain a separate Java API for this.  I was looking around 
> and saw that JAXB might be the right thing here.  From what I can tell, it 
> lets you create Java classes from XSD schemas.  So, we should be able to 
> auto-generate a Java API for writing Oozie jobs, without having to really 
> maintain it.
> We should investigate if this is feasible and, if so, implement it.
> Some useful looking links:
> * [JAXB 
> overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding]
> * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html]
> * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home]
> * [Apache Falcon|https://falcon.apache.org]
> Key features:
> * must have:
> ** inside an {{oozie-jobs-api}} artifact
> ** able to create workflow / coordinator / bundle definitions programmatically
> ** synchronizing each and every XSD change on rebuild
> ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and 
> {{jobs.properties}} artifacts of every XSD version
> ** cloneability of workflow etc. {{Object}} s
> ** perform cross checks, e.g. that the workflow graph is a DAG
> ** only latest XSD versions should be supported as must have
> * nice to have:
> ** XSD version(s) can be provided. When not provided, latest ones are 
> considered as valid
> ** implement a [*fluent API*|https://en.wikipedia.org/wiki/Fluent_interface]
> ** have a Python / Jython REPL to make it easy to experiment
> ** create documentation about usage
> ** can read {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and 
> {{jobs.properties}} artifacts of every XSD version
> ** can convert between XSD versions
> ** support XSD change on the fly (within REPL)
> ** support HDFS reads / writes
> ** support dry run on an Oozie server to perform checks



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

[jira] [Updated] (OOZIE-3011) API for workflows: decision nodes autogeneration

[Daniel Becker (JIRA)]

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

Daniel Becker updated OOZIE-3011:
-
Remaining Estimate: 24h
 Original Estimate: 24h

> API for workflows: decision nodes autogeneration
> 
>
> Key: OOZIE-3011
> URL: https://issues.apache.org/jira/browse/OOZIE-3011
> Project: Oozie
>  Issue Type: Sub-task
>  Components: client
>Reporter: Andras Piros
>Assignee: Daniel Becker
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




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

[jira] [Updated] (OOZIE-3010) API for workflows: fork / join node autogeneration

[Daniel Becker (JIRA)]

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

Daniel Becker updated OOZIE-3010:
-
Remaining Estimate: 32h
 Original Estimate: 32h

> API for workflows: fork / join node autogeneration
> --
>
> Key: OOZIE-3010
> URL: https://issues.apache.org/jira/browse/OOZIE-3010
> Project: Oozie
>  Issue Type: Sub-task
>  Components: client
>Reporter: Andras Piros
>Assignee: Daniel Becker
>   Original Estimate: 32h
>  Remaining Estimate: 32h
>




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

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

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2662:
--
Summary: DB migration fails if database is too big  (was: DB migration 
fails if DB is too big)

> DB migration fails if database 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, OOZIE-2662.004.patch, 
> OOZIE-2662.005.patch, OOZIE-2662.006.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-2662) DB migration fails if database is too big

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2662:
---

+1

> DB migration fails if database 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, OOZIE-2662.004.patch, 
> OOZIE-2662.005.patch, OOZIE-2662.006.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

[Peter Cseh]

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


Ship it!




Ship It!

- Peter Cseh


On July 17, 2017, 4:05 p.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/52782/
> ---
> 
> (Updated July 17, 2017, 4:05 p.m.)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Cseh, Peter Bacsko, and 
> Robert Kanter.
> 
> 
> 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
> -
> 
>   core/src/main/resources/oozie-default.xml 
> 832bbe14a4b027e198061527a956e2992cbec174 
>   tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java 
> 0e14a30693a76b8b2bdc2f7ceaf3f045d69f4155 
>   tools/src/test/java/org/apache/oozie/tools/TestDBLoadDump.java 
> c43223ef05aa702be49565ba2626314628e63749 
>   tools/src/test/resources/dumpData/invalid/ooziedb_ac.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_sysinfo.json PRE-CREATION 
>   tools/src/test/resources/dumpData/invalid/ooziedb_wf.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_ac.json  
>   tools/src/test/resources/dumpData/ooziedb_bna.json  
>   tools/src/test/resources/dumpData/ooziedb_bnj.json  
>   tools/src/test/resources/dumpData/ooziedb_ca.json  
>   tools/src/test/resources/dumpData/ooziedb_cj.json  
>   tools/src/test/resources/dumpData/ooziedb_slareg.json  
>   tools/src/test/resources/dumpData/ooziedb_slasum.json  
>   tools/src/test/resources/dumpData/ooziedb_sysinfo.json  
>   tools/src/test/resources/dumpData/ooziedb_wf.json  
>   tools/src/test/resources/dumpData/valid/ooziedb_slareg.json PRE-CREATION 
>   tools/src/test/resources/dumpData/valid/ooziedb_slasum.json PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/52782/diff/6/
> 
> 
> Testing
> ---
> 
> See `TestDBLoadDump` for further reference.
> 
> 
> Thanks,
> 
> András Piros
> 
>

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

[Denes Bodo]

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

(Updated July 31, 2017, 9:57 a.m.)


Review request for oozie.


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


Repository: oozie-git


Description
---

Possible NullPointerException


Diffs
-

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


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


Testing (updated)
---


Thanks,

Denes Bodo

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (110 issues)

Subscriber: ooziedaily

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

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (115 issues)

Subscriber: ooziedaily

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