[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2105:
--

Yeah, I think we can close this as won't fix.  This was specifically about the 
repackaging of Hadoop stuff where we had hybrid versions (e.g. 
{{1.1.1.oozie-4.1.0}}: that is, Hadoop 1.1.1 in Oozie 4.1.0), which we're not 
doing anymore.  Those versions didn't work with the maven version plugin 
command.

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2211:
-

failing test is unrelated, passes locally.

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch, 
> OOZIE-2211.02.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2105:
-

[~rkanter] that's why I was wondering if this Jira made any sense at this 
point, I remember https://issues.apache.org/jira/browse/OOZIE-3097 where I used 
the mvn versions command to change all child modules. Maybe close this as won't 
fix?

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2352) Unportable shebang in shell scripts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2352:
--

PreCommit-OOZIE-Build started


> Unportable shebang in shell scripts
> ---
>
> Key: OOZIE-2352
> URL: https://issues.apache.org/jira/browse/OOZIE-2352
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Dmitry Sivachenko
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2352-00.patch
>
>
> Some shell scripts in oozie distribution use unportable shebangs:
> #!/bin/bash
> bash shell interpreter may be installed in different locations (e.g 
> /usr/local/bin/bash on FreeBSD).
> The proposed solution is to use more portable
> #!/usr/bin/env bash
> instead.
> Affected files:
> client/src/main/bin/oozie
> distro/src/main/bin/addtowar.sh
> distro/src/main/bin/oozied.sh
> distro/src/main/bin/oozie-setup.sh
> distro/src/main/bin/oozie-sys.sh
> tools/src/main/bin/ooziedb.sh
> core/src/main/conf/oozie-env.sh



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

[jira] [Assigned] (OOZIE-2352) Unportable shebang in shell scripts

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-2352:
---

Assignee: Artem Ervits

> Unportable shebang in shell scripts
> ---
>
> Key: OOZIE-2352
> URL: https://issues.apache.org/jira/browse/OOZIE-2352
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Dmitry Sivachenko
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2352-00.patch
>
>
> Some shell scripts in oozie distribution use unportable shebangs:
> #!/bin/bash
> bash shell interpreter may be installed in different locations (e.g 
> /usr/local/bin/bash on FreeBSD).
> The proposed solution is to use more portable
> #!/usr/bin/env bash
> instead.
> Affected files:
> client/src/main/bin/oozie
> distro/src/main/bin/addtowar.sh
> distro/src/main/bin/oozied.sh
> distro/src/main/bin/oozie-setup.sh
> distro/src/main/bin/oozie-sys.sh
> tools/src/main/bin/ooziedb.sh
> core/src/main/conf/oozie-env.sh



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

[jira] [Updated] (OOZIE-2352) Unportable shebang in shell scripts

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2352:

Attachment: OOZIE-2352-00.patch

> Unportable shebang in shell scripts
> ---
>
> Key: OOZIE-2352
> URL: https://issues.apache.org/jira/browse/OOZIE-2352
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Dmitry Sivachenko
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2352-00.patch
>
>
> Some shell scripts in oozie distribution use unportable shebangs:
> #!/bin/bash
> bash shell interpreter may be installed in different locations (e.g 
> /usr/local/bin/bash on FreeBSD).
> The proposed solution is to use more portable
> #!/usr/bin/env bash
> instead.
> Affected files:
> client/src/main/bin/oozie
> distro/src/main/bin/addtowar.sh
> distro/src/main/bin/oozied.sh
> distro/src/main/bin/oozie-setup.sh
> distro/src/main/bin/oozie-sys.sh
> tools/src/main/bin/ooziedb.sh
> core/src/main/conf/oozie-env.sh



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

[jira] [Commented] (OOZIE-2339) Fluent Job API

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2339:
--


Testing JIRA OOZIE-2339

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 2 line(s) longer than 132 
characters
.{color:green}+1{color} the patch adds/modifies 93 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:red}-1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:red}-1{color} the patch seems to introduce 24 new Javadoc error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s)
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 8 new javac warning(s)
{color:red}-1{color} There are [118] new bugs found below threshold in total 
that must be fixed.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:red}-1{color} There are [1] new bugs found below threshold in [core] 
that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
core/findbugs-new.html
. The most important FindBugs errors are:
. At V1JobsServlet.java:[line 170]: String.format(String, Object[]) needs 
printf-style format but called with MessageFormat
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:red}-1{color} There are [113] new bugs found below threshold in 
[fluent-job/fluent-job-api] that must be fixed, listing only the first [5] ones.
. You can find the FindBugs diff here (look for the red and orange ones): 
fluent-job/fluent-job-api/findbugs-new.html
. The top [5] most important FindBugs errors are:
. At ACTION.java:[lines 413-414]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.ACTION.equals(Object) is 
unusual
. At CHGRP.java:[lines 236-237]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CHGRP.equals(Object) is 
unusual
. At CHMOD.java:[lines 236-237]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CHMOD.equals(Object) is 
unusual
. At CONFIGURATION.java:[lines 133-134]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CONFIGURATION.equals(Object)
 is unusual
. At CONFIGURATION.java:[lines 318-319]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CONFIGURATION$Property.equals(Object)
 is unusual
. {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/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {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/spark].
. {color:red}-1{color} There are [2] new bugs found below threshold in [client] 
that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
. The most important FindBugs errors are:
. At OozieCLI.java:[line 1425]: java/io/File.init(Ljava/lang/String;)V 
reads a file whose location might be specified by user input
. java/io/FileOutputStream.init(Ljava/lang/String;)V writes to a file 
whose location might be specified by user input: At OozieCLI.java:[line 1425]
. At ApiJarFactory.java:[line 70]: At ApiJarFactory.java:[line 71]
. {color:red}-1{color} There are [2] new bugs found below threshold in 
[examples] that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
examples/findbugs-new.html
. The most important FindBugs errors are:
. At Shell.java:[line 53]: Dead store to happyPath in 
org.apache.oozie.example.fluentjob.Shell.create()
. At Shell.java:[line 59]: Dead store to sadPath in 
org.apache.oozie.example.fluentjob.Shell.create()
. {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 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 

Failed: OOZIE-2339 PreCommit Build #577

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.87 MB...]
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 2 line(s) longer than 132 characters
+1 the patch adds/modifies 93 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
-1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
-1 the patch seems to introduce 24 new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(s)
-1 COMPILE
+1 HEAD compiles
+1 patch compiles
-1 the patch seems to introduce 8 new javac warning(s)
-1 There are [118] new bugs found below threshold in total that must be fixed.
 +1 There are no new bugs found in [webapp].
 -1 There are [1] new bugs found below threshold in [core] that must be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
core/findbugs-new.html
 The most important FindBugs errors are:
 At V1JobsServlet.java:[line 170]: String.format(String, Object[]) needs 
printf-style format but called with MessageFormat
 +1 There are no new bugs found in [tools].
 -1 There are [113] new bugs found below threshold in 
[fluent-job/fluent-job-api] that must be fixed, listing only the first [5] ones.
 You can find the FindBugs diff here (look for the red and orange ones): 
fluent-job/fluent-job-api/findbugs-new.html
 The top [5] most important FindBugs errors are:
 At ACTION.java:[lines 413-414]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.ACTION.equals(Object) is 
unusual
 At CHGRP.java:[lines 236-237]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CHGRP.equals(Object) is 
unusual
 At CHMOD.java:[lines 236-237]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CHMOD.equals(Object) is 
unusual
 At CONFIGURATION.java:[lines 133-134]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CONFIGURATION.equals(Object)
 is unusual
 At CONFIGURATION.java:[lines 318-319]: 
org.apache.oozie.fluentjob.api.generated.action.distcp.CONFIGURATION$Property.equals(Object)
 is unusual
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 -1 There are [2] new bugs found below threshold in [client] that must be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
 The most important FindBugs errors are:
 At OozieCLI.java:[line 1425]: java/io/File.init(Ljava/lang/String;)V 
reads a file whose location might be specified by user input
 java/io/FileOutputStream.init(Ljava/lang/String;)V writes to a file 
whose location might be specified by user input: At OozieCLI.java:[line 1425]
 At ApiJarFactory.java:[line 70]: At ApiJarFactory.java:[line 71]
 -1 There are [2] new bugs found below threshold in [examples] that must be 
fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
examples/findbugs-new.html
 The most important FindBugs errors are:
 At Shell.java:[line 53]: Dead store to happyPath in 
org.apache.oozie.example.fluentjob.Shell.create()
 At Shell.java:[line 59]: Dead store to sadPath in 
org.apache.oozie.example.fluentjob.Shell.create()
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2857
Tests failed: 5
Tests errors: 1

The patch failed the following testcases:

testValidateJar(org.apache.oozie.client.TestOozieCLI)
testRunJarWithoutAppPath(org.apache.oozie.client.TestOozieCLI)
testSubmitJarWithoutAppPath(org.apache.oozie.client.TestOozieCLI)
testSubmitJar(org.apache.oozie.client.TestOozieCLI)
testRunJar(org.apache.oozie.client.TestOozieCLI)

Tests failing with errors:
whenWorkflowXmlWithAllActionTypesIsUnmarshalledAttributesArePreserved(org.apache.oozie.jobs.client.jaxb.TestJAXBWorkflow)

Tests failed at first run:
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


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


The full output of the test-patch run is 

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2105:
--

Can't you just use the maven versions plugin to update the versions as-is?
e.g.
{code}
mvn versions:set -DnewVersion=5.1.0
{code}

As for the warning when using an expression, that's been a long-standing issue 
that Maven doesn't like non-constant versions in poms (other than for 
dependencies).

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2105:
---

If it's inherited from the parent pom it will make our lives significantly 
easier with version bumps.


> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2105:
--


Testing JIRA OOZIE-2105

Cleaning local git workspace



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


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


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

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



> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

Failed: OOZIE-2105 PreCommit Build #576

[Apache Jenkins Server]

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

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


Testing JIRA OOZIE-2105

