[jira] [Assigned] (OOZIE-3330) [spark-action] Remove double quotes inside plain option values
[
https://issues.apache.org/jira/browse/OOZIE-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Salamon reassigned OOZIE-3330:
-
Assignee: Andras Salamon
> [spark-action] Remove double quotes inside plain option values
> --
>
> Key: OOZIE-3330
> URL: https://issues.apache.org/jira/browse/OOZIE-3330
> Project: Oozie
> Issue Type: Bug
> Components: action
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3330.000.wip.patch
>
>
> For Spark action parametrization, OOZIE-2984 fixed the case where users tried
> to put quoted values inside assembled options, like {{--conf name1="value1
> value2"}}. The underlying Spark executor JVM treats {{"value1 value2"}} as
> one value with the quotes - we needed to remove these before passing to Spark.
> We have to extend that approach for plain option values like this: {{--name
> "value1 value2"}} where we also need to remove the quotes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3264) Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
[
https://issues.apache.org/jira/browse/OOZIE-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583948#comment-16583948
]
Andras Salamon commented on OOZIE-3264:
---
[~andras.piros] Sure thing: [https://reviews.apache.org/r/68411/]
> Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
> -
>
> Key: OOZIE-3264
> URL: https://issues.apache.org/jira/browse/OOZIE-3264
> Project: Oozie
> Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3264-1.patch
>
>
> The test {{testLastOnlyMaterialization}} failed.
> {noformat}
> junit.framework.AssertionFailedError: expected: but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.checkCoordActionsStatus(TestCoordMaterializeTransitionXCommand.java:1415)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testLastOnlyMaterialization(TestCoordMaterializeTransitionXCommand.java:1114)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3329) [build] test-patch-30-distro improvement
[
https://issues.apache.org/jira/browse/OOZIE-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3329:
Component/s: build
> [build] test-patch-30-distro improvement
>
>
> Key: OOZIE-3329
> URL: https://issues.apache.org/jira/browse/OOZIE-3329
> Project: Oozie
> Issue Type: Test
> Components: build
>Affects Versions: 5.0.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Minor
> Attachments: OOZIE-3329-1.patch
>
>
> The distro testing script (test-patch-30-distro) executes the following maven
> command:
> {noformat}
> mvn package assembly:single -DgenerateDocs -DskipTests
> {noformat}
> which might give false result if executed in a not totally clean directory.
> A maven clean should be executed before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3329) [build] test-patch-30-distro improvement
[
https://issues.apache.org/jira/browse/OOZIE-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3329:
Affects Version/s: 5.0.0
> [build] test-patch-30-distro improvement
>
>
> Key: OOZIE-3329
> URL: https://issues.apache.org/jira/browse/OOZIE-3329
> Project: Oozie
> Issue Type: Test
> Components: build
>Affects Versions: 5.0.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Minor
> Attachments: OOZIE-3329-1.patch
>
>
> The distro testing script (test-patch-30-distro) executes the following maven
> command:
> {noformat}
> mvn package assembly:single -DgenerateDocs -DskipTests
> {noformat}
> which might give false result if executed in a not totally clean directory.
> A maven clean should be executed before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3329) [build] test-patch-30-distro improvement
[
https://issues.apache.org/jira/browse/OOZIE-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3329:
Summary: [build] test-patch-30-distro improvement (was:
test-patch-30-distro improvement)
> [build] test-patch-30-distro improvement
>
>
> Key: OOZIE-3329
> URL: https://issues.apache.org/jira/browse/OOZIE-3329
> Project: Oozie
> Issue Type: Test
> Components: build
>Affects Versions: 5.0.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Minor
> Attachments: OOZIE-3329-1.patch
>
>
> The distro testing script (test-patch-30-distro) executes the following maven
> command:
> {noformat}
> mvn package assembly:single -DgenerateDocs -DskipTests
> {noformat}
> which might give false result if executed in a not totally clean directory.
> A maven clean should be executed before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3329) test-patch-30-distro improvement
[
https://issues.apache.org/jira/browse/OOZIE-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583945#comment-16583945
]
Andras Piros commented on OOZIE-3329:
-
Thanks for the contribution [~asalamon74]! +1
> test-patch-30-distro improvement
>
>
> Key: OOZIE-3329
> URL: https://issues.apache.org/jira/browse/OOZIE-3329
> Project: Oozie
> Issue Type: Test
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Minor
> Attachments: OOZIE-3329-1.patch
>
>
> The distro testing script (test-patch-30-distro) executes the following maven
> command:
> {noformat}
> mvn package assembly:single -DgenerateDocs -DskipTests
> {noformat}
> which might give false result if executed in a not totally clean directory.
> A maven clean should be executed before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Review Request 68411: OOZIE-3264 - Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68411/ --- Review request for oozie, András Piros, Kinga Marton, and Peter Bacsko. Repository: oozie-git Description --- OOZIE-3264 - Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization Diffs - core/src/test/java/org/apache/oozie/command/coord/TestCoordChangeXCommand.java b784093b core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java 8189732e core/src/test/java/org/apache/oozie/test/XDataTestCase.java a8fe7037 Diff: https://reviews.apache.org/r/68411/diff/1/ Testing --- I was using grind. Before the modification it was failing 2 times out of 50 executions, after the patch it works 50/50. Thanks, Andras Salamon
[jira] [Commented] (OOZIE-3264) Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
[
https://issues.apache.org/jira/browse/OOZIE-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583916#comment-16583916
]
Andras Piros commented on OOZIE-3264:
-
[~asalamon74] thanks for the contribution! Can you please create a ReviewBoard
request as well? Thanks!
> Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
> -
>
> Key: OOZIE-3264
> URL: https://issues.apache.org/jira/browse/OOZIE-3264
> Project: Oozie
> Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3264-1.patch
>
>
> The test {{testLastOnlyMaterialization}} failed.
> {noformat}
> junit.framework.AssertionFailedError: expected: but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.checkCoordActionsStatus(TestCoordMaterializeTransitionXCommand.java:1415)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testLastOnlyMaterialization(TestCoordMaterializeTransitionXCommand.java:1114)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3264) Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
[
https://issues.apache.org/jira/browse/OOZIE-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583864#comment-16583864
]
Hadoop QA commented on OOZIE-3264:
--
Testing JIRA OOZIE-3264
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 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new 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
[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 [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: 2918
.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommand#testNone
.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:green}*+1 Overall result, good!, no -1s*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/765/
> Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
> -
>
> Key: OOZIE-3264
> URL: https://issues.apache.org/jira/browse/OOZIE-3264
> Project: Oozie
> Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3264-1.patch
>
>
> The test {{testLastOnlyMaterialization}} failed.
> {noformat}
> junit.framework.AssertionFailedError: expected: but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.checkCoordActionsStatus(TestCoordMaterializeTransitionXCommand.java:1415)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testLastOnlyMaterialization(TestCoordMaterializeTransitionXCommand.java:1114)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Success: OOZIE-3264 PreCommit Build #765
Jira: https://issues.apache.org/jira/browse/OOZIE-3264 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/765/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 1.75 MB...] [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 2456 bytes [TRACE] Full summary file size is 1399 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-3264 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 3 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) WARNING: the current HEAD has 100 Javadoc warning(s) +1 the patch does not seem to introduce new 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 [fluent-job/fluent-job-api]. +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: 2918 Tests failed at first run: 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, good!, no -1s There is at least one warning, please check The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/765/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 33300 0 100 3330 0 4013 --:--:-- --:--:-- --:--:--
[jira] [Commented] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting
[
https://issues.apache.org/jira/browse/OOZIE-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583855#comment-16583855
]
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: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 2 testcase(s)
{color:red}-1 RAT{color}
.{color:red}-1{color} the patch seems to introduce 1 new RAT warning(s)
{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 [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
[fluent-job/fluent-job-api].
. {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: 2595
.{color:orange}Tests failed at first run:{color}
TestWorkflowRetries>TestWorkflow#testWorkflowWithStartAndEndCompletesSuccessfully
.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/764/
> 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-001.patch, OOZIE-3160-002.patch, OOZIE-3160-003.patch,
> OOZIE-3160-POC01.patch, OOZIE-3160-POC02.patch, OOZIE-3160-POC02.patch,
> OOZIE-3160-POC03.patch, OOZIE-3160-POC04.patch, OOZIE-3160-POC05.patch,
> PriorityDelayQueue improvement - OOZIE-3160.pdf
>
>
> 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-3160 PreCommit Build #764
Jira: https://issues.apache.org/jira/browse/OOZIE-3160
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/764/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 1.72 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 2442 bytes
[TRACE] Full summary file size is 1399 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-3160
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 2 testcase(s)
-1 RAT
-1 the patch seems to introduce 1 new RAT warning(s)
+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 [fluent-job/fluent-job-api].
+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: 2595
Tests failed at first run:
TestWorkflowRetries>TestWorkflow#testWorkflowWithStartAndEndCompletesSuccessfully
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/764/
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/13130774/comment/16583855","id":"16583855","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","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-3330) [spark-action] Remove double quotes inside plain option values
[
https://issues.apache.org/jira/browse/OOZIE-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583854#comment-16583854
]
Andras Piros commented on OOZIE-3330:
-
{{OOZIE-3330.000.wip.patch}} contains two new unit tests that are failing
currently and show the nature of the issue.
> [spark-action] Remove double quotes inside plain option values
> --
>
> Key: OOZIE-3330
> URL: https://issues.apache.org/jira/browse/OOZIE-3330
> Project: Oozie
> Issue Type: Bug
> Components: action
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Priority: Major
> Attachments: OOZIE-3330.000.wip.patch
>
>
> For Spark action parametrization, OOZIE-2984 fixed the case where users tried
> to put quoted values inside assembled options, like {{--conf name1="value1
> value2"}}. The underlying Spark executor JVM treats {{"value1 value2"}} as
> one value with the quotes - we needed to remove these before passing to Spark.
> We have to extend that approach for plain option values like this: {{--name
> "value1 value2"}} where we also need to remove the quotes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3330) [spark-action] Remove double quotes inside plain option values
[
https://issues.apache.org/jira/browse/OOZIE-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3330:
Attachment: OOZIE-3330.000.wip.patch
> [spark-action] Remove double quotes inside plain option values
> --
>
> Key: OOZIE-3330
> URL: https://issues.apache.org/jira/browse/OOZIE-3330
> Project: Oozie
> Issue Type: Bug
> Components: action
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Priority: Major
> Attachments: OOZIE-3330.000.wip.patch
>
>
> For Spark action parametrization, OOZIE-2984 fixed the case where users tried
> to put quoted values inside assembled options, like {{--conf name1="value1
> value2"}}. The underlying Spark executor JVM treats {{"value1 value2"}} as
> one value with the quotes - we needed to remove these before passing to Spark.
> We have to extend that approach for plain option values like this: {{--name
> "value1 value2"}} where we also need to remove the quotes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Review Request 67885: POC: OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67885/ --- (Updated aug. 17, 2018, 12:37 du) Review request for oozie, András Piros, Peter Cseh, Kinga Marton, and Robert Kanter. Repository: oozie-git Description --- See upstream JIRA for details Diffs (updated) - core/src/main/java/org/apache/oozie/service/AsyncXCommandExecutor.java PRE-CREATION core/src/main/java/org/apache/oozie/service/CallableQueueService.java ef8d58da5 core/src/main/java/org/apache/oozie/util/PriorityDelayQueue.java 75c20698c core/src/main/resources/oozie-default.xml b69d2c9aa core/src/test/java/org/apache/oozie/service/TestAsyncXCommandExecutor.java PRE-CREATION core/src/test/java/org/apache/oozie/service/TestCallableQueueService.java 9c2a11d6f Diff: https://reviews.apache.org/r/67885/diff/8/ Changes: https://reviews.apache.org/r/67885/diff/7-8/ Testing --- 1. Executed TestCallableQueueService which passed completely. 2. New unit tests for ASyncXCommandExecutor. 3. Tried it on a 3-node cluster Thanks, Peter Bacsko
Re: Review Request 67885: POC: OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67885/ --- (Updated aug. 17, 2018, 12:36 du) Review request for oozie, András Piros, Peter Cseh, Kinga Marton, and Robert Kanter. Repository: oozie-git Description (updated) --- See upstream JIRA for details Diffs - core/src/main/java/org/apache/oozie/service/AsyncXCommandExecutor.java PRE-CREATION core/src/main/java/org/apache/oozie/service/CallableQueueService.java ef8d58da5 core/src/main/java/org/apache/oozie/util/PriorityDelayQueue.java 75c20698c core/src/main/resources/oozie-default.xml b69d2c9aa core/src/test/java/org/apache/oozie/service/TestAsyncXCommandExecutor.java PRE-CREATION core/src/test/java/org/apache/oozie/service/TestCallableQueueService.java 9c2a11d6f Diff: https://reviews.apache.org/r/67885/diff/7/ Testing (updated) --- 1. Executed TestCallableQueueService which passed completely. 2. New unit tests for ASyncXCommandExecutor. 3. Tried it on a 3-node cluster Thanks, Peter Bacsko
[jira] [Updated] (OOZIE-3330) [spark-action] Remove double quotes inside plain option values
[
https://issues.apache.org/jira/browse/OOZIE-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3330:
Description:
For Spark action parametrization, OOZIE-2984 fixed the case where users tried
to put quoted values inside assembled options, like {{--conf name1="value1
value2"}}. The underlying Spark executor JVM treats {{"value1 value2"}} as one
value with the quotes - we needed to remove these before passing to Spark.
We have to extend that approach for plain option values like this: {{--name
"value1 value2"}} where we also need to remove the quotes.
was:
For Spark action parametrization, OOZIE-2984 fixed the case where users tried
to put quoted values inside assembled options, like {{--conf name1=\"value1
value2\"}}. The underlying Spark executor JVM treats {{\"value1 value2\"}} as
one value with the quotes - we needed to remove these before passing to Spark.
We have to extend that approach for plain option values like this: {{--name
\"value1 value2\"}} where we also need to remove the quotes.
> [spark-action] Remove double quotes inside plain option values
> --
>
> Key: OOZIE-3330
> URL: https://issues.apache.org/jira/browse/OOZIE-3330
> Project: Oozie
> Issue Type: Bug
> Components: action
>Affects Versions: 5.0.0
>Reporter: Andras Piros
>Priority: Major
>
> For Spark action parametrization, OOZIE-2984 fixed the case where users tried
> to put quoted values inside assembled options, like {{--conf name1="value1
> value2"}}. The underlying Spark executor JVM treats {{"value1 value2"}} as
> one value with the quotes - we needed to remove these before passing to Spark.
> We have to extend that approach for plain option values like this: {{--name
> "value1 value2"}} where we also need to remove the quotes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OOZIE-3330) [spark-action] Remove double quotes inside plain option values
Andras Piros created OOZIE-3330:
---
Summary: [spark-action] Remove double quotes inside plain option
values
Key: OOZIE-3330
URL: https://issues.apache.org/jira/browse/OOZIE-3330
Project: Oozie
Issue Type: Bug
Components: action
Affects Versions: 5.0.0
Reporter: Andras Piros
For Spark action parametrization, OOZIE-2984 fixed the case where users tried
to put quoted values inside assembled options, like {{--conf name1=\"value1
value2\"}}. The underlying Spark executor JVM treats {{\"value1 value2\"}} as
one value with the quotes - we needed to remove these before passing to Spark.
We have to extend that approach for plain option values like this: {{--name
\"value1 value2\"}} where we also need to remove the quotes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3264) Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
[
https://issues.apache.org/jira/browse/OOZIE-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583796#comment-16583796
]
Hadoop QA commented on OOZIE-3264:
--
PreCommit-OOZIE-Build started
> Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
> -
>
> Key: OOZIE-3264
> URL: https://issues.apache.org/jira/browse/OOZIE-3264
> Project: Oozie
> Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3264-1.patch
>
>
> The test {{testLastOnlyMaterialization}} failed.
> {noformat}
> junit.framework.AssertionFailedError: expected: but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.checkCoordActionsStatus(TestCoordMaterializeTransitionXCommand.java:1415)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testLastOnlyMaterialization(TestCoordMaterializeTransitionXCommand.java:1114)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3264) Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
[
https://issues.apache.org/jira/browse/OOZIE-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583764#comment-16583764
]
Andras Salamon commented on OOZIE-3264:
---
Sometimes it fails with a different error:
{noformat}
junit.framework.AssertionFailedError: expected: but was:
{noformat}
> Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
> -
>
> Key: OOZIE-3264
> URL: https://issues.apache.org/jira/browse/OOZIE-3264
> Project: Oozie
> Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
>
> The test {{testLastOnlyMaterialization}} failed.
> {noformat}
> junit.framework.AssertionFailedError: expected: but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.checkCoordActionsStatus(TestCoordMaterializeTransitionXCommand.java:1415)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testLastOnlyMaterialization(TestCoordMaterializeTransitionXCommand.java:1114)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OOZIE-3160) PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting
[
https://issues.apache.org/jira/browse/OOZIE-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583753#comment-16583753
]
Peter Bacsko edited comment on OOZIE-3160 at 8/17/18 10:44 AM:
---
[~rohini] [~puru] [~satishsaley] - do you guys have some time to take a look at
this patch? It's a pretty substantial change (for this reason, the original
code is kept, so users can switch back if they experience any issues). I really
should have involved you earlier, sorry for that - but the code is still not on
master.
was (Author: pbacsko):
[~rohini] [~puru] [~satishsaley] - do you guys have some time to take a look at
this patch? It's a pretty substantial change (for this reason, the original
code is kept, so users can switch back if they experience any issues).
> 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-001.patch, OOZIE-3160-002.patch, OOZIE-3160-003.patch,
> OOZIE-3160-POC01.patch, OOZIE-3160-POC02.patch, OOZIE-3160-POC02.patch,
> OOZIE-3160-POC03.patch, OOZIE-3160-POC04.patch, OOZIE-3160-POC05.patch,
> PriorityDelayQueue improvement - OOZIE-3160.pdf
>
>
> 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
[
https://issues.apache.org/jira/browse/OOZIE-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583753#comment-16583753
]
Peter Bacsko commented on OOZIE-3160:
-
[~rohini] [~puru] [~satishsaley] - do you guys have some time to take a look at
this patch? It's a pretty substantial change (for this reason, the original
code is kept, so users can switch back if they experience any issues).
> 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-001.patch, OOZIE-3160-002.patch, OOZIE-3160-003.patch,
> OOZIE-3160-POC01.patch, OOZIE-3160-POC02.patch, OOZIE-3160-POC02.patch,
> OOZIE-3160-POC03.patch, OOZIE-3160-POC04.patch, OOZIE-3160-POC05.patch,
> PriorityDelayQueue improvement - OOZIE-3160.pdf
>
>
> 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
[
https://issues.apache.org/jira/browse/OOZIE-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583746#comment-16583746
]
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-001.patch, OOZIE-3160-002.patch, OOZIE-3160-003.patch,
> OOZIE-3160-POC01.patch, OOZIE-3160-POC02.patch, OOZIE-3160-POC02.patch,
> OOZIE-3160-POC03.patch, OOZIE-3160-POC04.patch, OOZIE-3160-POC05.patch,
> PriorityDelayQueue improvement - OOZIE-3160.pdf
>
>
> 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
[
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-003.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: Peter Bacsko
>Priority: Major
> Attachments: 11.png, 22.png,
> OOZIE-3160-001.patch, OOZIE-3160-002.patch, OOZIE-3160-003.patch,
> OOZIE-3160-POC01.patch, OOZIE-3160-POC02.patch, OOZIE-3160-POC02.patch,
> OOZIE-3160-POC03.patch, OOZIE-3160-POC04.patch, OOZIE-3160-POC05.patch,
> PriorityDelayQueue improvement - OOZIE-3160.pdf
>
>
> 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-3264) Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
[
https://issues.apache.org/jira/browse/OOZIE-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Salamon reassigned OOZIE-3264:
-
Assignee: Andras Salamon
> Flaky test TestCoordMaterializeTransitionXCommand#testLastOnlyMaterialization
> -
>
> Key: OOZIE-3264
> URL: https://issues.apache.org/jira/browse/OOZIE-3264
> Project: Oozie
> Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Andras Salamon
>Priority: Major
>
> The test {{testLastOnlyMaterialization}} failed.
> {noformat}
> junit.framework.AssertionFailedError: expected: but was:
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.checkCoordActionsStatus(TestCoordMaterializeTransitionXCommand.java:1415)
> at
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testLastOnlyMaterialization(TestCoordMaterializeTransitionXCommand.java:1114)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (97 issues) Subscriber: ooziedaily Key Summary OOZIE-3329 test-patch-30-distro improvement https://issues.apache.org/jira/browse/OOZIE-3329 OOZIE-3326 Sqoop Action should support tez delegation tokens for hive-import https://issues.apache.org/jira/browse/OOZIE-3326 OOZIE-3320 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3320 OOZIE-3319 Log SSH action callback error output https://issues.apache.org/jira/browse/OOZIE-3319 OOZIE-3318 Fix Javadoc check in the pre-commit https://issues.apache.org/jira/browse/OOZIE-3318 OOZIE-3317 Fix false positive precommit reports https://issues.apache.org/jira/browse/OOZIE-3317 OOZIE-3301 Update NOTICE file https://issues.apache.org/jira/browse/OOZIE-3301 OOZIE-3298 OYA: external ID is not filled properly and failing MR job is treated as SUCCEEDED https://issues.apache.org/jira/browse/OOZIE-3298 OOZIE-3274 Remove slf4j https://issues.apache.org/jira/browse/OOZIE-3274 OOZIE-3266 Coord action rerun support RERUN_SKIP_NODES option https://issues.apache.org/jira/browse/OOZIE-3266 OOZIE-3265 properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to appear together https://issues.apache.org/jira/browse/OOZIE-3265 OOZIE-3256 refactor OozieCLI class https://issues.apache.org/jira/browse/OOZIE-3256 OOZIE-3249 [tools] Instrumentation log parser https://issues.apache.org/jira/browse/OOZIE-3249 OOZIE-3229 Improved filtering options in V2SLAServlet https://issues.apache.org/jira/browse/OOZIE-3229 OOZIE-3218 Oozie Sqoop action with command splits the select clause into multiple parts due to delimiter being space https://issues.apache.org/jira/browse/OOZIE-3218 OOZIE-3199 Let system property restriction configurable https://issues.apache.org/jira/browse/OOZIE-3199 OOZIE-3196 Authorization: restrict world readability by user https://issues.apache.org/jira/browse/OOZIE-3196 OOZIE-3194 Oozie should set proper permissions to sharelib after upload https://issues.apache.org/jira/browse/OOZIE-3194 OOZIE-3186 Oozie is unable to use configuration linked using jceks://file/... https://issues.apache.org/jira/browse/OOZIE-3186 OOZIE-3179 Adding a configurable config-default.xml location to a workflow https://issues.apache.org/jira/browse/OOZIE-3179 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting https://issues.apache.org/jira/browse/OOZIE-3160 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-3061 Kill only those child jobs which are not already killed https://issues.apache.org/jira/browse/OOZIE-3061 OOZIE-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2949 Escape quotes whitespaces in Sqoop field https://issues.apache.org/jira/browse/OOZIE-2949 OOZIE-2927 Append new line character for Hive2 query using query tag https://issues.apache.org/jira/browse/OOZIE-2927 OOZIE-2877 Oozie Git Action https://issues.apache.org/jira/browse/OOZIE-2877 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
