Failed: OOZIE-3443 PreCommit Build #1061
Jira: https://issues.apache.org/jira/browse/OOZIE-3443 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1061/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 1.91 MB...] [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 [WARN] There are [4] new bugs found in [server]. [DEBUG] You can find the SpotBugs diff here: server/findbugs-new.html [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [fluent-job/fluent-job-api]. [ERROR] There are [6] new bugs found below threshold in total that must be fixed. [TRACE] SpotBugs diffs checked and reports created [TRACE] Summary file size is 3482 bytes [TRACE] Full summary file size is 3830 bytes [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Testing JIRA OOZIE-3443 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 star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings -1 There are [6] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [webapp]. -1 There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html The top [5] most important SpotBugs errors are: At BulkJPAExecutor.java:[line 207]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176] At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200] This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207] At BulkJPAExecutor.java:[line 112]: At BulkJPAExecutor.java:[line 128] +1 There are no new bugs found in [client]. +1 There are no new bugs found in [docs]. +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/hive2]. +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/git]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [tools]. 0 There are [4] new bugs found in [server] that would be nice to have fixed. You can find the SpotBugs diff here: server/findbugs-new.html +1 There are no new bugs found in [fluent-job/fluent-job-api]. +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: 3169 +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/1061/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 41450 0 100 4145 0 5785 --:--:-- --:--:-- --:--:--
[jira] [Commented] (OOZIE-3443) Migrate from joda time to java.time
[
https://issues.apache.org/jira/browse/OOZIE-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801997#comment-16801997
]
Hadoop QA commented on OOZIE-3443:
--
Testing JIRA OOZIE-3443
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 star imports
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [6] 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 [6] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 207]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176]
.At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207]
.At BulkJPAExecutor.java:[line 112]: At BulkJPAExecutor.java:[line 128]
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [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/hive2].
.{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/git].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:orange}0{color} There are [4] new bugs found in [server] that would
be nice to have fixed.
.You can find the SpotBugs diff here: server/findbugs-new.html
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
{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: 3169
{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/1061/
> Migrate from joda time to java.time
> ---
>
> Key: OOZIE-3443
> URL: https://issues.apache.org/jira/browse/OOZIE-3443
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Mate Juhasz
>Priority: Minor
> Attachments: OOZIE-3443-V1.patch, OOZIE-3443-V2.patch,
> OOZIE-3443-V3.patch
>
>
> From Java SE 8 onwards, users are asked to migrate to from [joda
> time|https://www.joda.org/joda-time/] to java.time (JSR-310).
> It seems to me, that we only use it directly in one place:
>
[jira] [Commented] (OOZIE-3443) Migrate from joda time to java.time
[ https://issues.apache.org/jira/browse/OOZIE-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801874#comment-16801874 ] Hadoop QA commented on OOZIE-3443: -- PreCommit-OOZIE-Build started > Migrate from joda time to java.time > --- > > Key: OOZIE-3443 > URL: https://issues.apache.org/jira/browse/OOZIE-3443 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Attachments: OOZIE-3443-V1.patch, OOZIE-3443-V2.patch, > OOZIE-3443-V3.patch > > > From Java SE 8 onwards, users are asked to migrate to from [joda > time|https://www.joda.org/joda-time/] to java.time (JSR-310). > It seems to me, that we only use it directly in one place: > [TestWorkflowActionRetryInfoXCommand.java|https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/command/wf/TestWorkflowActionRetryInfoXCommand.java] > so it would be not too difficult to migrate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Failed: OOZIE-3179 PreCommit Build #1060
Jira: https://issues.apache.org/jira/browse/OOZIE-3179 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1060/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 1.92 MB...] [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [ERROR] There are [4] new bugs found below threshold in [core]. [DEBUG] You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html [ERROR] There are [5] new bugs found below threshold in total that must be fixed. [TRACE] SpotBugs diffs checked and reports created [TRACE] Summary file size is 3768 bytes [TRACE] Full summary file size is 3576 bytes [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Testing JIRA OOZIE-3179 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 star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings -1 There are [5] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/spark]. -1 There are [1] new bugs found below threshold in [sharelib/oozie] that must be fixed. You can find the SpotBugs diff here (look for the red and orange ones): sharelib/oozie/findbugs-new.html The most important SpotBugs errors are: At ShellMain.java:[line 92]: This usage of java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to Command Injection At ShellMain.java:[line 90]: At ShellMain.java:[line 89] At ShellMain.java:[line 91] +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/distcp]. +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/git]. +1 There are no new bugs found in [client]. +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [tools]. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [server]. +1 There are no new bugs found in [webapp]. +1 There are no new bugs found in [examples]. -1 There are [4] new bugs found below threshold in [core] that must be fixed. You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html The most important SpotBugs errors are: At BulkJPAExecutor.java:[line 207]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176] At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200] This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207] At BulkJPAExecutor.java:[line 112]: At BulkJPAExecutor.java:[line 128] +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: 3170 +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/1060/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
[jira] [Commented] (OOZIE-3179) Adding a configurable config-default.xml location to a workflow
[
https://issues.apache.org/jira/browse/OOZIE-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801868#comment-16801868
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
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 star imports
.{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} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [5] new bugs found below threshold in total that
must be fixed.
.{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/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 92]: This usage of
java/lang/ProcessBuilder.init(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 90]: At ShellMain.java:[line 89]
.At ShellMain.java:[line 91]
.{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/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/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:red}-1{color} There are [4] new bugs found below threshold in
[core] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 207]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176]
.At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207]
.At BulkJPAExecutor.java:[line 112]: At BulkJPAExecutor.java:[line 128]
{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: 3170
{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/1060/
> Adding a configurable config-default.xml location to a workflow
> ---
>
> Key: OOZIE-3179
> URL: https://issues.apache.org/jira/browse/OOZIE-3179
> Project: Oozie
> Issue Type: Improvement
>Reporter: Jason Phelps
>Assignee: Jason Phelps
>Priority: Major
>
[jira] [Commented] (OOZIE-3443) Migrate from joda time to java.time
[
https://issues.apache.org/jira/browse/OOZIE-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801857#comment-16801857
]
Mate Juhasz commented on OOZIE-3443:
I agree :) I put back the dependency to the root pom.xml to force the versions
to 2.9.9, thanks [~asalamon74]!
Now the distro will look like this:
{noformat}
./embedded-oozie-server/webapp/WEB-INF/lib/joda-time-2.9.9.jar
./share/lib/pig/joda-time-2.9.9.jar
./share/lib/hcatalog/joda-time-2.9.9.jar
./share/lib/hive2/joda-time-2.9.9.jar
./share/lib/hive/joda-time-2.9.9.jar
./share/lib/spark/joda-time-2.9.9.jar
{noformat}
> Migrate from joda time to java.time
> ---
>
> Key: OOZIE-3443
> URL: https://issues.apache.org/jira/browse/OOZIE-3443
> Project: Oozie
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Andras Salamon
>Assignee: Mate Juhasz
>Priority: Minor
> Attachments: OOZIE-3443-V1.patch, OOZIE-3443-V2.patch,
> OOZIE-3443-V3.patch
>
>
> From Java SE 8 onwards, users are asked to migrate to from [joda
> time|https://www.joda.org/joda-time/] to java.time (JSR-310).
> It seems to me, that we only use it directly in one place:
> [TestWorkflowActionRetryInfoXCommand.java|https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/command/wf/TestWorkflowActionRetryInfoXCommand.java]
> so it would be not too difficult to migrate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3443) Migrate from joda time to java.time
[ https://issues.apache.org/jira/browse/OOZIE-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Juhasz updated OOZIE-3443: --- Attachment: OOZIE-3443-V3.patch > Migrate from joda time to java.time > --- > > Key: OOZIE-3443 > URL: https://issues.apache.org/jira/browse/OOZIE-3443 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Attachments: OOZIE-3443-V1.patch, OOZIE-3443-V2.patch, > OOZIE-3443-V3.patch > > > From Java SE 8 onwards, users are asked to migrate to from [joda > time|https://www.joda.org/joda-time/] to java.time (JSR-310). > It seems to me, that we only use it directly in one place: > [TestWorkflowActionRetryInfoXCommand.java|https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/command/wf/TestWorkflowActionRetryInfoXCommand.java] > so it would be not too difficult to migrate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3443) Migrate from joda time to java.time
[ https://issues.apache.org/jira/browse/OOZIE-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801844#comment-16801844 ] Andras Salamon commented on OOZIE-3443: --- [~matijhs] Ouch. It's not a good idea to downgrade the joda version in the sharelibs (and in oozie-server) even if the projects require and old version. We should probably use the same joda versions just like before the patch. > Migrate from joda time to java.time > --- > > Key: OOZIE-3443 > URL: https://issues.apache.org/jira/browse/OOZIE-3443 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Attachments: OOZIE-3443-V1.patch, OOZIE-3443-V2.patch > > > From Java SE 8 onwards, users are asked to migrate to from [joda > time|https://www.joda.org/joda-time/] to java.time (JSR-310). > It seems to me, that we only use it directly in one place: > [TestWorkflowActionRetryInfoXCommand.java|https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/command/wf/TestWorkflowActionRetryInfoXCommand.java] > so it would be not too difficult to migrate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OOZIE-3454) Fix oozie-setup.sh usage information
Andras Salamon created OOZIE-3454:
-
Summary: Fix oozie-setup.sh usage information
Key: OOZIE-3454
URL: https://issues.apache.org/jira/browse/OOZIE-3454
Project: Oozie
Issue Type: Bug
Reporter: Andras Salamon
This is the usage information of {{oozie-setup.sh}}:
{noformat}
Usage : oozie-setup.sh
sharelib create -fs FS_URI [-locallib SHARED_LIBRARY] [-concurrency
CONCURRENCY]
(create
sharelib for oozie,
FS_URI is the
fs.default.name
for hdfs uri;
SHARED_LIBRARY, path to the
Oozie sharelib
to install, it can be a tarball
or an expanded
version of it. If omitted,
the Oozie
sharelib tarball from the Oozie
installation
directory will be used.
CONCURRENCY is
a number of threads to be used
for copy
operations.
By default 1
thread will be used)
(action fails
if sharelib is already installed
in HDFS)
sharelib upgrade -fs FS_URI [-locallib SHARED_LIBRARY]
([deprecated][use create command to create new version]
upgrade
existing sharelib, fails if there
is no
existing sharelib installed in HDFS)
db create|upgrade|postupgrade -run [-sqlfile ] (create, upgrade
or postupgrade oozie db with an
optional sql
File)
export exports the
oozie database to the specified
file in zip
format
import imports the
oozie database from the zip file
created by
export
(without options prints this usage information)
EXTJS can be downloaded from http://www.extjs.com/learn/Ext_Version_Archives
{noformat}
It sounds logical that without options the script prints of the usage
information, but this is not true:
{noformat}
$ oozie-setup.sh
INFO: Oozie webconsole disabled, ExtJS library not specified
INFO: Oozie is ready to be started
{noformat}
Checking the source code also shows that in this case it will
[call|https://github.com/apache/oozie/blob/master/distro/src/main/bin/oozie-setup.sh#L249-L251]
the prepare_jetty part of the script. It only prints out the usage information
if we add an invalid option.
Since calling the script without options is the only way to access the
prepare_jetty part and we want to keep the script compatible with the earlier
versions, probably we could just delete this sentence.
The "EXTJS can be downloaded" part is also obsolete, it cannot be downloaded
from the link. I'm afraid this version is so old, it cannot be downloaded from
the official website anymore. This [stackoverflow
answer|https://stackoverflow.com/a/49298186/21348] suggests to download it from
the cloudera archive, but I'm not sure if it's a good idea to put that link
into the opensource Oozie.
If we fix this, we also need to fix the
[documentation|https://oozie.apache.org/docs/5.1.0/AG_Install.html], since it
also contains the usage information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3179) Adding a configurable config-default.xml location to a workflow
[ https://issues.apache.org/jira/browse/OOZIE-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801736#comment-16801736 ] Jason Phelps commented on OOZIE-3179: - Adding rebased patch updated for the code changes in OOZIE-3370 as well > Adding a configurable config-default.xml location to a workflow > --- > > Key: OOZIE-3179 > URL: https://issues.apache.org/jira/browse/OOZIE-3179 > Project: Oozie > Issue Type: Improvement >Reporter: Jason Phelps >Assignee: Jason Phelps >Priority: Major > Attachments: OOZIE-3179-1.patch, OOZIE-3179-2.patch > > > Recently a customer requested a way to include several job.properties > variables to every workflow in their cluster. > Normally the config-default.xml file would be the best way to include a set > of variables, but it does not scale very well if that file needs to be > updated, as it would require it to be updated in every workflow application > path. > What I am requesting is another job.properties variable that can point to a > config-default.xml file, or a comma separated list of config-default.xml > files that will all be applied to the workflow. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Failed: OOZIE-3179 PreCommit Build #1059
Jira: https://issues.apache.org/jira/browse/OOZIE-3179
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1059/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 805.13 KB...]
[INFO] Reactor Summary for Apache Oozie Main 5.2.0-SNAPSHOT:
[INFO]
[INFO] Apache Oozie Main .. SUCCESS [ 1.935 s]
[INFO] Apache Oozie Fluent Job SUCCESS [ 0.080 s]
[INFO] Apache Oozie Fluent Job API SUCCESS [ 25.544 s]
[INFO] Apache Oozie Client SUCCESS [ 16.235 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 11.913 s]
[INFO] Apache Oozie Share Lib HCatalog SUCCESS [ 6.307 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 5.236 s]
[INFO] Apache Oozie Core .. SUCCESS [01:26 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [ 7.898 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [ 8.237 s]
[INFO] Apache Oozie Share Lib Git . SUCCESS [ 10.471 s]
[INFO] Apache Oozie Share Lib Hive SUCCESS [ 8.119 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 9.193 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [ 6.064 s]
[INFO] Apache Oozie Examples .. SUCCESS [ 9.192 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 11.053 s]
[INFO] Apache Oozie Share Lib . SUCCESS [ 0.024 s]
[INFO] Apache Oozie Docs .. SUCCESS [ 3.489 s]
[INFO] Apache Oozie WebApp SUCCESS [ 9.138 s]
[INFO] Apache Oozie Tools . SUCCESS [ 12.988 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [ 1.940 s]
[INFO] Apache Oozie Fluent Job Client . SUCCESS [ 0.567 s]
[INFO] Apache Oozie Server SUCCESS [ 10.417 s]
[INFO] Apache Oozie Distro SUCCESS [ 2.332 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [ 3.032 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 04:28 min
[INFO] Finished at: 2019-03-26T13:38:32Z
[INFO]
[TRACE] SpotBugs 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 client/src/main/java/org/apache/oozie/client/OozieClient.java...
Hunk #1 succeeded at 174 (offset -15 lines).
Checking patch
core/src/main/java/org/apache/oozie/command/wf/SubmitXCommand.java...
error: while searching for:
Configuration fsConf = has.createConfiguration(uri.getAuthority());
FileSystem fs = has.createFileSystem(user, uri, fsConf);
Path configDefault = null;
Configuration defaultConf = null;
// app path could be a directory
Path path = new Path(uri.getPath());
if (!fs.isFile(path)) {
configDefault = new Path(path, CONFIG_DEFAULT);
} else {
configDefault = new Path(path.getParent(), CONFIG_DEFAULT);
}
if (fs.exists(configDefault)) {
try {
defaultConf = new XConfiguration(fs.open(configDefault));
PropertiesUtils.checkDisallowedProperties(defaultConf,
DISALLOWED_DEFAULT_PROPERTIES);
XConfiguration.injectDefaults(defaultConf, conf);
}
catch (IOException ex) {
throw new IOException("default configuration file, " +
ex.getMessage(), ex);
}
}
if (defaultConf != null) {
defaultConf = resolveDefaultConfVariables(defaultConf);
}
WorkflowApp app = wps.parseDef(conf, defaultConf);
XConfiguration protoActionConf = wps.createProtoActionConf(conf,
true);
error: patch failed:
core/src/main/java/org/apache/oozie/command/wf/SubmitXCommand.java:140
error: core/src/main/java/org/apache/oozie/command/wf/SubmitXCommand.java:
patch does not apply
Checking patch
core/src/test/java/org/apache/oozie/command/wf/TestSubmitXCommand.java...
Checking patch src/main/java/org/apache/oozie/client/OozieClient.java...
error: src/main/java/org/apache/oozie/client/OozieClient.java: No such file or
directory
Checking patch src/main/java/org/apache/oozie/command/wf/SubmitXCommand.java...
error:
[jira] [Commented] (OOZIE-3179) Adding a configurable config-default.xml location to a workflow
[
https://issues.apache.org/jira/browse/OOZIE-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801715#comment-16801715
]
Hadoop QA commented on OOZIE-3179:
--
Testing JIRA OOZIE-3179
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Adding a configurable config-default.xml location to a workflow
> ---
>
> Key: OOZIE-3179
> URL: https://issues.apache.org/jira/browse/OOZIE-3179
> Project: Oozie
> Issue Type: Improvement
>Reporter: Jason Phelps
>Assignee: Jason Phelps
>Priority: Major
> Attachments: OOZIE-3179-1.patch, OOZIE-3179-2.patch
>
>
> Recently a customer requested a way to include several job.properties
> variables to every workflow in their cluster.
> Normally the config-default.xml file would be the best way to include a set
> of variables, but it does not scale very well if that file needs to be
> updated, as it would require it to be updated in every workflow application
> path.
> What I am requesting is another job.properties variable that can point to a
> config-default.xml file, or a comma separated list of config-default.xml
> files that will all be applied to the workflow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3179) Adding a configurable config-default.xml location to a workflow
[ https://issues.apache.org/jira/browse/OOZIE-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801700#comment-16801700 ] Hadoop QA commented on OOZIE-3179: -- PreCommit-OOZIE-Build started > Adding a configurable config-default.xml location to a workflow > --- > > Key: OOZIE-3179 > URL: https://issues.apache.org/jira/browse/OOZIE-3179 > Project: Oozie > Issue Type: Improvement >Reporter: Jason Phelps >Assignee: Jason Phelps >Priority: Major > Attachments: OOZIE-3179-1.patch, OOZIE-3179-2.patch > > > Recently a customer requested a way to include several job.properties > variables to every workflow in their cluster. > Normally the config-default.xml file would be the best way to include a set > of variables, but it does not scale very well if that file needs to be > updated, as it would require it to be updated in every workflow application > path. > What I am requesting is another job.properties variable that can point to a > config-default.xml file, or a comma separated list of config-default.xml > files that will all be applied to the workflow. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3179) Adding a configurable config-default.xml location to a workflow
[ https://issues.apache.org/jira/browse/OOZIE-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801681#comment-16801681 ] Andras Salamon commented on OOZIE-3179: --- [~jphelps] Can you please rebase the patch? > Adding a configurable config-default.xml location to a workflow > --- > > Key: OOZIE-3179 > URL: https://issues.apache.org/jira/browse/OOZIE-3179 > Project: Oozie > Issue Type: Improvement >Reporter: Jason Phelps >Assignee: Jason Phelps >Priority: Major > Attachments: OOZIE-3179-1.patch, OOZIE-3179-2.patch > > > Recently a customer requested a way to include several job.properties > variables to every workflow in their cluster. > Normally the config-default.xml file would be the best way to include a set > of variables, but it does not scale very well if that file needs to be > updated, as it would require it to be updated in every workflow application > path. > What I am requesting is another job.properties variable that can point to a > config-default.xml file, or a comma separated list of config-default.xml > files that will all be applied to the workflow. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-2652) Skip trash while deleting hive table partition
[
https://issues.apache.org/jira/browse/OOZIE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801544#comment-16801544
]
Hadoop QA commented on OOZIE-2652:
--
Testing JIRA OOZIE-2652
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Skip trash while deleting hive table partition
> --
>
> Key: OOZIE-2652
> URL: https://issues.apache.org/jira/browse/OOZIE-2652
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-2652-1.patch
>
>
> Currently, when we delete a partition in the work flow, the data persists in
> trash and does not get purged. This takes up namespaces.
> {code}
>
> ${jobTracker}
> ${oozieNameNode}
>
>
>
> {code}
> Solution: User will pass on "skip-trash" option. Accordingly, Oozie will call
> appropriate hcat api.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Failed: OOZIE-2652 PreCommit Build #1058
Jira: https://issues.apache.org/jira/browse/OOZIE-2652 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1058/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 804.80 KB...] [INFO] --- spotbugs-maven-plugin:3.1.11:spotbugs (spotbugs) @ oozie-zookeeper-security-tests --- [INFO] [INFO] <<< spotbugs-maven-plugin:3.1.11:check (default-cli) < :spotbugs @ oozie-zookeeper-security-tests <<< [INFO] [INFO] [INFO] --- spotbugs-maven-plugin:3.1.11:check (default-cli) @ oozie-zookeeper-security-tests --- [INFO] [INFO] Reactor Summary for Apache Oozie Main 5.2.0-SNAPSHOT: [INFO] [INFO] Apache Oozie Main .. SUCCESS [ 4.541 s] [INFO] Apache Oozie Fluent Job SUCCESS [ 0.134 s] [INFO] Apache Oozie Fluent Job API SUCCESS [ 30.789 s] [INFO] Apache Oozie Client SUCCESS [ 18.072 s] [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 13.601 s] [INFO] Apache Oozie Share Lib HCatalog SUCCESS [ 7.007 s] [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 5.840 s] [INFO] Apache Oozie Core .. SUCCESS [01:37 min] [INFO] Apache Oozie Share Lib Streaming ... SUCCESS [ 8.344 s] [INFO] Apache Oozie Share Lib Pig . SUCCESS [ 8.487 s] [INFO] Apache Oozie Share Lib Git . SUCCESS [ 11.653 s] [INFO] Apache Oozie Share Lib Hive SUCCESS [ 8.523 s] [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 9.929 s] [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [ 6.311 s] [INFO] Apache Oozie Examples .. SUCCESS [ 10.362 s] [INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 11.789 s] [INFO] Apache Oozie Share Lib . SUCCESS [ 0.025 s] [INFO] Apache Oozie Docs .. SUCCESS [ 3.278 s] [INFO] Apache Oozie WebApp SUCCESS [ 9.634 s] [INFO] Apache Oozie Tools . SUCCESS [ 14.342 s] [INFO] Apache Oozie MiniOozie . SUCCESS [ 1.822 s] [INFO] Apache Oozie Fluent Job Client . SUCCESS [ 0.530 s] [INFO] Apache Oozie Server SUCCESS [ 11.320 s] [INFO] Apache Oozie Distro SUCCESS [ 2.427 s] [INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [ 3.238 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 05:00 min [INFO] Finished at: 2019-03-26T10:09:56Z [INFO] [TRACE] SpotBugs 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 a/client/src/main/resources/hive-action-0.5.xsd => b/client/src/main/resources/hive-action-0.5.xsd... error: a/client/src/main/resources/hive-action-0.5.xsd: No such file or directory Checking patch a/sharelib/hcatalog/src/main/java/org/apache/oozie/action/hadoop/HCatLauncherURIHandler.java => b/sharelib/hcatalog/src/main/java/org/apache/oozie/action/hadoop/HCatLauncherURIHandler.java... error: a/sharelib/hcatalog/src/main/java/org/apache/oozie/action/hadoop/HCatLauncherURIHandler.java: No such file or directory Checking patch a/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/FSLauncherURIHandler.java => b/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/FSLauncherURIHandler.java... error: a/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/FSLauncherURIHandler.java: No such file or directory Checking patch a/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherURIHandler.java => b/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherURIHandler.java... error: a/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherURIHandler.java: No such file or directory Checking patch a/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/PrepareActionsDriver.java => b/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/PrepareActionsDriver.java... error: a/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/PrepareActionsDriver.java: No such file or directory Checking patch client/src/main/resources/hive-action-0.5.xsd... Checking patch sharelib/hcatalog/src/main/java/org/apache/oozie/action/hadoop/HCatLauncherURIHandler.java... Hunk
[jira] [Commented] (OOZIE-2652) Skip trash while deleting hive table partition
[
https://issues.apache.org/jira/browse/OOZIE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801539#comment-16801539
]
Hadoop QA commented on OOZIE-2652:
--
PreCommit-OOZIE-Build started
> Skip trash while deleting hive table partition
> --
>
> Key: OOZIE-2652
> URL: https://issues.apache.org/jira/browse/OOZIE-2652
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-2652-1.patch
>
>
> Currently, when we delete a partition in the work flow, the data persists in
> trash and does not get purged. This takes up namespaces.
> {code}
>
> ${jobTracker}
> ${oozieNameNode}
>
>
>
> {code}
> Solution: User will pass on "skip-trash" option. Accordingly, Oozie will call
> appropriate hcat api.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-2652) Skip trash while deleting hive table partition
[
https://issues.apache.org/jira/browse/OOZIE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801524#comment-16801524
]
Andras Salamon commented on OOZIE-2652:
---
I think this patch needs to be refactored, right now DELETE is defined in
[oozie-common-1.0.xsd|https://github.com/apache/oozie/blob/master/client/src/main/resources/oozie-common-1.0.xsd].
It would give us a more general solution than the original version of the
patch which only modified the hive xsd.
> Skip trash while deleting hive table partition
> --
>
> Key: OOZIE-2652
> URL: https://issues.apache.org/jira/browse/OOZIE-2652
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-2652-1.patch
>
>
> Currently, when we delete a partition in the work flow, the data persists in
> trash and does not get purged. This takes up namespaces.
> {code}
>
> ${jobTracker}
> ${oozieNameNode}
>
>
>
> {code}
> Solution: User will pass on "skip-trash" option. Accordingly, Oozie will call
> appropriate hcat api.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (90 issues) Subscriber: ooziedaily Key Summary OOZIE-3453 Copy only server dependencies in dependency folder to distro https://issues.apache.org/jira/browse/OOZIE-3453 OOZIE-3449 Make spark-2 as the default profile https://issues.apache.org/jira/browse/OOZIE-3449 OOZIE-3447 Run test case in local : It shows oozie-hsqldb-orm.xml exception https://issues.apache.org/jira/browse/OOZIE-3447 OOZIE-3443 Migrate from joda time to java.time https://issues.apache.org/jira/browse/OOZIE-3443 OOZIE-3418 Upgrade to Guava 27 https://issues.apache.org/jira/browse/OOZIE-3418 OOZIE-3404 The env variable of SPARK_HOME needs to be set when running pySpark https://issues.apache.org/jira/browse/OOZIE-3404 OOZIE-3375 Can't use empty in coordinator https://issues.apache.org/jira/browse/OOZIE-3375 OOZIE-3367 Using && in EL expressions in oozie bundle.xml files generates parse errors https://issues.apache.org/jira/browse/OOZIE-3367 OOZIE-3366 Update workflow status and subworkflow status on suspend command https://issues.apache.org/jira/browse/OOZIE-3366 OOZIE-3364 Rerunning Oozie bundle jobs starts the coordinators in indeterminate order https://issues.apache.org/jira/browse/OOZIE-3364 OOZIE-3362 When killed, SSH action should kill the spawned processes on target host https://issues.apache.org/jira/browse/OOZIE-3362 OOZIE-3335 Cleanup parseFilter methods https://issues.apache.org/jira/browse/OOZIE-3335 OOZIE-3320 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3320 OOZIE-3319 Log SSH action callback error output https://issues.apache.org/jira/browse/OOZIE-3319 OOZIE-3301 Update NOTICE file https://issues.apache.org/jira/browse/OOZIE-3301 OOZIE-3274 Remove slf4j https://issues.apache.org/jira/browse/OOZIE-3274 OOZIE-3266 Coord action rerun support RERUN_SKIP_NODES option https://issues.apache.org/jira/browse/OOZIE-3266 OOZIE-3265 properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to appear together https://issues.apache.org/jira/browse/OOZIE-3265 OOZIE-3256 refactor OozieCLI class https://issues.apache.org/jira/browse/OOZIE-3256 OOZIE-3249 [tools] Instrumentation log parser https://issues.apache.org/jira/browse/OOZIE-3249 OOZIE-3199 Let system property restriction configurable https://issues.apache.org/jira/browse/OOZIE-3199 OOZIE-3196 Authorization: restrict world readability by user https://issues.apache.org/jira/browse/OOZIE-3196 OOZIE-3179 Adding a configurable config-default.xml location to a workflow https://issues.apache.org/jira/browse/OOZIE-3179 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3137 Add support for log4j2 in HiveMain https://issues.apache.org/jira/browse/OOZIE-3137 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 OOZIE-3091 Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper" https://issues.apache.org/jira/browse/OOZIE-3091 OOZIE-3071 Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0 https://issues.apache.org/jira/browse/OOZIE-3071 OOZIE-3063 Sanitizing variables that are part of openjpa.ConnectionProperties https://issues.apache.org/jira/browse/OOZIE-3063 OOZIE-3062 Set HADOOP_CONF_DIR for spark action https://issues.apache.org/jira/browse/OOZIE-3062 OOZIE-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2927 Append new line character for Hive2 query using query tag https://issues.apache.org/jira/browse/OOZIE-2927 OOZIE-2834 ParameterVerifier logging non-useful warning for workflow definition https://issues.apache.org/jira/browse/OOZIE-2834 OOZIE-2833 when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes. https://issues.apache.org/jira/browse/OOZIE-2833 OOZIE-2812 SparkConfigurationService should support loading configurations from multiple Spark versions https://issues.apache.org/jira/browse/OOZIE-2812 OOZIE-2795 Create lib directory or symlink for Oozie CLI during packaging https://issues.apache.org/jira/browse/OOZIE-2795 OOZIE-2784 Include WEEK as a parameter in the Coordinator Expression Language Evaulator https://issues.apache.org/jira/browse/OOZIE-2784 OOZIE-2779 Mask Hive2 action Beeline JDBC password