Cleaning local git workspace



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


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  30190 0  100  3019  0   3820 --:--:-- --:--:-- --:--:--  
3816{"self":"https://issues.apache.org/jira/rest/api/2/issue/12765021/comment/16489784","id":"16489784","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 

Failed: OOZIE-2211 PreCommit Build #575

[Apache Jenkins Server]

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

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


Testing JIRA OOZIE-2211

Cleaning local git workspace



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


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32110 0  100  3211  0   3696 --:--:-- --:--:-- --:--:--  
3695{"self":"https://issues.apache.org/jira/rest/api/2/issue/12822363/comment/16489763","id":"16489763","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 

Failed: OOZIE-3256 PreCommit Build #573

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive2].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[ERROR] There are [1] new bugs found below threshold in total that must be 
fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2841 bytes
[TRACE] Full summary file size is 1792 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3256

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 1 line(s) longer than 132 characters
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 the patch does not seem to introduce new Javadoc error(s)
ERROR: the current HEAD has 2 Javadoc error(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
-1 There are [1] new bugs found below threshold in total that must be fixed.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [server].
 -1 There are [1] new bugs found below threshold in [client] that must be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
 The most important FindBugs errors are:
 At OozieCLI.java:[line 1398]: Format-string method String.format(String, 
Object[]) called with format string "%-43s%-10s%-37s%-10s%-21s%-21s" wants 6 
arguments but is given 7 in 
org.apache.oozie.cli.OozieCLI.lambda$printCoordJob$4(String, boolean, 
CoordinatorAction)
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [webapp].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 2134
Tests failed at first run:
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  39080   200  100  3708480   8899 --:--:-- --:--:-- --:--:--  8913
{"errorMessages":["Unexpected character ('%' (code 37)): was expecting comma to 
separate OBJECT entries\n at [Source: 
org.apache.catalina.connector.CoyoteInputStream@e67d66c; line: 1, column: 
1994]"]}
test-patch exit code: 1

Build step 'Execute shell' marked build as failure

[jira] [Commented] (OOZIE-2339) Fluent Job API

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2339:
--

PreCommit-OOZIE-Build started


> Fluent Job API
> --
>
> 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
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, 
> OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, 
> OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch, 
> OOZIE-2339.011.patch, OOZIE-2339.012.patch, OOZIE-2339.013.patch, 
> OOZIE-2339.014.patch
>
>
> 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 a {{fluent-job-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 / Py4J REPL to make it easy to experiment with also 
> for data engineers / data scientists
> ** 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
(v7.6.3#76005)

[jira] [Updated] (OOZIE-2339) Fluent Job API

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2339:

Attachment: OOZIE-2339.014.patch

> Fluent Job API
> --
>
> 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
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, 
> OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, 
> OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch, 
> OOZIE-2339.011.patch, OOZIE-2339.012.patch, OOZIE-2339.013.patch, 
> OOZIE-2339.014.patch
>
>
> 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 a {{fluent-job-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 / Py4J REPL to make it easy to experiment with also 
> for data engineers / data scientists
> ** 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
(v7.6.3#76005)

[jira] [Commented] (OOZIE-2339) Fluent Job API

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2339:
-

Addressing review comments, documentation extensions.

> Fluent Job API
> --
>
> 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
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, 
> OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, 
> OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch, 
> OOZIE-2339.011.patch, OOZIE-2339.012.patch, OOZIE-2339.013.patch, 
> OOZIE-2339.014.patch
>
>
> 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 a {{fluent-job-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 / Py4J REPL to make it easy to experiment with also 
> for data engineers / data scientists
> ** 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
(v7.6.3#76005)

Re: Review Request 64029: OOZIE-2339 Provide an API for writing jobs based on the XSD schemas

[András Piros via Review Board]

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

(Updated May 24, 2018, 7:36 p.m.)


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


Changes
---

Addressing review comments, documentation changes.


Repository: oozie-git


Description
---

OOZIE-2339 Provide an API for writing jobs based on the XSD schemas


Diffs (updated)
-

  client/pom.xml 7d36e2d5941e598520a653a9eb4b293c763378e3 
  client/src/main/java/org/apache/oozie/cli/OozieCLI.java 
28286338d1a208df934c2f9dbd30dd0c6b2745d0 
  client/src/main/java/org/apache/oozie/client/ApiJarFactory.java PRE-CREATION 
  client/src/main/java/org/apache/oozie/client/ApiJarLoader.java PRE-CREATION 
  client/src/main/java/org/apache/oozie/client/OozieClient.java 
4c8175628ba5ee346d97ad984532662032b88acc 
  core/pom.xml 45880a619e70a1643f4eb5ceeb61abb2090551f1 
  core/src/main/java/org/apache/oozie/BaseLocalOozieClient.java 
38fb006980c0acb582b4f91175be1ced8a1afa79 
  core/src/main/java/org/apache/oozie/local/LocalOozie.java 
9ab646cd53223d903e387eb92aa103a7b6577d0f 
  core/src/main/java/org/apache/oozie/servlet/BaseJobServlet.java 
e1bd3cf61aabfa4311881b2944fc9f10ffe9145d 
  core/src/main/java/org/apache/oozie/servlet/BaseJobsServlet.java 
d4b08711223356c8d4f58a3391b6b87efa0a2b73 
  core/src/main/java/org/apache/oozie/servlet/ServletUtilities.java 
3eb32d50d07687c136fcc0e467a055bdc1e7ec60 
  core/src/main/java/org/apache/oozie/servlet/V0JobsServlet.java 
1d800949cbff34a95f2ae111364eb8cbc6a5f5fb 
  core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java 
c1ca65fd2f8bf0f3e5c618dddcba3bf52eaf5420 
  core/src/main/java/org/apache/oozie/servlet/V2ValidateServlet.java 
b86fa6ace43aead115302aad3ae15368b15f1923 
  core/src/main/resources/oozie-default.xml 
c54db34ffeb560eef3d87abd4d926b4e6a6b5300 
  core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 
3395cc25d27805444ba0b6463357c4ecff977ac1 
  core/src/test/java/org/apache/oozie/servlet/TestV1JobsServlet.java 
fb481e367653187a94199069199f1d1b06d1cecf 
  core/src/test/java/org/apache/oozie/test/MiniOozieTestCase.java 
0a030d660f9c545b520afcce458a27ba2a367658 
  docs/src/site/twiki/DG_CommandLineTool.twiki 
9a174596dd78fb15989daf4e88936a9a2b09ef13 
  docs/src/site/twiki/DG_CustomActionExecutor.twiki 
4acbf0d40ae36c441f8510e107243603fa0e001b 
  docs/src/site/twiki/DG_Examples.twiki 
13dfa28c0eecab70321886b2806a791346c46d3b 
  docs/src/site/twiki/DG_FluentJobAPI.twiki PRE-CREATION 
  examples/pom.xml c13febc81cf5b26b4af90885787113e247ae7cb8 
  examples/src/main/java/org/apache/oozie/example/fluentjob/Credentials.java 
PRE-CREATION 
  examples/src/main/java/org/apache/oozie/example/fluentjob/Global.java 
PRE-CREATION 
  examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java 
PRE-CREATION 
  
examples/src/main/java/org/apache/oozie/example/fluentjob/MultipleShellActions.java
 PRE-CREATION 
  examples/src/main/java/org/apache/oozie/example/fluentjob/Parameters.java 
PRE-CREATION 
  examples/src/main/java/org/apache/oozie/example/fluentjob/Shell.java 
PRE-CREATION 
  examples/src/main/java/org/apache/oozie/example/fluentjob/Spark.java 
PRE-CREATION 
  fluent-job/fluent-job-api/pom.xml PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/Condition.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/GraphVisualization.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/ModifyOnce.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/ActionAttributes.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/ActionAttributesBuilder.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/Builder.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/ChFSBase.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/ChFSBaseBuilder.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/Chgrp.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/ChgrpBuilder.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/Chmod.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/ChmodBuilder.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/Delete.java
 PRE-CREATION 
  
fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action/DistcpAction.java
 PRE-CREATION 
  

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2105:
--

PreCommit-OOZIE-Build started


> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Comment Edited] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-2105 at 5/24/18 7:14 PM:
--

[~andras.piros] once I change the version to expression, we get warnings
{code:java}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-client:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-client:${project.parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/client/pom.xml, line 29, column 14
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-core:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml, line 29, column 14
[WARNING] The expression ${parent.version} is deprecated. Please use 
${project.parent.version} instead. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml{code}
I'm submitting a new patch with version removed, it will inherit version from 
parent. Btw, ${project.parent.version} expression also throws a warning.


was (Author: dbist13):
[~andras.piros] once I change the version to expression, we get warnings
{code:java}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-client:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-client:${project.parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/client/pom.xml, line 29, column 14
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-core:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml, line 29, column 14
[WARNING] The expression ${parent.version} is deprecated. Please use 
${project.parent.version} instead. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml{code}
I'm submitting a new patch with version removed, it will inherit version from 
parent.

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2211:
--


Testing JIRA OOZIE-2211

Cleaning local git workspace



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

.The patch failed the following testcases:

testValid(org.apache.oozie.cli.TestValidation)
testInvalid(org.apache.oozie.cli.TestValidation)

.Tests failing with errors:


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


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


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

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



> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch, 
> OOZIE-2211.02.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Updated] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2105:

Attachment: OOZIE-2105-03.patch

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

Failed: OOZIE-2211 PreCommit Build #572

[Apache Jenkins Server]

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

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


Testing JIRA OOZIE-2211

Cleaning local git workspace



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

The patch failed the following testcases:

testValid(org.apache.oozie.cli.TestValidation)
testInvalid(org.apache.oozie.cli.TestValidation)

Tests failing with errors:


+1 DISTRO
+1 distro tarball builds with the patch 


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


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

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

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

Re: Review Request 64029: OOZIE-2339 Provide an API for writing jobs based on the XSD schemas

[András Piros via Review Board]

> On May 20, 2018, 10:14 p.m., Robert Kanter wrote:
> > core/src/main/resources/oozie-default.xml
> > Lines 3326 (patched)
> > 
> >
> > When using the Fluent API, how does Oozie choose which HDFS to use?

The same way as 
[`ShareLibService#init()`](https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/service/ShareLibService.java#L128-L133)
 sets the reference for `private FileSystem fs`.


> On May 20, 2018, 10:14 p.m., Robert Kanter wrote:
> > fluent-job/fluent-job-api/pom.xml
> > Lines 122-131 (patched)
> > 
> >
> > Shouldn't these be the newest 1.x XSDs?

`distcp-action-1.0.xsd` needed to be updated. All the others are already 
up-to-date.


> On May 20, 2018, 10:14 p.m., Robert Kanter wrote:
> > fluent-job/fluent-job-api/src/test/java/org/apache/oozie/fluentjob/api/factory/SimpleWorkflowFactory.java
> > Lines 33 (patched)
> > 
> >
> > This seems like it belongs in the examples?

Duplicated under `org.apache.oozie.examples.fluentjob.Shell.java` to have it as 
example as well.

We need it here, too, because `TestOozieCLI` uses it, and we don't want 
`oozie-client` depend on `oozie-examples`.


- András


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


On May 14, 2018, 8:36 p.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64029/
> ---
> 
> (Updated May 14, 2018, 8:36 p.m.)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Cseh, and Robert Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2339 Provide an API for writing jobs based on the XSD schemas
> 
> 
> Diffs
> -
> 
>   client/pom.xml 795a92d4af1a6d96603c99506cd70e8cf8e2c347 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 
> 4abc7502c0c9d8b59ded2baaed30c407ad073008 
>   client/src/main/java/org/apache/oozie/client/ApiJarFactory.java 
> PRE-CREATION 
>   client/src/main/java/org/apache/oozie/client/ApiJarLoader.java PRE-CREATION 
>   client/src/main/java/org/apache/oozie/client/OozieClient.java 
> 4c8175628ba5ee346d97ad984532662032b88acc 
>   core/pom.xml 45880a619e70a1643f4eb5ceeb61abb2090551f1 
>   core/src/main/java/org/apache/oozie/BaseLocalOozieClient.java 
> 38fb006980c0acb582b4f91175be1ced8a1afa79 
>   core/src/main/java/org/apache/oozie/local/LocalOozie.java 
> 9ab646cd53223d903e387eb92aa103a7b6577d0f 
>   core/src/main/java/org/apache/oozie/servlet/BaseJobServlet.java 
> e1bd3cf61aabfa4311881b2944fc9f10ffe9145d 
>   core/src/main/java/org/apache/oozie/servlet/BaseJobsServlet.java 
> d4b08711223356c8d4f58a3391b6b87efa0a2b73 
>   core/src/main/java/org/apache/oozie/servlet/ServletUtilities.java 
> 3eb32d50d07687c136fcc0e467a055bdc1e7ec60 
>   core/src/main/java/org/apache/oozie/servlet/V0JobsServlet.java 
> 1d800949cbff34a95f2ae111364eb8cbc6a5f5fb 
>   core/src/main/java/org/apache/oozie/servlet/V1JobsServlet.java 
> c1ca65fd2f8bf0f3e5c618dddcba3bf52eaf5420 
>   core/src/main/java/org/apache/oozie/servlet/V2ValidateServlet.java 
> b86fa6ace43aead115302aad3ae15368b15f1923 
>   core/src/main/resources/oozie-default.xml 
> 6f8925828090cee29a818de30a7c31db0617d816 
>   core/src/test/java/org/apache/oozie/client/TestOozieCLI.java 
> 3395cc25d27805444ba0b6463357c4ecff977ac1 
>   core/src/test/java/org/apache/oozie/servlet/TestV1JobsServlet.java 
> fb481e367653187a94199069199f1d1b06d1cecf 
>   core/src/test/java/org/apache/oozie/test/MiniOozieTestCase.java 
> 0a030d660f9c545b520afcce458a27ba2a367658 
>   docs/src/site/twiki/DG_CommandLineTool.twiki 
> 9a174596dd78fb15989daf4e88936a9a2b09ef13 
>   docs/src/site/twiki/DG_FluentJobAPI.twiki PRE-CREATION 
>   examples/pom.xml 2bfc7c8b3fc3de4876c62d70f25bed35b886ece8 
>   examples/src/main/java/org/apache/oozie/example/fluentjob/Credentials.java 
> PRE-CREATION 
>   examples/src/main/java/org/apache/oozie/example/fluentjob/Global.java 
> PRE-CREATION 
>   examples/src/main/java/org/apache/oozie/example/fluentjob/JavaMain.java 
> PRE-CREATION 
>   examples/src/main/java/org/apache/oozie/example/fluentjob/Parameters.java 
> PRE-CREATION 
>   examples/src/main/java/org/apache/oozie/example/fluentjob/Shell.java 
> PRE-CREATION 
>   examples/src/main/java/org/apache/oozie/example/fluentjob/Spark.java 
> PRE-CREATION 
>   fluent-job/fluent-job-api/pom.xml PRE-CREATION 
>   
> fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/Condition.java
>  PRE-CREATION 
>   
> 

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2105:
-

[~andras.piros] once I change the version to expression, we get warnings
{code:java}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-client:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-client:${project.parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/client/pom.xml, line 29, column 14
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-core:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml, line 29, column 14
[WARNING] The expression ${parent.version} is deprecated. Please use 
${project.parent.version} instead. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml{code}
I'm submitting a new patch with version removed, it will inherit version from 
parent.

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2211:
--

PreCommit-OOZIE-Build started


> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch, 
> OOZIE-2211.02.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

Failed: OOZIE-2211 PreCommit Build #574

[Apache Jenkins Server]

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

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


Testing JIRA OOZIE-2211

Cleaning local git workspace



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


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0  30400 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/12822363/comment/16489593","id":"16489593","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Attachment: OOZIE-2211.02.patch

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch, 
> OOZIE-2211.02.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Commented] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2211:
--


Testing JIRA OOZIE-2211

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s)
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{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 [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [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/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {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/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 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:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch


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


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

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



> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch, 
> OOZIE-2211.02.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Commented] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2211:
--

PreCommit-OOZIE-Build started


> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Attachment: OOZIE-2211.01.patch

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

Failed: OOZIE-2105 PreCommit Build #571

[Apache Jenkins Server]

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

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


Testing JIRA OOZIE-2105

Cleaning local git workspace



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


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/12765021/comment/16489576","id":"16489576","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2105:
--


Testing JIRA OOZIE-2105

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}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 85 new javac warning(s)
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [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/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {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/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 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: 2134
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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



> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-3256) refactor OozieCLI class

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3256:
--

PreCommit-OOZIE-Build started


> refactor OozieCLI class
> ---
>
> Key: OOZIE-3256
> URL: https://issues.apache.org/jira/browse/OOZIE-3256
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 5.0.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: OOZIE-3256.00.patch
>
>




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

Re: Review Request 64029: OOZIE-2339 Provide an API for writing jobs based on the XSD schemas

[András Piros via Review Board]

> On March 27, 2018, 1:02 a.m., Robert Kanter wrote:
> > docs/src/site/twiki/DG_JobsAPI.twiki
> > Lines 61 (patched)
> > 
> >
> > How does this work for backwards compatibility?  i.e. If I generate a 
> > jar using wf schema 1.0 and then upgrade Oozie which includes a 1.1 schema, 
> > is my jar no longer accepted by Oozie?  Do I need to recompile?  Is it 
> > possible that the API has changed and it won't compile anymore?
> > 
> > We should make sure to have a good story around backwards 
> > compatibility.  I think it's reasonable to only _generate_ jars using the 
> > latest schema, but we should at least accept older jars, ideally without 
> > recompiling.
> 
> András Piros wrote:
> When new schemas are introduced to Oozie, old Fluent Job API JARs as well 
> as old workflow.xml definitions keep of course working.
> 
> For the time being I would ship this feature without any more guarantees 
> on backward compatibility - the patch is way too huge to deal with anyways. 
> We can consider something like having guest-facing API packages versioned 
> like `org.apache.oozie.fluentjob.api.v1.workflow` to maintain binary 
> compatibility to older XSDs and be able to innovate effortless later.
> 
> What do you think?

Introduced Hadoop annotations:
```
@InterfaceAudience.Private
@InterfaceStability.Unstable
```
for all classes of packages inside `fluent-job-api`:
* `org.apache.oozie.fluentjob.api.action`
* `org.apache.oozie.fluentjob.api.factory`
* `org.apache.oozie.fluentjob.api.workflow`

Moreover, writing another part to `DG_FluentJobAPI.twiki` stating about current 
plans of supporting backwards compatibility.


> On March 27, 2018, 1:02 a.m., Robert Kanter wrote:
> > jobs/jobs-api/pom.xml
> > Lines 111-120 (patched)
> > 
> >
> > It's unfortunate that we have to keep this manually :(
> > 
> > I hope we don't forget to update this when adding new schema versions.  
> > Perhaps there's some way to write a unit test that would fail if a 
> > developer added a newer schema version and didn't update this?  That would 
> > prevent this issue.
> 
> András Piros wrote:
> Yes, we have to maintain that stuff manually.
> 
> Writing a piece of documentation about how to extend new schema versions 
> and maintain backwards compatibility. This is achieved by extending this 
> `pom.xml` and `xjb/bindings.xml` for the new schema versions, and for the new 
> Fluent API JAR generated packages.
> 
> I'm thinking of having `org.apache.oozie.fluentjob.api.v1.generated` as a 
> root package for all 1.0 XSDs listed in `xjb/bindings.xml`, and used 
> elsewhere.
> 
> What do you think?

Extending `DG_FluentJobAPI.twiki` by a new section `How to extend based on 
schema changes`, and linking from `DG_CustomActionExecutor.twiki`.


- András


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


On May 14, 2018, 8:36 p.m., András Piros wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64029/
> ---
> 
> (Updated May 14, 2018, 8:36 p.m.)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Cseh, and Robert Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2339 Provide an API for writing jobs based on the XSD schemas
> 
> 
> Diffs
> -
> 
>   client/pom.xml 795a92d4af1a6d96603c99506cd70e8cf8e2c347 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 
> 4abc7502c0c9d8b59ded2baaed30c407ad073008 
>   client/src/main/java/org/apache/oozie/client/ApiJarFactory.java 
> PRE-CREATION 
>   client/src/main/java/org/apache/oozie/client/ApiJarLoader.java PRE-CREATION 
>   client/src/main/java/org/apache/oozie/client/OozieClient.java 
> 4c8175628ba5ee346d97ad984532662032b88acc 
>   core/pom.xml 45880a619e70a1643f4eb5ceeb61abb2090551f1 
>   core/src/main/java/org/apache/oozie/BaseLocalOozieClient.java 
> 38fb006980c0acb582b4f91175be1ced8a1afa79 
>   core/src/main/java/org/apache/oozie/local/LocalOozie.java 
> 9ab646cd53223d903e387eb92aa103a7b6577d0f 
>   core/src/main/java/org/apache/oozie/servlet/BaseJobServlet.java 
> e1bd3cf61aabfa4311881b2944fc9f10ffe9145d 
>   core/src/main/java/org/apache/oozie/servlet/BaseJobsServlet.java 
> d4b08711223356c8d4f58a3391b6b87efa0a2b73 
>   core/src/main/java/org/apache/oozie/servlet/ServletUtilities.java 
> 3eb32d50d07687c136fcc0e467a055bdc1e7ec60 
>   core/src/main/java/org/apache/oozie/servlet/V0JobsServlet.java 
> 1d800949cbff34a95f2ae111364eb8cbc6a5f5fb 
>   

[jira] [Updated] (OOZIE-3256) refactor OozieCLI class

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3256:

Attachment: OOZIE-3256.00.patch

> refactor OozieCLI class
> ---
>
> Key: OOZIE-3256
> URL: https://issues.apache.org/jira/browse/OOZIE-3256
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 5.0.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: OOZIE-3256.00.patch
>
>




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

[jira] [Commented] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3160:
-

Looks like we have to do the following if we have to avoid busy waiting:
1. Have a {{ScheduledThreadPoolExecutor}} per priority level
2. We submit tasks in a wrapped {{Callable}} to these executors depending on 
priority
3. There's a separate thread for each priority where we call {{queue.take()}}. 
In our case, the queue will be a {{DelayWorkQueue}} which blocks {{take()}} 
until an item expires.

#3 looks like a limitation, however we only have 3 priority levels in Oozie, so 
it isn't really a problem.

Since we have to deal with priorities, we need a common {{ExecutorService}} 
where the queue is not an ordinary blocking queue, but a 
{{PriorityBlockingQueue}} (this comes with the JDK). This ensures that 
submitted tasks are ordered based on their priority. So higher priority tasks 
will run before lower ones. 

Problem is, there is no anti-starvation logic in {{PriorityBlockingQueue}}. To 
avoid this, we have to track the added elements in a separate data structure. 
This could be a set of priority queues, which we peek at certain points. If a 
certain item reached the anti-starvation threshold, we do a promotion inside 
the main {{PriorityBlockingQueue}} (remove then re-add it with a higher 
priority).

Whoah, this is a big pain. There must be an easier solution to this... I know I 
do overcomplicate simple things from time to time. 

[~gezapeti], [~andras.piros], [~rkanter] any thoughts? 

> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: 11.png, 22.png, 
> OOZIE-3160-POC01.patch
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-3178:
---

The long lines are in the shell script and it's acceptable there.
+1


> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Commented] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2211:
--

PreCommit-OOZIE-Build started


> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Commented] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3160:
-

OK, this is not going to be as easy as I thought. Actually you can only take 
out elements after they expired. So a blocking {{take()}} should be woken up 
properly. 

> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: 11.png, 22.png, 
> OOZIE-3160-POC01.patch
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

Failed: OOZIE-3178 PreCommit Build #570

[Apache Jenkins Server]

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

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


Testing JIRA OOZIE-3178

Cleaning local git workspace



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


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  32150 0  100  3215  0   3897 --:--:-- --:--:-- --:--:--  
3896{"self":"https://issues.apache.org/jira/rest/api/2/issue/13136855/comment/16489454","id":"16489454","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3178:
--


Testing JIRA OOZIE-3178

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 2 line(s) longer than 132 
characters
.{color:green}+1{color} the patch adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2134
.{color:orange}Tests failed at first run:{color}
TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


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


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

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



> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Created] (OOZIE-3256) refactor OozieCLI class

[Artem Ervits (JIRA)]

Artem Ervits created OOZIE-3256:
---

 Summary: refactor OozieCLI class
 Key: OOZIE-3256
 URL: https://issues.apache.org/jira/browse/OOZIE-3256
 Project: Oozie
  Issue Type: Improvement
Affects Versions: 5.0.0
Reporter: Artem Ervits
Assignee: Artem Ervits






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

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Attachment: OOZIE-2211-00.patch

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Fix Version/s: 5.1.0

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Assigned] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-2211:
---

Assignee: Artem Ervits

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Resolved] (OOZIE-2002) Removed un-used property

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2002.
-
Resolution: Implemented

> Removed un-used property
> 
>
> Key: OOZIE-2002
> URL: https://issues.apache.org/jira/browse/OOZIE-2002
> Project: Oozie
>  Issue Type: Bug
>Reporter: Shwetha G S
>Priority: Trivial
>
> Looks like the following property is not used, but is available in 
> oozie-default and oozie-site
> {noformat}
>
> use.system.libpath.for.mapreduce.and.pig.jobs
> false
> 
> If set to true, submissions of MapReduce and Pig jobs will include
> automatically the system library path, thus not requiring users to
> specify where the Pig JAR files are. Instead, the ones from the 
> system
> library path are used.
> 
> 
> {noformat}



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

[jira] [Commented] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3160:
--


Testing JIRA OOZIE-3160

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: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:red}-1{color} There are [1] new bugs found below threshold in total that 
must be fixed.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:red}-1{color} There are [1] new bugs found below threshold in [core] 
that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
core/findbugs-new.html
. The most important FindBugs errors are:
. At PriorityDelayQueue.java:[line 655]: Exceptional return value of 
java.util.concurrent.locks.Condition.await(long, TimeUnit) ignored in 
org.apache.oozie.util.PriorityDelayQueue.poll(long, TimeUnit)
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2134
.Tests failed: 17
.Tests errors: 3

.The patch failed the following testcases:

testQueueUniquenessWithSameKeyInComposite(org.apache.oozie.service.TestCallableQueueService)
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)
testSerialConcurrencyLimit(org.apache.oozie.service.TestCallableQueueService)
testDelayedQueuing(org.apache.oozie.service.TestCallableQueueService)
testConcurrency(org.apache.oozie.service.TestCallableQueueService)
testCoordStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService)
testMultipleCoordSubmit(org.apache.oozie.command.bundle.TestBundleSubmitXCommand)
testEarlyCallbackTimeout(org.apache.oozie.command.wf.TestCompletedActionXCommand)
testEarlyCallbackTransitionToRunning(org.apache.oozie.command.wf.TestCompletedActionXCommand)
testBundleSuspend2(org.apache.oozie.command.bundle.TestBundleJobSuspendXCommand)
testStartTransient(org.apache.oozie.command.wf.TestActionErrors)
testEndTransient(org.apache.oozie.command.wf.TestActionErrors)
testDoneFlagCreation(org.apache.oozie.TestCoordinatorEngine)
testEmptyDoneFlag(org.apache.oozie.TestCoordinatorEngine)
testCustomDoneFlag(org.apache.oozie.TestCoordinatorEngine)
testDoneFlag(org.apache.oozie.TestCoordinatorEngine)
testUserRetryPolicy(org.apache.oozie.command.wf.TestActionUserRetry)

.Tests failing with errors:
testInfoWithBundle(org.apache.oozie.action.hadoop.TestOozieJobInfo)
testReRunRefresh(org.apache.oozie.command.coord.TestCoordUpdateXCommand)
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)

.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
TestPastActionsTimeOut#testEngine
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:red}-1 DISTRO{color}
.{color:red}-1{color} 

Failed: OOZIE-3160 PreCommit Build #569

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.65 MB...]

+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
-1 There are [1] new bugs found below threshold in total that must be fixed.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 -1 There are [1] new bugs found below threshold in [core] that must be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
core/findbugs-new.html
 The most important FindBugs errors are:
 At PriorityDelayQueue.java:[line 655]: Exceptional return value of 
java.util.concurrent.locks.Condition.await(long, TimeUnit) ignored in 
org.apache.oozie.util.PriorityDelayQueue.poll(long, TimeUnit)
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2134
Tests failed: 17
Tests errors: 3

The patch failed the following testcases:

testQueueUniquenessWithSameKeyInComposite(org.apache.oozie.service.TestCallableQueueService)
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)
testSerialConcurrencyLimit(org.apache.oozie.service.TestCallableQueueService)
testDelayedQueuing(org.apache.oozie.service.TestCallableQueueService)
testConcurrency(org.apache.oozie.service.TestCallableQueueService)
testCoordStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService)
testMultipleCoordSubmit(org.apache.oozie.command.bundle.TestBundleSubmitXCommand)
testEarlyCallbackTimeout(org.apache.oozie.command.wf.TestCompletedActionXCommand)
testEarlyCallbackTransitionToRunning(org.apache.oozie.command.wf.TestCompletedActionXCommand)
testBundleSuspend2(org.apache.oozie.command.bundle.TestBundleJobSuspendXCommand)
testStartTransient(org.apache.oozie.command.wf.TestActionErrors)
testEndTransient(org.apache.oozie.command.wf.TestActionErrors)
testDoneFlagCreation(org.apache.oozie.TestCoordinatorEngine)
testEmptyDoneFlag(org.apache.oozie.TestCoordinatorEngine)
testCustomDoneFlag(org.apache.oozie.TestCoordinatorEngine)
testDoneFlag(org.apache.oozie.TestCoordinatorEngine)
testUserRetryPolicy(org.apache.oozie.command.wf.TestActionUserRetry)

Tests failing with errors:
testInfoWithBundle(org.apache.oozie.action.hadoop.TestOozieJobInfo)
testReRunRefresh(org.apache.oozie.command.coord.TestCoordUpdateXCommand)
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)

Tests failed at first run:
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
TestPastActionsTimeOut#testEngine
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
-1 DISTRO
-1 distro tarball fails with the patch


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


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  51120 0  100  5112  0   6379 --:--:-- --:--:-- --:--:--  
6374{"self":"https://issues.apache.org/jira/rest/api/2/issue/13130774/comment/16489404","id":"16489404","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot 

[jira] [Commented] (OOZIE-3255) Oozie cannot start with Hadoop 3.1.0

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3255:
-

[~andras.piros] I used
{code:java}
mv clean install -DskipTests -Dhadoop.version=3.1.0 -Puber
./bin/mkdistro.sh -DskipTests -Dhadoop.version=3.1.0 -Puber {code}

> Oozie cannot start with Hadoop 3.1.0
> 
>
> Key: OOZIE-3255
> URL: https://issues.apache.org/jira/browse/OOZIE-3255
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
> Environment: Apache Maven 3.5.3 
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
> Maven home: /opt/maven/apache-maven-3.5.3
> Java version: 1.8.0_171, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.171-8.b10.el7_5.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-862.2.3.el7.x86_64", arch: "amd64", 
> family: "unix"
>Reporter: Artem Ervits
>Priority: Major
>
> {code:java}
> bin/oozied.sh start{code}
> {code:java}
> Setting up oozie DB
> Validate DB Connection
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/util/ReflectionUtils
> at org.apache.oozie.service.Services.setServiceInternal(Services.java:377)
> at org.apache.oozie.service.Services.(Services.java:111)
> at org.apache.oozie.tools.OozieDBCLI.getJdbcConf(OozieDBCLI.java:169)
> at org.apache.oozie.tools.OozieDBCLI.createConnection(OozieDBCLI.java:918)
> at org.apache.oozie.tools.OozieDBCLI.validateConnection(OozieDBCLI.java:926)
> at org.apache.oozie.tools.OozieDBCLI.createDB(OozieDBCLI.java:188)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:131)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:79)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.hadoop.util.ReflectionUtils
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 8 more{code}
> {code:java}
> /opt/oozie/oozie-5.1.0-SNAPSHOT/bin/oozie-setup.sh sharelib create -fs 
> hdfs://hadoop.example.com:8020 -locallib ~/share/{code}
> {code:java}
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/fs/Path
> at org.apache.oozie.tools.OozieSharelibCLI.run(OozieSharelibCLI.java:153)
> at org.apache.oozie.tools.OozieSharelibCLI.main(OozieSharelibCLI.java:67)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.fs.Path
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 2 more{code}



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2105:
--

PreCommit-OOZIE-Build started


> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Updated] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2105:

