[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (108 issues) Subscriber: ooziedaily Key Summary OOZIE-3189 Update the release script and wiki page to use sha512 instead of md5 https://issues.apache.org/jira/browse/OOZIE-3189 OOZIE-3186 Oozie is unable to use configuration linked using jceks://file/... https://issues.apache.org/jira/browse/OOZIE-3186 OOZIE-3185 Conflicting JARs org.apache.derby exist in Oozie https://issues.apache.org/jira/browse/OOZIE-3185 OOZIE-3179 Adding a configurable config-default.xml location to a workflow https://issues.apache.org/jira/browse/OOZIE-3179 OOZIE-3176 Oozie-core fails with checkstyle errors. https://issues.apache.org/jira/browse/OOZIE-3176 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 OOZIE-3134 Potential inconsistency between the in-memory SLA map and the Oozie database https://issues.apache.org/jira/browse/OOZIE-3134 OOZIE-3109 Escape log-streaming's HTML-specific characters https://issues.apache.org/jira/browse/OOZIE-3109 OOZIE-3105 testJMXInstrumentation from the org.apache.oozie.util.TestMetricsInstrumentation class is flaky https://issues.apache.org/jira/browse/OOZIE-3105 OOZIE-3094 fix for grammar mistake https://issues.apache.org/jira/browse/OOZIE-3094 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-3002 address findbugs errors in client lib https://issues.apache.org/jira/browse/OOZIE-3002 OOZIE-2975 code clean up in pig sharelib, replace Exception with more explicit, add try with resources, StringBuilder instead of StringBuffer https://issues.apache.org/jira/browse/OOZIE-2975 OOZIE-2957 Documentation states that starting a coordinator is possible https://issues.apache.org/jira/browse/OOZIE-2957 OOZIE-2956 Fix Findbugs warnings related to reliance on default encoding in oozie-core https://issues.apache.org/jira/browse/OOZIE-2956 OOZIE-2955 Fix Findbugs warnings related to reliance on default encoding in oozie-client https://issues.apache.org/jira/browse/OOZIE-2955 OOZIE-2954 Fix Checkstyle issues in oozie-client https://issues.apache.org/jira/browse/OOZIE-2954 OOZIE-2953 Fix Checkstyle issues in oozie-tools https://issues.apache.org/jira/browse/OOZIE-2953 OOZIE-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2949 Escape quotes whitespaces in Sqoop field https://issues.apache.org/jira/browse/OOZIE-2949 OOZIE-2942 Fix Findbugs warnings in oozie-examples https://issues.apache.org/jira/browse/OOZIE-2942 OOZIE-2937 Remove redundant groupId from the child pom's https://issues.apache.org/jira/browse/OOZIE-2937 OOZIE-2934 Fix "Exceptional return value of java.io.File.mkdirs() ignored" Findbugs error in oozie-sharelib-spark https://issues.apache.org/jira/browse/OOZIE-2934 OOZIE-2927 Append new line character for Hive2 query using query tag https://issues.apache.org/jira/browse/OOZIE-2927 OOZIE-2914 Consolidate Trim https://issues.apache.org/jira/browse/OOZIE-2914 OOZIE-2883 OOZIE throw the error "Missing [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups] property" https://issues.apache.org/jira/browse/OOZIE-2883 OOZIE-2877 Oozie Git Action https://issues.apache.org/jira/browse/OOZIE-2877 OOZIE-2867 Timezone handling for Coordinators: emphasize "Continent/City" format https://issues.apache.org/jira/browse/OOZIE-2867 OOZIE-2834 ParameterVerifier logging non-useful warning for workflow definition https://issues.apache.org/jira/browse/OOZIE-2834 OOZIE-2833 when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes. https://issues.apache.org/jira/browse/OOZIE-2833 OOZIE-2829 Improve sharelib upload to accept multiple source folders
[jira] [Commented] (OOZIE-3189) Update the release script and wiki page to use sha512 instead of md5
[ https://issues.apache.org/jira/browse/OOZIE-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390491#comment-16390491 ] Robert Kanter commented on OOZIE-3189: -- Test failures unrelated (no code changes). > Update the release script and wiki page to use sha512 instead of md5 > > > Key: OOZIE-3189 > URL: https://issues.apache.org/jira/browse/OOZIE-3189 > Project: Oozie > Issue Type: Improvement > Components: scripts >Reporter: Robert Kanter >Assignee: Robert Kanter >Priority: Major > Fix For: 5.0.0 > > Attachments: OOZIE-3189.001.patch > > > Apache has updated it's policy on the release signatures, as per it's website > [here|https://www.apache.org/dev/release-distribution#sigs-and-sums] and a > recent email. Basically, all future releases should be providing a sha512 > checksum instead of an md5 one. > There are two tasks: > # Update the release script to use sha512 instead of md5 > [https://github.com/apache/oozie/blob/master/bin/create-release-artifact#L71] > [https://www.apache.org/dev/release-signing#sha-checksum] > # Update the wiki (requires committer/pmc permissions?) > [https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release] > While we're updating the wiki, we should add details on: > # Making sure the gpg key used for signing releases is 4096 bit RSA > # Publishing your gpg public key to a key server > ([https://www.apache.org/dev/release-signing#keyserver]) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Failed: OOZIE-3189 PreCommit Build #417
Jira: https://issues.apache.org/jira/browse/OOZIE-3189
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/417/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 1.73 MB...]
[DEBUG] There are no new bugs found in [sharelib/sqoop].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [tools].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [core].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2253 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
removed
[TRACE] File
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
removed
Running test-patch task BACKWARDS_COMPATIBILITY
Running test-patch task TESTS
Running test-patch task DISTRO
Testing JIRA OOZIE-3189
Cleaning local git workspace
+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
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 [docs].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [sharelib/hcatalog].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [webapp].
+1 There are no new bugs found in [examples].
+1 There are no new bugs found in [client].
+1 There are no new bugs found in [tools].
+1 There are no new bugs found in [server].
+1 There are no new bugs found in [core].
+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: 2092
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestHiveActionExecutor#testHiveAction
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)
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/417/
Adding comment to JIRA
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0100 31790 0 100 3179 0 3181 --:--:-- --:--:-- --:--:--
3179{"self":"https://issues.apache.org/jira/rest/api/2/issue/13142614/comment/16390479","id":"16390479","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
at hadoop dot apache dot
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
[jira] [Commented] (OOZIE-3189) Update the release script and wiki page to use sha512 instead of md5
[
https://issues.apache.org/jira/browse/OOZIE-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390479#comment-16390479
]
Hadoop QA commented on OOZIE-3189:
--
Testing JIRA OOZIE-3189
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
.{color:red}WARNING{color}: the current HEAD has 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 [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2092
.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestHiveActionExecutor#testHiveAction
.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}
{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/417/
> Update the release script and wiki page to use sha512 instead of md5
>
>
> Key: OOZIE-3189
> URL: https://issues.apache.org/jira/browse/OOZIE-3189
> Project: Oozie
> Issue Type: Improvement
> Components: scripts
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3189.001.patch
>
>
> Apache has updated it's policy on the release signatures, as per it's website
> [here|https://www.apache.org/dev/release-distribution#sigs-and-sums] and a
> recent email. Basically, all future releases should be providing a sha512
> checksum instead of an md5 one.
> There are two tasks:
> # Update the release script to use sha512 instead of md5
> [https://github.com/apache/oozie/blob/master/bin/create-release-artifact#L71]
> [https://www.apache.org/dev/release-signing#sha-checksum]
> # Update the wiki (requires committer/pmc permissions?)
> [https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release]
> While we're updating the wiki, we should add details on:
> # Making sure the gpg key used for signing releases is 4096 bit RSA
> # Publishing your gpg public key to a key server
> ([https://www.apache.org/dev/release-signing#keyserver])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3189) Update the release script and wiki page to use sha512 instead of md5
[ https://issues.apache.org/jira/browse/OOZIE-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390341#comment-16390341 ] Hadoop QA commented on OOZIE-3189: -- PreCommit-OOZIE-Build started > Update the release script and wiki page to use sha512 instead of md5 > > > Key: OOZIE-3189 > URL: https://issues.apache.org/jira/browse/OOZIE-3189 > Project: Oozie > Issue Type: Improvement > Components: scripts >Reporter: Robert Kanter >Assignee: Robert Kanter >Priority: Major > Fix For: 5.0.0 > > Attachments: OOZIE-3189.001.patch > > > Apache has updated it's policy on the release signatures, as per it's website > [here|https://www.apache.org/dev/release-distribution#sigs-and-sums] and a > recent email. Basically, all future releases should be providing a sha512 > checksum instead of an md5 one. > There are two tasks: > # Update the release script to use sha512 instead of md5 > [https://github.com/apache/oozie/blob/master/bin/create-release-artifact#L71] > [https://www.apache.org/dev/release-signing#sha-checksum] > # Update the wiki (requires committer/pmc permissions?) > [https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release] > While we're updating the wiki, we should add details on: > # Making sure the gpg key used for signing releases is 4096 bit RSA > # Publishing your gpg public key to a key server > ([https://www.apache.org/dev/release-signing#keyserver]) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3189) Update the release script and wiki page to use sha512 instead of md5
[
https://issues.apache.org/jira/browse/OOZIE-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390339#comment-16390339
]
Robert Kanter commented on OOZIE-3189:
--
The patch replaces the code generating the md5 with code generating the sha512
as prescribed by the ASF. I also ran ShellCheck and fixed a bunch of minor
things it was complaining about. I did run into a complication because the
command to generate the sha512 has to use a {{>}} to redirect stdout, and that
doesn't work so great with our {{run}} function. I worked around it by
duplicating a few things, but if there's a cleaner way, let me know.
I'll update the wiki shortly.
> Update the release script and wiki page to use sha512 instead of md5
>
>
> Key: OOZIE-3189
> URL: https://issues.apache.org/jira/browse/OOZIE-3189
> Project: Oozie
> Issue Type: Improvement
> Components: scripts
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3189.001.patch
>
>
> Apache has updated it's policy on the release signatures, as per it's website
> [here|https://www.apache.org/dev/release-distribution#sigs-and-sums] and a
> recent email. Basically, all future releases should be providing a sha512
> checksum instead of an md5 one.
> There are two tasks:
> # Update the release script to use sha512 instead of md5
> [https://github.com/apache/oozie/blob/master/bin/create-release-artifact#L71]
> [https://www.apache.org/dev/release-signing#sha-checksum]
> # Update the wiki (requires committer/pmc permissions?)
> [https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release]
> While we're updating the wiki, we should add details on:
> # Making sure the gpg key used for signing releases is 4096 bit RSA
> # Publishing your gpg public key to a key server
> ([https://www.apache.org/dev/release-signing#keyserver])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3189) Update the release script and wiki page to use sha512 instead of md5
[ https://issues.apache.org/jira/browse/OOZIE-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-3189: - Attachment: OOZIE-3189.001.patch > Update the release script and wiki page to use sha512 instead of md5 > > > Key: OOZIE-3189 > URL: https://issues.apache.org/jira/browse/OOZIE-3189 > Project: Oozie > Issue Type: Improvement > Components: scripts >Reporter: Robert Kanter >Assignee: Robert Kanter >Priority: Major > Fix For: 5.0.0 > > Attachments: OOZIE-3189.001.patch > > > Apache has updated it's policy on the release signatures, as per it's website > [here|https://www.apache.org/dev/release-distribution#sigs-and-sums] and a > recent email. Basically, all future releases should be providing a sha512 > checksum instead of an md5 one. > There are two tasks: > # Update the release script to use sha512 instead of md5 > [https://github.com/apache/oozie/blob/master/bin/create-release-artifact#L71] > [https://www.apache.org/dev/release-signing#sha-checksum] > # Update the wiki (requires committer/pmc permissions?) > [https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release] > While we're updating the wiki, we should add details on: > # Making sure the gpg key used for signing releases is 4096 bit RSA > # Publishing your gpg public key to a key server > ([https://www.apache.org/dev/release-signing#keyserver]) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OOZIE-3193) Applications are not killed when submitted via subworkflow
Peter Cseh created OOZIE-3193:
-
Summary: Applications are not killed when submitted via subworkflow
Key: OOZIE-3193
URL: https://issues.apache.org/jira/browse/OOZIE-3193
Project: Oozie
Issue Type: Bug
Reporter: Peter Cseh
We're using tags to kill applications. Subworkflows have special tags like
{{workflowID@subwfAcitonID@actionID}}
Right now we're not getting the subWorkflow config properly in JavaAE.kill() so
we're looking for the tag {{subWorkflowID@actionID}} to kill. Therefore actions
submitted via subworkflows are not killed properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OOZIE-3193) Applications are not killed when submitted via subworkflow
[
https://issues.apache.org/jira/browse/OOZIE-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Cseh reassigned OOZIE-3193:
-
Assignee: Peter Cseh
> Applications are not killed when submitted via subworkflow
> --
>
> Key: OOZIE-3193
> URL: https://issues.apache.org/jira/browse/OOZIE-3193
> Project: Oozie
> Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>Priority: Major
>
> We're using tags to kill applications. Subworkflows have special tags like
> {{workflowID@subwfAcitonID@actionID}}
> Right now we're not getting the subWorkflow config properly in JavaAE.kill()
> so we're looking for the tag {{subWorkflowID@actionID}} to kill. Therefore
> actions submitted via subworkflows are not killed properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OOZIE-3192) Oozie Delete runtime directory is not getting called in Services.destroy()
Prabhu Joseph created OOZIE-3192:
Summary: Oozie Delete runtime directory is not getting called in
Services.destroy()
Key: OOZIE-3192
URL: https://issues.apache.org/jira/browse/OOZIE-3192
Project: Oozie
Issue Type: Bug
Components: core
Affects Versions: 4.2.0
Reporter: Prabhu Joseph
Assignee: Prabhu Joseph
Oozie Delete runtime directory as part of Services.destroy() is never getting
called and so we observe below directories accumulate under /tmp.
{code:java}
[root@bigdata2 libtools]# ls /tmp/oozie-oozi*
/tmp/oozie-oozi1000989288737845910.dir:
/tmp/oozie-oozi1036845504637967814.dir:
/tmp/oozie-oozi2051016416521814301.dir:
/tmp/oozie-oozi3194893167383531504.dir:
/tmp/oozie-oozi3750814910369499964.dir:
/tmp/oozie-oozi3988391799981903880.dir:
/tmp/oozie-oozi4308477407910112054.dir:
/tmp/oozie-oozi4717881377452217148.dir:
/tmp/oozie-oozi5894080803700698940.dir:
/tmp/oozie-oozi6367849996578983710.dir:
/tmp/oozie-oozi682733264186033679.dir:
/tmp/oozie-oozi7006370502487976692.dir:
{code}
Below code is never getting called as part of Services.destroy()
{code}
if (deleteRuntimeDir) {
try {
IOUtils.delete(new File(runtimeDir));
}
catch (IOException ex) {
log.error("Error deleting runtime directory [{0}], {1}", runtimeDir,
ex.getMessage(), ex);
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3176) Oozie-core fails with checkstyle errors.
[ https://issues.apache.org/jira/browse/OOZIE-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389240#comment-16389240 ] Alisha Prabhu commented on OOZIE-3176: -- Hi [~asasvari] , can you please review the above patch. Thank you. > Oozie-core fails with checkstyle errors. > > > Key: OOZIE-3176 > URL: https://issues.apache.org/jira/browse/OOZIE-3176 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.0.0b1 > Environment: # uname -a > Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug > 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Alisha Prabhu >Assignee: Alisha Prabhu >Priority: Minor > Attachments: Checkstyle-erros.txt, OOZIE-3176-001.patch > > > There are multiple checkstyle violations in the Oozie-core module. > Maven command used is mvn clean install -DskipTests > I have attached the Checkstyle-errors.txt file, that has the errors occurred > while building. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
