[jira] [Commented] (OOZIE-3366) Update workflow status and subworkflow status on suspend command
[
https://issues.apache.org/jira/browse/OOZIE-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648528#comment-16648528
]
Hadoop QA commented on OOZIE-3366:
--
Testing JIRA OOZIE-3366
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 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3058
.{color:orange}Tests failed at first run:{color}
TestSubWorkflowActionExecutor#testSubWorkflowParentSuspend
.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/891/
> Update workflow status and subworkflow status on suspend command
>
>
> Key: OOZIE-3366
> URL: https://issues.apache.org/jira/browse/OOZIE-3366
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3366-1.patch, OOZIE-3366-2.patch
>
>
> Currently, when subworkflow gets suspended, its corresponding workflow status
> is not updated correctly. Also, when a coord is suspended, the subworkflows
> are not suspended. We need to fix this.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Failed: OOZIE-3366 PreCommit Build #891
Jira: https://issues.apache.org/jira/browse/OOZIE-3366
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/891/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 2.35 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive2].
[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 [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2560 bytes
[TRACE] Full summary file size is 1471 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-3366
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 3 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)
WARNING: the current HEAD has 100 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 no new bugs found in total.
+1 There are no new bugs found in [fluent-job/fluent-job-api].
+1 There are no new bugs found in [core].
+1 There are no new bugs found in [server].
+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 [examples].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/git].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/spark].
+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/hive2].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [webapp].
+1 There are no new bugs found in [tools].
+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: 3058
Tests failed at first run:
TestSubWorkflowActionExecutor#testSubWorkflowParentSuspend
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/891/
Adding comment to JIRA
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0100 34510 0 100 3451 0 3716 --:--:-- --:--:-- --:--:--
3714{"self":"https://issues.apache.org/jira/rest/api/2/issue/13191069/comment/16648528","id":"16648528","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
QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA
Success: OOZIE-3364 PreCommit Build #889
Jira: https://issues.apache.org/jira/browse/OOZIE-3364 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/889/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 1.89 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 [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 [webapp]. [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 [fluent-job/fluent-job-api]. [INFO] There are no new bugs found totally]. [TRACE] FindBugs diffs checked and reports created [TRACE] Summary file size is 2560 bytes [TRACE] Full summary file size is 1471 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-3364 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) WARNING: the current HEAD has 100 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 no new bugs found in total. +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/pig]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/spark]. +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/hive2]. +1 There are no new bugs found in [server]. +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 [docs]. +1 There are no new bugs found in [webapp]. +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 [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: 3056 Tests failed at first run: TestWorkflowActionRetryInfoXCommand#testRetryConsoleUrlForked 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/889/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 34540 0 100 3454 0 4789 --:--:-- --:--:-- --:--:--
[jira] [Commented] (OOZIE-3364) Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
[
https://issues.apache.org/jira/browse/OOZIE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648524#comment-16648524
]
Hadoop QA commented on OOZIE-3364:
--
Testing JIRA OOZIE-3364
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:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [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/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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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: 3056
.{color:orange}Tests failed at first run:{color}
TestWorkflowActionRetryInfoXCommand#testRetryConsoleUrlForked
.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/889/
> Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
> --
>
> Key: OOZIE-3364
> URL: https://issues.apache.org/jira/browse/OOZIE-3364
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3364-1.patch, OOZIE-3364-2.patch
>
>
> User restarted a bundle with the following command
> {noformat}
> oozie job -rerun 1234-1234-oozie-B -date 2018-03-29T23:55Z::2018-04-03T00:00Z
> -refresh
> {noformat}
> The coordinators run in indeterminate order. User thought if he don't specify
> the order of the coordinators to run it is FIFO by default.
> ([https://oozie.apache.org/docs/3.1.3-incubating/CoordinatorFunctionalSpec.html#a5.1._Synchronous_Datasets])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Failed: OOZIE-3367 PreCommit Build #890
Jira: https://issues.apache.org/jira/browse/OOZIE-3367
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/890/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 1.89 MB...]
[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 [fluent-job/fluent-job-api].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2560 bytes
[TRACE] Full summary file size is 1471 bytes
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
removed
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build@2/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
xargs: Warning: a NUL character occurred in the input. It cannot be passed
through in the argument list. Did you mean to use the --null option?
Running test-patch task DISTRO
Testing JIRA OOZIE-3367
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)
WARNING: the current HEAD has 100 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 no new bugs found in total.
+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/pig].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/git].
+1 There are no new bugs found in [sharelib/spark].
+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/hive2].
+1 There are no new bugs found in [server].
+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 [docs].
+1 There are no new bugs found in [webapp].
+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 [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: 3057
Tests failed : 1
Tests in error : 0
Tests timed out : 0
-1 [ERROR] There are [1] test failures in [core]. Listing only the first [5]
ones
testRetryConsoleUrlForked:org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand
Check console output for the full list of errors/failures
+1 DISTRO
+1 distro tarball builds with the patch
-1 Overall result, please check the reported -1(s)
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/890/
Adding comment to JIRA
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13191090/comment/16648523","id":"16648523","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
QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA
OOZIE-3367\n\nCleaning local git
workspace\n\n\n\n{color:green}+1
[jira] [Commented] (OOZIE-3367) Using && in EL expressions in oozie bundle.xml files generates parse errors
[
https://issues.apache.org/jira/browse/OOZIE-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648523#comment-16648523
]
Hadoop QA commented on OOZIE-3367:
--
Testing JIRA OOZIE-3367
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:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [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/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/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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:red}-1 TESTS{color}
.Tests run: 3057
.Tests failed : 1
.Tests in error : 0
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [1] test failures in [core]. Listing
only the first [5] ones
testRetryConsoleUrlForked:org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand
Check console output for the full list of errors/failures
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/890/
> Using && in EL expressions in oozie bundle.xml files generates parse errors
> ---
>
> Key: OOZIE-3367
> URL: https://issues.apache.org/jira/browse/OOZIE-3367
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3367-1.patch, OOZIE-3367-2.patch
>
>
> [~wla...@yahoo-inc.com]reported -
> I need to put a logical AND into an expression in an oozie bundle (in the
> enabled flag on the coordinator). When I try "{{A && B}}", oozie gives me a
> perfectly understandable error about this being invalid XML ({{XML schema
> error, The entity name must immediately follow the '&' in the entity
> reference.}}). But when I try to replace this with an XML entity ({{A &&
> B}}), I get an unexpected error that seems to indicate that a space (or
> something else) is getting injected unexpectedly into my expression:
> {noformat}
> Bundle Job submission Error: [E1004: Expression language evaluation error,
> Encountered "&", expected one of ["}", ".", ">", "gt",
[jira] [Commented] (OOZIE-3366) Update workflow status and subworkflow status on suspend command
[ https://issues.apache.org/jira/browse/OOZIE-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648405#comment-16648405 ] Hadoop QA commented on OOZIE-3366: -- PreCommit-OOZIE-Build started > Update workflow status and subworkflow status on suspend command > > > Key: OOZIE-3366 > URL: https://issues.apache.org/jira/browse/OOZIE-3366 > Project: Oozie > Issue Type: Bug >Reporter: Satish Subhashrao Saley >Assignee: Satish Subhashrao Saley >Priority: Major > Attachments: OOZIE-3366-1.patch, OOZIE-3366-2.patch > > > Currently, when subworkflow gets suspended, its corresponding workflow status > is not updated correctly. Also, when a coord is suspended, the subworkflows > are not suspended. We need to fix this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3367) Using && in EL expressions in oozie bundle.xml files generates parse errors
[
https://issues.apache.org/jira/browse/OOZIE-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648404#comment-16648404
]
Hadoop QA commented on OOZIE-3367:
--
PreCommit-OOZIE-Build started
> Using && in EL expressions in oozie bundle.xml files generates parse errors
> ---
>
> Key: OOZIE-3367
> URL: https://issues.apache.org/jira/browse/OOZIE-3367
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3367-1.patch, OOZIE-3367-2.patch
>
>
> [~wla...@yahoo-inc.com]reported -
> I need to put a logical AND into an expression in an oozie bundle (in the
> enabled flag on the coordinator). When I try "{{A && B}}", oozie gives me a
> perfectly understandable error about this being invalid XML ({{XML schema
> error, The entity name must immediately follow the '&' in the entity
> reference.}}). But when I try to replace this with an XML entity ({{A &&
> B}}), I get an unexpected error that seems to indicate that a space (or
> something else) is getting injected unexpectedly into my expression:
> {noformat}
> Bundle Job submission Error: [E1004: Expression language evaluation error,
> Encountered "&", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq",
> "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%",
> "mod", "and", "&&", "or", "||", ":", "(", "?"]]
> {noformat}
> Any idea how I can get the expression "A && B" to be parsed correctly in an
> oozie bundle.xml file?
> It turned out to be a bug in Oozie.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3364) Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
[
https://issues.apache.org/jira/browse/OOZIE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648403#comment-16648403
]
Hadoop QA commented on OOZIE-3364:
--
PreCommit-OOZIE-Build started
> Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
> --
>
> Key: OOZIE-3364
> URL: https://issues.apache.org/jira/browse/OOZIE-3364
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3364-1.patch, OOZIE-3364-2.patch
>
>
> User restarted a bundle with the following command
> {noformat}
> oozie job -rerun 1234-1234-oozie-B -date 2018-03-29T23:55Z::2018-04-03T00:00Z
> -refresh
> {noformat}
> The coordinators run in indeterminate order. User thought if he don't specify
> the order of the coordinators to run it is FIFO by default.
> ([https://oozie.apache.org/docs/3.1.3-incubating/CoordinatorFunctionalSpec.html#a5.1._Synchronous_Datasets])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3364) Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
[
https://issues.apache.org/jira/browse/OOZIE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648393#comment-16648393
]
Satish Subhashrao Saley commented on OOZIE-3364:
{quote}bq.{color:#FF}-1{color} the patch contains 1 line(s) longer than 132
characters
{quote}
updated patch
> Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
> --
>
> Key: OOZIE-3364
> URL: https://issues.apache.org/jira/browse/OOZIE-3364
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3364-1.patch, OOZIE-3364-2.patch
>
>
> User restarted a bundle with the following command
> {noformat}
> oozie job -rerun 1234-1234-oozie-B -date 2018-03-29T23:55Z::2018-04-03T00:00Z
> -refresh
> {noformat}
> The coordinators run in indeterminate order. User thought if he don't specify
> the order of the coordinators to run it is FIFO by default.
> ([https://oozie.apache.org/docs/3.1.3-incubating/CoordinatorFunctionalSpec.html#a5.1._Synchronous_Datasets])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3364) Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
[
https://issues.apache.org/jira/browse/OOZIE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Subhashrao Saley updated OOZIE-3364:
---
Attachment: OOZIE-3364-2.patch
> Rerunning Oozie bundle jobs starts the coordinators in indeterminate order
> --
>
> Key: OOZIE-3364
> URL: https://issues.apache.org/jira/browse/OOZIE-3364
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3364-1.patch, OOZIE-3364-2.patch
>
>
> User restarted a bundle with the following command
> {noformat}
> oozie job -rerun 1234-1234-oozie-B -date 2018-03-29T23:55Z::2018-04-03T00:00Z
> -refresh
> {noformat}
> The coordinators run in indeterminate order. User thought if he don't specify
> the order of the coordinators to run it is FIFO by default.
> ([https://oozie.apache.org/docs/3.1.3-incubating/CoordinatorFunctionalSpec.html#a5.1._Synchronous_Datasets])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3366) Update workflow status and subworkflow status on suspend command
[
https://issues.apache.org/jira/browse/OOZIE-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648381#comment-16648381
]
Satish Subhashrao Saley commented on OOZIE-3366:
bq. {color:#FF}-1{color} the patch contains 4 line(s) longer than 132
characters
Updated patch
> Update workflow status and subworkflow status on suspend command
>
>
> Key: OOZIE-3366
> URL: https://issues.apache.org/jira/browse/OOZIE-3366
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3366-1.patch, OOZIE-3366-2.patch
>
>
> Currently, when subworkflow gets suspended, its corresponding workflow status
> is not updated correctly. Also, when a coord is suspended, the subworkflows
> are not suspended. We need to fix this.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3366) Update workflow status and subworkflow status on suspend command
[ https://issues.apache.org/jira/browse/OOZIE-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Subhashrao Saley updated OOZIE-3366: --- Attachment: OOZIE-3366-2.patch > Update workflow status and subworkflow status on suspend command > > > Key: OOZIE-3366 > URL: https://issues.apache.org/jira/browse/OOZIE-3366 > Project: Oozie > Issue Type: Bug >Reporter: Satish Subhashrao Saley >Assignee: Satish Subhashrao Saley >Priority: Major > Attachments: OOZIE-3366-1.patch, OOZIE-3366-2.patch > > > Currently, when subworkflow gets suspended, its corresponding workflow status > is not updated correctly. Also, when a coord is suspended, the subworkflows > are not suspended. We need to fix this. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3367) Using && in EL expressions in oozie bundle.xml files generates parse errors
[
https://issues.apache.org/jira/browse/OOZIE-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648370#comment-16648370
]
Satish Subhashrao Saley commented on OOZIE-3367:
bq. {color:#FF}-1{color} the patch contains 1 line(s) longer than 132
characters
Updated patch to solve this.
> Using && in EL expressions in oozie bundle.xml files generates parse errors
> ---
>
> Key: OOZIE-3367
> URL: https://issues.apache.org/jira/browse/OOZIE-3367
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3367-1.patch, OOZIE-3367-2.patch
>
>
> [~wla...@yahoo-inc.com]reported -
> I need to put a logical AND into an expression in an oozie bundle (in the
> enabled flag on the coordinator). When I try "{{A && B}}", oozie gives me a
> perfectly understandable error about this being invalid XML ({{XML schema
> error, The entity name must immediately follow the '&' in the entity
> reference.}}). But when I try to replace this with an XML entity ({{A &&
> B}}), I get an unexpected error that seems to indicate that a space (or
> something else) is getting injected unexpectedly into my expression:
> {noformat}
> Bundle Job submission Error: [E1004: Expression language evaluation error,
> Encountered "&", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq",
> "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%",
> "mod", "and", "&&", "or", "||", ":", "(", "?"]]
> {noformat}
> Any idea how I can get the expression "A && B" to be parsed correctly in an
> oozie bundle.xml file?
> It turned out to be a bug in Oozie.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3367) Using && in EL expressions in oozie bundle.xml files generates parse errors
[
https://issues.apache.org/jira/browse/OOZIE-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Subhashrao Saley updated OOZIE-3367:
---
Attachment: OOZIE-3367-2.patch
> Using && in EL expressions in oozie bundle.xml files generates parse errors
> ---
>
> Key: OOZIE-3367
> URL: https://issues.apache.org/jira/browse/OOZIE-3367
> Project: Oozie
> Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
>Priority: Major
> Attachments: OOZIE-3367-1.patch, OOZIE-3367-2.patch
>
>
> [~wla...@yahoo-inc.com]reported -
> I need to put a logical AND into an expression in an oozie bundle (in the
> enabled flag on the coordinator). When I try "{{A && B}}", oozie gives me a
> perfectly understandable error about this being invalid XML ({{XML schema
> error, The entity name must immediately follow the '&' in the entity
> reference.}}). But when I try to replace this with an XML entity ({{A &&
> B}}), I get an unexpected error that seems to indicate that a space (or
> something else) is getting injected unexpectedly into my expression:
> {noformat}
> Bundle Job submission Error: [E1004: Expression language evaluation error,
> Encountered "&", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq",
> "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%",
> "mod", "and", "&&", "or", "||", ":", "(", "?"]]
> {noformat}
> Any idea how I can get the expression "A && B" to be parsed correctly in an
> oozie bundle.xml file?
> It turned out to be a bug in Oozie.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OOZIE-3363) Hadoop's cleanup of local directory in uber mode causing failures for sqoop actions
[
https://issues.apache.org/jira/browse/OOZIE-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satish Subhashrao Saley reassigned OOZIE-3363:
--
Assignee: (was: Satish Subhashrao Saley)
> Hadoop's cleanup of local directory in uber mode causing failures for sqoop
> actions
> ---
>
> Key: OOZIE-3363
> URL: https://issues.apache.org/jira/browse/OOZIE-3363
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0, 5.0.0
>Reporter: Clemens Valiente
>Priority: Blocker
>
> See related task OOZIE-2536 and discussion
> https://issues.apache.org/jira/browse/OOZIE-2536?focusedCommentId=16617206=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16617206
> the same issue cleaning up local directories also affects sqoop jobs that
> create the sqoop.xml file inbetween.
> {code:java}
> 2018-09-15 00:31:09,416 [AsyncDispatcher event handler] INFO
> org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl - Num completed Tasks: 1
> 2018-09-15 00:31:09,417 [AsyncDispatcher event handler] INFO
> org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl -
> job_1535972033593_259806Job Transitioned from RUNNING to COMMITTING
> 2018-09-15 00:31:09,419 [CommitterEvent Processor #1] INFO
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler - Processing
> the event EventType: JOB_COMMIT
> 2018-09-15 00:31:09,455 [uber-SubtaskRunner] WARN
> org.apache.hadoop.mapred.LocalContainerLauncher - Unable to delete
> unexpected local file/dir .action.xml.crc: insufficient permissions?
> 2018-09-15 00:31:09,455 [uber-SubtaskRunner] WARN
> org.apache.hadoop.mapred.LocalContainerLauncher - Unable to delete
> unexpected local file/dir .action.xml.crc: insufficient permissions?
> 2018-09-15 00:31:09,459 [CommitterEvent Processor #1] FATAL
> org.apache.hadoop.conf.Configuration - error parsing conf sqoop-site.xml
> java.io.FileNotFoundException:
> /appdata/hdfs/v7/yarn/nm/usercache/SEM/appcache/application_1535972033593_259806/container_e100_1535972033593_259806_01_01/sqoop-site.xml
> (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:146)
> at java.io.FileInputStream.(FileInputStream.java:101)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2483)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2554)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2507)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2413)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:984)
> at
> org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:1034)
> at org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1254)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:804)
> at
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.touchz(CommitterEventHandler.java:268)
> at
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.handleJobCommit(CommitterEventHandler.java:282)
> at
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.run(CommitterEventHandler.java:237)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3363) Hadoop's cleanup of local directory in uber mode causing failures for sqoop actions
[
https://issues.apache.org/jira/browse/OOZIE-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648118#comment-16648118
]
Satish Subhashrao Saley commented on OOZIE-3363:
For workaround, set following property for sqoop action
{code:java}
oozie.launcher.mapreduce.job.ubertask.enable
false
{code}
> Hadoop's cleanup of local directory in uber mode causing failures for sqoop
> actions
> ---
>
> Key: OOZIE-3363
> URL: https://issues.apache.org/jira/browse/OOZIE-3363
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0, 5.0.0
>Reporter: Clemens Valiente
>Assignee: Satish Subhashrao Saley
>Priority: Blocker
>
> See related task OOZIE-2536 and discussion
> https://issues.apache.org/jira/browse/OOZIE-2536?focusedCommentId=16617206=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16617206
> the same issue cleaning up local directories also affects sqoop jobs that
> create the sqoop.xml file inbetween.
> {code:java}
> 2018-09-15 00:31:09,416 [AsyncDispatcher event handler] INFO
> org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl - Num completed Tasks: 1
> 2018-09-15 00:31:09,417 [AsyncDispatcher event handler] INFO
> org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl -
> job_1535972033593_259806Job Transitioned from RUNNING to COMMITTING
> 2018-09-15 00:31:09,419 [CommitterEvent Processor #1] INFO
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler - Processing
> the event EventType: JOB_COMMIT
> 2018-09-15 00:31:09,455 [uber-SubtaskRunner] WARN
> org.apache.hadoop.mapred.LocalContainerLauncher - Unable to delete
> unexpected local file/dir .action.xml.crc: insufficient permissions?
> 2018-09-15 00:31:09,455 [uber-SubtaskRunner] WARN
> org.apache.hadoop.mapred.LocalContainerLauncher - Unable to delete
> unexpected local file/dir .action.xml.crc: insufficient permissions?
> 2018-09-15 00:31:09,459 [CommitterEvent Processor #1] FATAL
> org.apache.hadoop.conf.Configuration - error parsing conf sqoop-site.xml
> java.io.FileNotFoundException:
> /appdata/hdfs/v7/yarn/nm/usercache/SEM/appcache/application_1535972033593_259806/container_e100_1535972033593_259806_01_01/sqoop-site.xml
> (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:146)
> at java.io.FileInputStream.(FileInputStream.java:101)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2483)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2554)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2507)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2413)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:984)
> at
> org.apache.hadoop.conf.Configuration.getTrimmed(Configuration.java:1034)
> at org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1254)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:804)
> at
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.touchz(CommitterEventHandler.java:268)
> at
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.handleJobCommit(CommitterEventHandler.java:282)
> at
> org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler$EventProcessor.run(CommitterEventHandler.java:237)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3137) Add support for log4j2 in HiveMain
[ https://issues.apache.org/jira/browse/OOZIE-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16647758#comment-16647758 ] Hadoop QA commented on OOZIE-3137: -- PreCommit-OOZIE-Build started > Add support for log4j2 in HiveMain > -- > > Key: OOZIE-3137 > URL: https://issues.apache.org/jira/browse/OOZIE-3137 > Project: Oozie > Issue Type: Sub-task >Reporter: Attila Sasvari >Assignee: Peter Bacsko >Priority: Major > Attachments: OOZIE-3137-001.patch > > > Hive 2.0 is using log4j 2 (HIVE-11304). In order to support Hadoop 3 we > should add a mechanism to configure log4j 2 in HiveMain. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3355) Regex based search option for searching workflows in the WFM-View of Ambari
[
https://issues.apache.org/jira/browse/OOZIE-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16647712#comment-16647712
]
Mate Juhasz commented on OOZIE-3355:
[~andras.piros], these are the available filter parameters from the ambari wfm:
* name
* id (oozie job id)
* user (job submitter user)
* status (SUCCEEDED, RUNNING, FAILED, KILLED, SUSPENDED)
* jobtype (wf, coord, bundles)
* startCreatedTime
* endCreatedTime
The offset and len parameters are used for paginating the results.
* len - always 20
* offset - always (page number - 1) * len
The filter parameter is filled with each of the user defined conditions, but
these seem to be in OR relation instead of AND:
_filter=status=SUCCEEDED;name=mr-wf_
Another observation about time filtering, that the wfm shows the local time,
but the filtering has to be done in GMT as oozie works.
> Regex based search option for searching workflows in the WFM-View of Ambari
> ---
>
> Key: OOZIE-3355
> URL: https://issues.apache.org/jira/browse/OOZIE-3355
> Project: Oozie
> Issue Type: New Feature
> Components: bundle, coordinator, core, tools, ui, workflow
>Affects Versions: 4.2.0
>Reporter: Krishnadevan Purushothaman
>Priority: Critical
>
> *Challenge faced :*
> _{color:#d04437}In the WFM view of ambari, there is no Filter option
> available to search for the Workflows. In order to search for the desired
> workflow, one has to type the full name of workflow,coordinator,bundles else
> it does not return anything which becomes a time-consuming job.{color}_
> *Feature description:*
> _{color:#14892c}There is a need for Regex based filter option in order to
> search the workflows without the need of entering the complete name of the
> workflow,coordinator,bundles rather by just typing the first three letters of
> the work post which it should populate suggestions based on the first three
> letters of the workflow,coordinator,bundles through which we can refine and
> optimize the searching mechanism.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (95 issues) Subscriber: ooziedaily Key Summary 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-3365 Workflow and Coord Action status remains RUNNING after rerun https://issues.apache.org/jira/browse/OOZIE-3365 OOZIE-3364 Rerunning Oozie bundle jobs starts the coordinators in indeterminate order https://issues.apache.org/jira/browse/OOZIE-3364 OOZIE-3361 Document embedded XML job submission mode https://issues.apache.org/jira/browse/OOZIE-3361 OOZIE-3338 Remove SVN references https://issues.apache.org/jira/browse/OOZIE-3338 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-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-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-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-3120 maven-assembly-plugin fails when bumped from 2.2.1 https://issues.apache.org/jira/browse/OOZIE-3120 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-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-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