Fix Version/s: 5.1.0

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Assigned] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-2105:
---

Assignee: Artem Ervits  (was: Mohammad Kamrul Islam)

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Updated] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2105:

Attachment: OOZIE-2105-02.patch

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Resolved] (OOZIE-2336) Few testcases of TestStatusTransitService are failing

[Peter Bacsko (JIRA)]

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

Peter Bacsko resolved OOZIE-2336.
-
Resolution: Duplicate

Closing this as duplicate. There are more recent tickets under OOZIE-3111.

> Few testcases of TestStatusTransitService are failing
> -
>
> Key: OOZIE-2336
> URL: https://issues.apache.org/jira/browse/OOZIE-2336
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Purshotam Shah
>Priority: Major
>
> test-C@1] Released lock for [000-150817195742795-oozie-jenk-B] in 
> [bundle_status_transit]
> 19:57:43,472  INFO StatusTransitService$StatusTransitRunnable:520 - USER[-] 
> GROUP[-] TOKEN[] APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Released lock for 
> [org.apache.oozie.service.StatusTransitService]
> 19:57:43,474  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting up to [3,000] msec
> 19:57:43,474  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting up to [3,000] msec
> 19:57:44,477  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting up to [1,999] msec
> 19:57:46,478  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting timed out after 
> [1,000] msec
> {color:red}
> 19:57:46,480  INFO StatusTransitService$StatusTransitRunnable:520 - USER[-] 
> GROUP[-] TOKEN[] APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] This StatusTransitService 
> instance will not run since there is already an instance running
> {color}
> 19:57:46,484  INFO Services:520 - USER[-] GROUP[-] TOKEN[] APP[-] 
> JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Shutdown



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3178:
--

PreCommit-OOZIE-Build started


> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3178:
-

[~andras.piros] & [~gezapeti] please review the latest patch, I added a new 
function to look for javadoc errors.

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Comment Edited] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-3178 at 5/24/18 3:54 PM:
--

[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind.

 

also, addressing a minor issue in OOZIE-2363


was (Author: dbist13):
[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

 

also, addressing a minor issue in OOZIE-2363

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Updated] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3178:

Attachment: OOZIE-3178-02.patch

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

Re: Review Request 67284: OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko via Review Board]

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

(Updated máj. 24, 2018, 3:29 du)


Review request for oozie, András Piros, Peter Cseh, and Robert Kanter.


Repository: oozie-git


Description (updated)
---

We must get rid of the Thread.sleep() calls inside PriorityDelayQueue


Diffs
-

  core/src/main/java/org/apache/oozie/util/PriorityDelayQueue.java 75c20698c 


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


Testing
---


Thanks,

Peter Bacsko

[jira] [Commented] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3160:
-

Code review: https://reviews.apache.org/r/67284/

Note that the tests must be enhanced too - so in the current state it's more 
like a POC.

> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: 11.png, 22.png, 
> OOZIE-3160-POC01.patch
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Commented] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3160:
--

PreCommit-OOZIE-Build started


> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: 11.png, 22.png, 
> OOZIE-3160-POC01.patch
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

Review Request 67284: OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko via Review Board]

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

Review request for oozie, András Piros, Peter Cseh, and Robert Kanter.


Repository: oozie-git


Description
---

We must get rid of the Thread.sleep() calls inside PriorityDelayQueue.


Diffs
-

  core/src/main/java/org/apache/oozie/util/PriorityDelayQueue.java 75c20698c 


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


Testing
---


Thanks,

Peter Bacsko

[jira] [Commented] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3160:
-

[~j782070772] if you're still following this ticket, I'd appreciate if you 
could try out the patch with the same settings.

Anyway, I implemented some big changes inside {{PriorityDelayQueue}}. Unit 
tests for the class passed on my machine, but we need to see a complete build 
first.

> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: 11.png, 22.png, 
> OOZIE-3160-POC01.patch
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Assigned] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko (JIRA)]

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

Peter Bacsko reassigned OOZIE-3160:
---

Assignee: Peter Bacsko  (was: Andras Piros)

> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: 11.png, 22.png, 
> OOZIE-3160-POC01.patch
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Updated] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-3160:

Attachment: OOZIE-3160-POC01.patch

> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Andras Piros
>Priority: Major
> Attachments: 11.png, 22.png, 
> OOZIE-3160-POC01.patch
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Comment Edited] (OOZIE-2301) JA017: Could not lookup launched hadoop Job ID

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-2301 at 5/24/18 2:46 PM:
--

[~mobinranjbar] I apologize, should've explained my motives. Apache Jira is not 
a place for individual issue resolution, this is clearly a message from Oozie 
with a valid Oozie error ID. A better place for questions like that would be on 
the Hue mailing list, Oozie mailing list, a vendor forum or StackOverflow where 
you clearly already have a question open:

[https://stackoverflow.com/questions/31379961/ja017-could-not-lookup-launched-hadoop-job-id]

Here's one possible solution for your problem: 
[https://community.hortonworks.com/content/supportkb/148594/errorja017-could-not-lookup-launched-hadoop-job-id.html]

Jira is for actual bugs, enhancements and new features to a project.


was (Author: dbist13):
[~mobinranjbar] I apologize, should've explained my motives. Apache Jira is not 
a place for individual issue resolution, this is clearly a message from Oozie 
with a valid Oozie error ID. A better place for questions like that would be on 
the Hue mailing list, Oozie mailing list, a vendor forum or StackOverflow where 
you clearly already have a question open:

[https://stackoverflow.com/questions/31379961/ja017-could-not-lookup-launched-hadoop-job-id]

Here's one possible solution for your problem: 
https://community.hortonworks.com/content/supportkb/148594/errorja017-could-not-lookup-launched-hadoop-job-id.html

 

> JA017: Could not lookup launched hadoop Job ID 
> ---
>
> Key: OOZIE-2301
> URL: https://issues.apache.org/jira/browse/OOZIE-2301
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mobin Ranjbar
>Priority: Major
>
> How can I solve this problem when I submit a mapreduce job in Oozie Editor in 
> Hue? :
> JA017: Could not lookup launched hadoop Job ID [job_local152843681_0009] 
> which was associated with action 
> [009-150711083342968-oozie-root-W@mapreduce-f660]. Failing this action!



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-3178:
---

I've just tried it and calling
{quote}
>> [37] 16:23 : oozie (master) :: ./bin/mkdistro.sh -Papache-release -DskipTests
{quote}
reproduces the issue we were having during the last release.

Also [~dbist13], I'd really appreciate it if you'd change the pre-commit hook 
as well in a way to prevent these errors in the future.

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3178:
--


Testing JIRA OOZIE-3178

Cleaning local git workspace



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




> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

Failed: OOZIE-3178 PreCommit Build #568

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 761.69 KB...]
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.996 s]
[INFO] Apache Oozie Client  SUCCESS [ 20.264 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 14.974 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  6.855 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  6.469 s]
[INFO] Apache Oozie Core .. SUCCESS [01:32 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.872 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  9.929 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [ 10.509 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  9.437 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  7.006 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 11.124 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 11.690 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.021 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.376 s]
[INFO] Apache Oozie WebApp  SUCCESS [  9.710 s]
[INFO] Apache Oozie Tools . SUCCESS [ 16.637 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.724 s]
[INFO] Apache Oozie Server  SUCCESS [ 12.190 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.475 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.959 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 04:22 min
[INFO] Finished at: 2018-05-24T14:19:14Z
[INFO] Final Memory: 170M/1852M
[INFO] 
[TRACE] FindBugs output in HEAD verified and saved
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO

Applying patch

Checking patch 
core/src/main/java/org/apache/oozie/compression/CodecFactory.java...
Checking patch pom.xml...
Checking patch 
tools/src/main/java/org/apache/oozie/tools/OozieDBExportCLI.java...
error: while searching for:

/**
 * This class provides the following functionality:
 * 
 * 
 * Exports the data from the Oozie database to a specified target zip 
file
 * This class uses the current oozie configuration in oozie-site.xml
 * 
 * 
 */

public class OozieDBExportCLI {

error: patch failed: 
tools/src/main/java/org/apache/oozie/tools/OozieDBExportCLI.java:41
error: tools/src/main/java/org/apache/oozie/tools/OozieDBExportCLI.java: patch 
does not apply
Checking patch 
tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java...
error: while searching for:

/**
 * This class provides the following functionality:
 * 
 *  
 *  imports the data from json files created by {@link 
OozieDBExportCLI} the specified target zip file
 *  this class uses the current Oozie configuration in 
{oozie-site.xml}
 *  
 *  
 * 
 */
public class OozieDBImportCLI {
private static final String[] HELP_INFO = {

error: patch failed: 
tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java:79
error: tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java: patch 
does not apply
fatal: git diff header lacks filename information when removing 1 leading 
pathname component (line 18)
Patch failed to apply to head of branch

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  18860  1687  100   199   2237263 --:--:-- --:--:-- --:--:--  2237

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3178:
-

[~dbist13] thanks for working so hard on the issue!

An example of calling {{test-patch}} locally:
{noformat}
bin/test-patch --patch=/path/to/OOZIE-3178-01.patch --dirty-scm --tasks=JAVADOC 
-Papache-release --verbose
{noformat}

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-3178:
--

PreCommit-OOZIE-Build started


> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Updated] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3178:

Attachment: OOZIE-3178-01.patch

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Comment Edited] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-3178 at 5/24/18 1:59 PM:
--

[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

 

also, addressing a minor issue in OOZIE-2363


was (Author: dbist13):
[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Resolved] (OOZIE-2363) the redundant comma in CodecFactory.java

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2363.
-
Resolution: Fixed

since this is a minor fix, I will address it as part of another issue.

> the redundant comma in CodecFactory.java
> 
>
> Key: OOZIE-2363
> URL: https://issues.apache.org/jira/browse/OOZIE-2363
> Project: Oozie
>  Issue Type: Bug
>Reporter: sunmeng
>Priority: Major
>




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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3178:
-

[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Updated] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting

[Peter Bacsko (JIRA)]

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

Peter Bacsko updated OOZIE-3160:

Summary: PriorityDelayQueue put()/take() can cause significant CPU load due 
to busy waiting  (was: oozie high cpu usage problem)

> PriorityDelayQueue put()/take() can cause significant CPU load due to busy 
> waiting
> --
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Andras Piros
>Priority: Major
> Attachments: 11.png, 22.png
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Commented] (OOZIE-3160) oozie high cpu usage problem

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3160:
-

I'm linking OOZIE-1855 as a related JIRA - the tests need significant 
improvements too.

> oozie high cpu usage problem
> 
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Andras Piros
>Priority: Major
> Attachments: 11.png, 22.png
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Commented] (OOZIE-3160) oozie high cpu usage problem

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-3160:
-

It's not just {{take()}}, {{put()}} does the same thing:

{noformat}
@Override
public void put(QueueElement e) throws InterruptedException {
while (!offer(e, true)) {
Thread.sleep(10);
}
}
{noformat}

These kinds of constructs should be avoided at all costs. Basically we have two 
options here:
1) Use a single {{Condition}} object for all priority levels - we already have 
a {{ReentrantLock}} for the whole queue
2) Use {{Condition}} objects on a per priority basis

#1 is much simpler and already solves this problem, so I'd go for that.



> oozie high cpu usage problem
> 
>
> Key: OOZIE-3160
> URL: https://issues.apache.org/jira/browse/OOZIE-3160
> Project: Oozie
>  Issue Type: Bug
>  Components: core
> Environment: all platforms
>Reporter: jj
>Assignee: Andras Piros
>Priority: Major
> Attachments: 11.png, 22.png
>
>
> oozie process always  consume  high cpu. in my mechine,around 10%. 
> I check the source code，find take() method in PriorityDelayQueue class。
> code:
> {code:java}
> public QueueElement take() throws InterruptedException {
> QueueElement e = poll();
> while (e == null) {
> Thread.sleep(10);
> e = poll();
> }
> return e;
> }
> {code}
> i think it's the reason of this problem. it's keep while, not await.  



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

[jira] [Assigned] (OOZIE-3244) Flaky test TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator

[Peter Bacsko (JIRA)]

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

Peter Bacsko reassigned OOZIE-3244:
---

Assignee: Peter Bacsko

> Flaky test 
> TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator
> 
>
> Key: OOZIE-3244
> URL: https://issues.apache.org/jira/browse/OOZIE-3244
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> The testcase 
> TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator 
> occasionally fails:
> {noformat}
> junit.framework.AssertionFailedError: expected: but was:
>   at 
> org.apache.oozie.command.bundle.TestBundleChangeXCommand.testBundlePauseExtendMaterializesCoordinator(TestBundleChangeXCommand.java:244)
> {noformat}



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

[jira] [Resolved] (OOZIE-3253) Flaky test TestStatusTransitService#testCoordStatusTransitWithLock

[Peter Bacsko (JIRA)]

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

Peter Bacsko resolved OOZIE-3253.
-
   Resolution: Fixed
Fix Version/s: 5.1.0

Committed togerther with OOZIE-3238

> Flaky test TestStatusTransitService#testCoordStatusTransitWithLock
> --
>
> Key: OOZIE-3253
> URL: https://issues.apache.org/jira/browse/OOZIE-3253
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
>




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

[jira] [Updated] (OOZIE-3238) Flaky test TestStatusTransitService#testBundleStatusTransitWithLock

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3238:

Component/s: tests

> Flaky test TestStatusTransitService#testBundleStatusTransitWithLock
> ---
>
> Key: OOZIE-3238
> URL: https://issues.apache.org/jira/browse/OOZIE-3238
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
> Attachments: OOZIE-3238-001.patch
>
>
> TestStatusTransitService#testBundleStatusTransitWithLock occasionally fails 
> with the following message:
> {noformat}
> junit.framework.AssertionFailedError: expected: but 
> was:
>   at 
> org.apache.oozie.service.TestStatusTransitService.testBundleStatusTransitWithLock(TestStatusTransitService.java:1593)
> {noformat}



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

[jira] [Commented] (OOZIE-3185) Upgrade org.apache.derby to 10.11.1.1

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3185:
-

Thanks for the contribution [~PandaMonkey]! +1

> Upgrade org.apache.derby to 10.11.1.1
> -
>
> Key: OOZIE-3185
> URL: https://issues.apache.org/jira/browse/OOZIE-3185
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: PandaMonkey
>Assignee: PandaMonkey
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: 0001-Fix1.patch, oozie.txt
>
>
> Hi, by analyzing oozie-master\core\pom.xml, I found that there are two 
> versions of org.apache.derby:derby. Their introduced paths are:
> 1. 
> org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile
> 2. 
> org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile
> Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by 
> org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct 
> dependency. By further analyzing the source code, *we found they have too 
> many different features*.
> Also, I found that you have already gave derby a exclusion tag when 
> transitively introducing derby by hive-beeline to avoid dependency conflict.
> So it would be nice to keep the consistency of library version for the 
> project long-term health, maybe *update org.apache.derby:derby from 10.10.1.1 
> to 10.11.1.1, or exclude derby from hive-exec* is a good choice. Hope this 
> can help you. Thanks.



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

[jira] [Updated] (OOZIE-3185) Upgrade org.apache.derby to 10.11.1.1

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3185:

Summary: Upgrade org.apache.derby to 10.11.1.1  (was: Conflicting JARs 
org.apache.derby exist in Oozie)

> Upgrade org.apache.derby to 10.11.1.1
> -
>
> Key: OOZIE-3185
> URL: https://issues.apache.org/jira/browse/OOZIE-3185
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: PandaMonkey
>Assignee: PandaMonkey
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: 0001-Fix1.patch, oozie.txt
>
>
> Hi, by analyzing oozie-master\core\pom.xml, I found that there are two 
> versions of org.apache.derby:derby. Their introduced paths are:
> 1. 
> org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile
> 2. 
> org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile
> Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by 
> org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct 
> dependency. By further analyzing the source code, *we found they have too 
> many different features*.
> Also, I found that you have already gave derby a exclusion tag when 
> transitively introducing derby by hive-beeline to avoid dependency conflict.
> So it would be nice to keep the consistency of library version for the 
> project long-term health, maybe *update org.apache.derby:derby from 10.10.1.1 
> to 10.11.1.1, or exclude derby from hive-exec* is a good choice. Hope this 
> can help you. Thanks.



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

[jira] [Resolved] (OOZIE-1745) can't start oozie : java.lang.ClassNotFoundException : org.apache.hadoop.util.PlatformName

[Andras Piros (JIRA)]

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

Andras Piros resolved OOZIE-1745.
-
Resolution: Cannot Reproduce

[~dbist13] thanks, closing as Cannot reproduce.

> can't start oozie : java.lang.ClassNotFoundException : 
> org.apache.hadoop.util.PlatformName
> --
>
> Key: OOZIE-1745
> URL: https://issues.apache.org/jira/browse/OOZIE-1745
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk
> Environment: ubuntu 64 
>Reporter: lulu prat
>Priority: Critical
>
> i build oozie and do the tuto 
> :http://www.linuxpedia.fr/doku.php/expert/systeme_chiffre_luks_pam_cryptsetup
> but when i run : bin/oozied.sh run 
> i get the error:
> ERROR: Oozie could not be started
> REASON: java.lang.NoClassDefFoundError: org/apache/hadoop/util/PlatformName
> Stacktrace:
> -
> java.lang.NoClassDefFoundError: org/apache/hadoop/util/PlatformName
>   at 
> org.apache.hadoop.security.UserGroupInformation.getOSLoginModuleName(UserGroupInformation.java:337)
>   at 
> org.apache.hadoop.security.UserGroupInformation.(UserGroupInformation.java:382)
>   at 
> org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:132)
>   at 
> org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:98)
>   at 
> org.apache.oozie.service.Services.setServiceInternal(Services.java:368)
>   at org.apache.oozie.service.Services.setService(Services.java:354)
>   at org.apache.oozie.service.Services.loadServices(Services.java:287)
>   at org.apache.oozie.service.Services.init(Services.java:208)
>   at 
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:45)
>   at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
>   at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
>   at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
>   at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
>   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
>   at 
> org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
>   at 
> org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
>   at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
>   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
>   at 
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
>   at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
>   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
>   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
>   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
>   at 
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
>   at 
> org.apache.catalina.core.StandardService.start(StandardService.java:525)
>   at 
> org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
>   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:622)
>   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
>   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.hadoop.util.PlatformName
>   at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
>   at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
>   ... 33 more



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

[jira] [Resolved] (OOZIE-2217) Oozie-4.1.0 Installation failed during oozie-client install

[Andras Piros (JIRA)]

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

Andras Piros resolved OOZIE-2217.
-
Resolution: Won't Fix

[~dbist13] [~vikramj] closing as Won't fix because {{4.1.0}} has been already 
passed by multiple minors (actual one is {{4.3.1}}), and a major ({{5.0.0}}).

> Oozie-4.1.0 Installation failed during oozie-client install
> ---
>
> Key: OOZIE-2217
> URL: https://issues.apache.org/jira/browse/OOZIE-2217
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 4.0.1
> Environment: CentOS 6 with Java-1.8 version
>Reporter: Vikram Janarthanan
>Priority: Critical
>  Labels: maven
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.7:javadoc (default) on 
> project oozie-client: An error has occurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:88:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:91:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:148:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:172:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:174:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:199:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:202:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:265:
>  error: bad use of '>'
> [ERROR] * null -> KerberosAuthenticator
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:266:
>  error: bad use of '>'
> [ERROR] * SIMPLE -> PseudoAuthenticator
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:267:
>  error: bad use of '>'
> [ERROR] * KERBEROS -> KerberosAuthenticator
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:270:
>  error: exception not thrown: org.apache.oozie.client.OozieClientException
> [ERROR] * @throws OozieClientException
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:270:
>  warning: no description for @throws
> [ERROR] * @throws OozieClientException
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:174:
>  warning: no @throws for java.io.IOException
> [ERROR] public String submitPig(Properties conf, String pigScriptFile, 
> String[] pigArgs) throws IOException, OozieClientException {
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:187:
>  warning: no @param for jobType
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String jobType)
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:187:
>  warning: no @throws for java.io.IOException
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String jobType)
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:202:
>  warning: no @param for jobType
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String[] params, String jobType)
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:202:
>  warning: no @throws for java.io.IOException
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String[] params, String jobType)
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:315:
>  error: unknown tag: file
> [ERROR] * The equivalent to  tag in oozie's workflow xml.
> [ERROR] ^
> [ERROR] 
> 

[jira] [Commented] (OOZIE-2364) Remove deprecated SLAEventBean and related code

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2364:
-

[~satishsaley] can you please rebase on top of latest {{master}}?

> Remove deprecated SLAEventBean and related code
> ---
>
> Key: OOZIE-2364
> URL: https://issues.apache.org/jira/browse/OOZIE-2364
> Project: Oozie
>  Issue Type: Task
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
>Priority: Major
>  Labels: newbie
> Fix For: 5.1.0
>
> Attachments: OOZIE-2364-1.patch, OOZIE-2364-2.patch, 
> OOZIE-2364-3.patch, OOZIE-2364-4.patch
>
>
>   With new SLAService feature which uses different tables, the old SLA_EVENTS 
> table is not used anymore. Need to remove all code related to it and drop 
> that table as well.



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

[jira] [Resolved] (OOZIE-1874) ./oozied.sh: line 104: /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/bin/catalina.sh: No such file or directory

[Andras Piros (JIRA)]

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

Andras Piros resolved OOZIE-1874.
-
Resolution: Won't Fix

[~dbist13] [~adarshahota] closing as not relevant w/ {{5.0.0}} anymore.

> ./oozied.sh: line 104: 
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/bin/catalina.sh: 
> No such file or directory
> 
>
> Key: OOZIE-1874
> URL: https://issues.apache.org/jira/browse/OOZIE-1874
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: ubuntu 12.04 LTS
>Reporter: ADARSHA HOTA
>Priority: Blocker
>
> At the time of installation process of Oozie-4.0.1 on Hadoop-2.3.0 , while 
> invoking "./oozied.sh prepare-war" command below error is coming.
> Setting OOZIE_HOME:  /usr/local/hadoop/oozie-4.0.1/distro/src/main
> Setting OOZIE_CONFIG:
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/conf
> Setting OOZIE_CONFIG_FILE:   oozie-site.xml
> Setting OOZIE_DATA:  
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/data
> Setting OOZIE_LOG:   
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/logs
> Setting OOZIE_LOG4J_FILE:oozie-log4j.properties
> Setting OOZIE_LOG4J_RELOAD:  10
> Setting OOZIE_HTTP_HOSTNAME: localhost
> Setting OOZIE_HTTP_PORT: 11000
> Setting OOZIE_ADMIN_PORT: 11001
> Setting OOZIE_HTTPS_PORT: 11443
> Setting OOZIE_BASE_URL:  http://localhost:11000/oozie
> Setting CATALINA_BASE:   
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server
> Setting OOZIE_HTTPS_KEYSTORE_FILE: /home/user/.keystore
> Setting OOZIE_HTTPS_KEYSTORE_PASS: password
> Setting CATALINA_OUT:
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/logs/catalina.out
> Setting CATALINA_PID:
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/temp/oozie.pid
> ./oozied.sh: line 104: 
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/bin/catalina.sh: 
> No such file or directory



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3178:
-

Thanks for the contribution [~dbist13]!

Would you mind also taking care of 
[*{{bin/test-patch-09-javadoc}}*|https://github.com/apache/oozie/blob/master/bin/test-patch-09-javadoc#L99-L104]
 to run {{mvn javadoc:javadoc}} to also warn on such errors to prevent the 
issue from reoccurring? Thanks!

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Updated] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3178:

Component/s: build

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Commented] (OOZIE-2883) ProxyUserService: invalid configuration error message is misleading

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2883:
-

Thanks for the contribution [~yangfang]! +1

> ProxyUserService: invalid configuration error message is misleading
> ---
>
> Key: OOZIE-2883
> URL: https://issues.apache.org/jira/browse/OOZIE-2883
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: yangfang
>Assignee: yangfang
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2883.001.patch
>
>
> When I started oozie server without the configuration 
> "oozie.service.ProxyUserService.proxyuser.#USER#.groups", I got the error 
> "E0551: Missing 
> [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
>  property" ,because I  don't have this configuration, but the exception tells 
> us 
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups",
>  
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups"
>  does not exist at all. The correct configuration is 
> "oozie.service.ProxyUserService.proxyuser.mr.groups".



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

[jira] [Updated] (OOZIE-2883) ProxyUserService: invalid configuration error message is misleading

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2883:

Summary: ProxyUserService: invalid configuration error message is 
misleading  (was: ProxyUserService: missing configuration error message is 
misleading)

> ProxyUserService: invalid configuration error message is misleading
> ---
>
> Key: OOZIE-2883
> URL: https://issues.apache.org/jira/browse/OOZIE-2883
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: yangfang
>Assignee: yangfang
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2883.001.patch
>
>
> When I started oozie server without the configuration 
> "oozie.service.ProxyUserService.proxyuser.#USER#.groups", I got the error 
> "E0551: Missing 
> [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
>  property" ,because I  don't have this configuration, but the exception tells 
> us 
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups",
>  
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups"
>  does not exist at all. The correct configuration is 
> "oozie.service.ProxyUserService.proxyuser.mr.groups".



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

[jira] [Assigned] (OOZIE-2883) ProxyUserService: missing configuration error message is misleading

[Andras Piros (JIRA)]

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

Andras Piros reassigned OOZIE-2883:
---

Assignee: yangfang

> ProxyUserService: missing configuration error message is misleading
> ---
>
> Key: OOZIE-2883
> URL: https://issues.apache.org/jira/browse/OOZIE-2883
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: yangfang
>Assignee: yangfang
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2883.001.patch
>
>
> When I started oozie server without the configuration 
> "oozie.service.ProxyUserService.proxyuser.#USER#.groups", I got the error 
> "E0551: Missing 
> [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
>  property" ,because I  don't have this configuration, but the exception tells 
> us 
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups",
>  
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups"
>  does not exist at all. The correct configuration is 
> "oozie.service.ProxyUserService.proxyuser.mr.groups".



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

[jira] [Updated] (OOZIE-2883) ProxyUserService: missing configuration error message is misleading

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-2883:

Summary: ProxyUserService: missing configuration error message is 
misleading  (was: OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property")

> ProxyUserService: missing configuration error message is misleading
> ---
>
> Key: OOZIE-2883
> URL: https://issues.apache.org/jira/browse/OOZIE-2883
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: yangfang
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2883.001.patch
>
>
> When I started oozie server without the configuration 
> "oozie.service.ProxyUserService.proxyuser.#USER#.groups", I got the error 
> "E0551: Missing 
> [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
>  property" ,because I  don't have this configuration, but the exception tells 
> us 
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups",
>  
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups"
>  does not exist at all. The correct configuration is 
> "oozie.service.ProxyUserService.proxyuser.mr.groups".



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2105:
-

[~dbist13] it's [*still an 
issue*|https://github.com/apache/oozie/blob/master/core/pom.xml#L29] w/ Oozie 
{{5.1.0-SNAPSHOT}}.

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Mohammad Kamrul Islam
>Priority: Major
> Attachments: OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2605) email action chinese disorderly code

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2605:
-

[~whgcxq] can you reproduce using Oozie CLI only? Can you please also post 
{{workflow.xml}}, {{job.properties}}, and expected output?

> email action chinese disorderly code
> 
>
> Key: OOZIE-2605
> URL: https://issues.apache.org/jira/browse/OOZIE-2605
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
> Environment: HUE 4.1.0
>Reporter: gewenhui
>Priority: Major
> Fix For: 4.1.0
>
>
> I use cloudera manager install the oozie and use HUE Operate oozie.
> Send Chinese mail ,it appears chinese disorderly code



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

[jira] [Resolved] (OOZIE-2633) Some Oozie 4.2 maven artifacts missing from maven central

[Andras Piros (JIRA)]

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

Andras Piros resolved OOZIE-2633.
-
Resolution: Won't Fix

> Some Oozie 4.2 maven artifacts missing from maven central
> -
>
> Key: OOZIE-2633
> URL: https://issues.apache.org/jira/browse/OOZIE-2633
> Project: Oozie
>  Issue Type: Wish
>  Components: bundle
>Affects Versions: 4.2.0
>Reporter: Tom Edwards
>Priority: Major
>  Labels: maven
>
> Some of the maven artifacts are missing for Oozie version 4.2, however they 
> exist for version 4.1.  The specific artifacts missing for 4.2 are:
>   - oozie-hadoop
>   - oozie-hadoop-dist
>   - oozie-hadoop-test
>   - oozie-hadoop-utils
> These artifacts are needed in order to perform certain integration with Oozie.



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

[jira] [Commented] (OOZIE-2633) Some Oozie 4.2 maven artifacts missing from maven central

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2633:
-

[~dbist13] closing. [~tom.edwards.development] please feel free to reopen if 
you want specifically to integrate w/ 4.2.0 instead of 5.0.0 / 4.3.1.

> Some Oozie 4.2 maven artifacts missing from maven central
> -
>
> Key: OOZIE-2633
> URL: https://issues.apache.org/jira/browse/OOZIE-2633
> Project: Oozie
>  Issue Type: Wish
>  Components: bundle
>Affects Versions: 4.2.0
>Reporter: Tom Edwards
>Priority: Major
>  Labels: maven
>
> Some of the maven artifacts are missing for Oozie version 4.2, however they 
> exist for version 4.1.  The specific artifacts missing for 4.2 are:
>   - oozie-hadoop
>   - oozie-hadoop-dist
>   - oozie-hadoop-test
>   - oozie-hadoop-utils
> These artifacts are needed in order to perform certain integration with Oozie.



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

[jira] [Commented] (OOZIE-1516) Usability issues submitting jobs

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-1516:
-

[~chitnis] still reproducible under Oozie 5.0.0? If not, closing.

> Usability issues submitting jobs
> 
>
> Key: OOZIE-1516
> URL: https://issues.apache.org/jira/browse/OOZIE-1516
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
> Environment: Cloudera CDH4 latest on Centos
>Reporter: Brad Cox
>Priority: Critical
>
> J Harsh suggested filing a usability issue concerning a problem he helped me 
> resolve via email. Problem seems to boil down to differences between 
> localhost and localhost.localdomain that I don't understand well enough to 
> explain here. I've enclosed the email thread as documentation.
> J Harsh...
> I believe we seem to be doing a strict hostname check in Apache Oozie
> and not a resolving check. Could you report an improvement on the
> Apache Oozie JIRA (https://issues.apache.org/jira/browse/OOZIE)
> upstream to perhaps improve this for usability?
> On Sun, Sep 1, 2013 at 2:41 AM, Brad Cox  wrote:
> Copied examples to /user/cloudera/examples and changed nameNode to
> hdfs://localhost.localdomain in job.properties. Results look like a good
> sign.
> [cloudera@localhost Desktop]$ oozie job -oozie http://localhost:11000/oozie
> -config examples/apps/map-reduce/job.properties -run
> job: 000-130831130415538-oozie-oozi-W
> But in oozie console, got a job fail because jobTracker's not in whitelist
> so changed that to just localhost.localdomain by analogy.
> [cloudera@localhost Desktop]$ oozie job -oozie http://localhost:11000/oozie
> -config examples/apps/map-reduce/job.properties -run
> job: 001-130831130415538-oozie-oozi-W
> Console says that try succeeded. So thanks for the help!!
> All I'm missing is an understanding of why cloudera comes outOfBox with some
> services configured as localhost and others localhost.localdomain. I always
> thought they were equivalent. But these are huge differences; success vs
> fail.
> On Aug 31, 2013, at 4:58 PM, Brad Cox  wrote:
> You mean use localhost.localdomain instead of localhost? Or should I define
> a unique name with hostname cmd, restart all, and use that instead?
> [cloudera@localhost Desktop]$ hostname
> localhost.localdomain
> On Aug 31, 2013, at 4:54 PM, Harsh J  wrote:
> The whitelist message is close to the solution. Do not use 'localhost'
> in your job.properties, but replace it with whatever the command
> 'hostname' produces on your terminal, and I believe it should do the
> trick.
> On Sat, Aug 31, 2013 at 11:11 PM, Brad Cox  wrote:
> That's what I tried in previous attempts. That causes this
> oozie job -oozie http://localhost:11000/oozie -config
> examples/apps/map-reduce/job.properties -run
> Error: HTTP error code: 500 : Internal Server Error
> /var/log/lochost.date.log contains
> Caused by: java.net.URISyntaxException: Relative path in absolute URI:
> localhost:8020/user/cloudera/examples/apps/map-reduce
>  at java.net.URI.checkPath(URI.java:1788)
> examples is where I put it as you said
> [cloudera@localhost Desktop]$ hdfs dfs -ls /
> Found 8 items
> drwxr-xr-x   - hdfs  supergroup  0 2013-08-30 15:28 /accumulo
> drwxr-xr-x   - oozie supergroup  0 2013-08-31 04:52 /examples
> drwxr-xr-x   - hbase hbase   0 2013-08-31 07:22 /hbase
> drwxr-xr-x   - hdfs  supergroup  0 2013-08-30 16:38 /share
> drwxr-xr-x   - solr  solr0 2013-07-17 00:03 /solr
> drwxrwxrwx   - hdfs  supergroup  0 2013-08-30 16:32 /tmp
> drwxr-xr-x   - hdfs  supergroup  0 2013-08-30 16:32 /user
> drwxr-xr-x   - hdfs  supergroup  0 2013-07-17 00:03 /var
> All this is after hacking nameNode=localhost:8020 (was hdfs://...) in
> job.properties based on the Running the Examples section of the Oozie docs.
> On reverting that change, the message changed to the problem I had before:
> oozie job -oozie http://localhost:11000/oozie -config
> examples/apps/map-reduce/job.properties -run
> Error: E0901 : E0901: Namenode [localhost:8020] not allowed, not in Oozies
> whitelist
> Based on that msg, I'd already changed
> oozie.service.HadoopAccessorService.nameNode.whitelist to localhost:8020 in
> /etc/oozie/conf/oozie-site.xml and just made a similar change to
> jobTracker.whitelist to localhost:8021. Best I've been able to do is switch
> mystifying messages.
> On Aug 31, 2013, at 12:22 PM, Harsh J  wrote:
> Hi Brad,
> In Oozie, an simple "application" consists of a directory on HDFS that
> carries workflow.xml, and associated libraries/files.
> To invoke an instance of such an application, we use a local
> job.properties 

[jira] [Resolved] (OOZIE-2562) Web application not getting started and Tomcat is shutting down with hadoop-2.7.2

[Andras Piros (JIRA)]

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

Andras Piros resolved OOZIE-2562.
-
Resolution: Won't Fix

Won't fix for 5.0.0 as that installation is based on Jetty instead of Tomcat.

> Web application not getting started and Tomcat is shutting down with 
> hadoop-2.7.2
> -
>
> Key: OOZIE-2562
> URL: https://issues.apache.org/jira/browse/OOZIE-2562
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
> Environment: Centos7
>Reporter: Prakash K
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: catalina.2016-06-09.log, catalina.out, oozie-error.log, 
> oozie-instrumentation.log, oozie-jpa.log, oozie-ops.log, oozie.log
>
>   Original Estimate: 53h
>  Remaining Estimate: 53h
>
> Jun 08, 2016 11:40:47 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal 
> performance in production environments was not found on the 
> java.library.path: 
> Jun 08, 2016 11:40:48 AM org.apache.coyote.http11.Http11Protocol init
> SEVERE: Error initializing endpoint
> java.net.BindException: Address already in use :11000
>   at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:549)
>   at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:182)
>   at 
> org.apache.catalina.connector.Connector.initialize(Connector.java:1123)
>   at 
> org.apache.catalina.core.StandardService.initialize(StandardService.java:703)
>   at 
> org.apache.catalina.core.StandardServer.initialize(StandardServer.java:843)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:538)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:562)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
>   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Caused by: java.net.BindException: Address already in use
>   at java.net.PlainSocketImpl.socketBind(Native Method)
>   at 
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
>   at java.net.ServerSocket.bind(ServerSocket.java:376)
>   at java.net.ServerSocket.(ServerSocket.java:237)
>   at java.net.ServerSocket.(ServerSocket.java:181)
>   at 
> org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
>   at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:538)
>   ... 12 more
> Jun 08, 2016 11:40:48 AM org.apache.catalina.core.StandardService initialize
> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-11000]]
> LifecycleException:  Protocol handler initialization failed: 
> java.net.BindException: Address already in use :11000
>   at 
> org.apache.catalina.connector.Connector.initialize(Connector.java:1125)
>   at 
> org.apache.catalina.core.StandardService.initialize(StandardService.java:703)
>   at 
> org.apache.catalina.core.StandardServer.initialize(StandardServer.java:843)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:538)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:562)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
>   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Jun 08, 2016 11:40:48 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 594 ms
> Jun 08, 2016 11:40:48 AM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Jun 08, 2016 11:40:48 AM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.43
> Jun 08, 2016 11:40:48 AM org.apache.catalina.startup.HostConfig 
> deployDescriptor
> INFO: Deploying configuration descriptor oozie.xml
> Jun 08, 2016 11:40:52 AM org.apache.catalina.loader.WebappClassLoader 
> validateJarFile
> INFO: 
> validateJarFile(/usr/local/oozie/distro/target/oozie-4.2.0-distro/oozie-4.2.0/oozie-server/webapps/oozie/WEB-INF/lib/hive-jdbc-2.0.0-standalone.jar)
>  - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending