Review Request 67766: OOZIE-2955 Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Kinga Marton via Review Board]

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

Review request for oozie and András Piros.


Repository: oozie-git


Description
---

Currently Findbugs complains about some warnings related to the reliance on the 
default encoding in the oozie-client module:
They should be fixed to get the code more reliable.


Diffs
-

  client/src/main/java/org/apache/oozie/cli/CLIParser.java bbdb8035 
  client/src/main/java/org/apache/oozie/cli/OozieCLI.java bc234e31 
  client/src/main/java/org/apache/oozie/client/AuthOozieClient.java 98f421f3 
  client/src/main/java/org/apache/oozie/client/OozieClient.java 2cc16923 
  client/src/main/java/org/apache/oozie/client/XOozieClient.java ba60f8e7 


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


Testing
---


Thanks,

Kinga Marton

[jira] [Commented] (OOZIE-2955) Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2955:
--

PreCommit-OOZIE-Build started


> Fix Findbugs warnings related to reliance on default encoding in oozie-client
> -
>
> Key: OOZIE-2955
> URL: https://issues.apache.org/jira/browse/OOZIE-2955
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, client
>Reporter: Jan Hentschel
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2955-002.patch, OOZIE-2955-1.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-client* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.CLIParser.showHelp(CommandLine): new 
> java.io.PrintWriter(OutputStream) [org.apache.oozie.cli.CLIParser] At 
> CLIParser.java:[line 169]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 845]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.validateCommandV41(CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 2171]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.readAuthToken(): new 
> java.io.FileReader(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 218]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.writeAuthToken(AuthenticatedURL$Token):
>  new java.io.FileWriter(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 248]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient.getSupportedProtocolVersions(): new 
> java.io.InputStreamReader(InputStream) [org.apache.oozie.client.OozieClient] 
> At OozieClient.java:[line 412]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BulkResponseStatus.call(HttpURLConnection):
>  new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BulkResponseStatus] At 
> OozieClient.java:[line 1693]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobInfo] At OozieClient.java:[line 
> 1502]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobsStatus] At 
> OozieClient.java:[line 1667]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionInfo] At 
> OozieClient.java:[line 1522]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionsKill.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionsKill] At 
> OozieClient.java:[line 1720]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordIgnore.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordIgnore] At OozieClient.java:[line 
> 1743]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobInfo.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobInfo] At OozieClient.java:[line 
> 1455]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobsStatus] At 
> OozieClient.java:[line 1640]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordRerun.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordRerun] At OozieClient.java:[line 
> 1773]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$GetBuildVersion.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$GetBuildVersion] At 
> OozieClient.java:[line 2168]
> [INFO] Found reliance on default encoding in 
> org.apache.

[jira] [Resolved] (OOZIE-3294) Launcher exception: java.io.IOException

[Ahmed (JIRA)]

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

Ahmed resolved OOZIE-3294.
--
Resolution: Fixed

> Launcher exception: java.io.IOException
> ---
>
> Key: OOZIE-3294
> URL: https://issues.apache.org/jira/browse/OOZIE-3294
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.2.0
>Reporter: Ahmed
>Priority: Major
>
> Hi ,
> There is an intermittent issue in oozie workflow, where the oozie action 
> fails sometimes with file not found error for some actions of spark-submit or 
> sqoop. (The issue is intermittent.)
>  
> I am using hadoop - 2.7.3
> oozie version-4.2.0
>  
> "Launcher exception: java.io.IOException Cannot run program "./spark-submit" 
> (in directory "/usr/hdp/current/spark2-client/bin"): error=2, No such file or 
> directory"
>  
>  



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

[jira] [Commented] (OOZIE-2953) Fix Checkstyle issues in oozie-tools

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton commented on OOZIE-2953:
---

[~Jan Hentschel], [~andras.piros], in the master branch this Checkstyle issue 
is not present anymore.So this issue can be marked as resolved.

> Fix Checkstyle issues in oozie-tools
> 
>
> Key: OOZIE-2953
> URL: https://issues.apache.org/jira/browse/OOZIE-2953
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, tools
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Major
> Attachments: OOZIE-2953-1.patch
>
>
> Fix the following Checkstyle issues in the *oozie-tools* module:
> {code}
> oozie/tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java:148: 
> warning: Line is longer than 132 characters.
> {code}



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

[jira] [Commented] (OOZIE-2954) Fix Checkstyle issues in oozie-client

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton commented on OOZIE-2954:
---

[~Jan Hentschel], [~andras.piros], in the master branch this Checkstyle issues 
are not present anymore. I think this issue can be marked as resolved.

> Fix Checkstyle issues in oozie-client
> -
>
> Key: OOZIE-2954
> URL: https://issues.apache.org/jira/browse/OOZIE-2954
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, client
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Major
> Attachments: OOZIE-2954-1.patch
>
>
> Fix the Checkstyle issues in the *oozie-client* module:
> {code}
> oozie/client/src/main/java/org/apache/oozie/cli/CLIParser.java:165: warning: 
> Line has trailing spaces.
> oozie/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:291: 
> warning: Line is longer than 132 characters.
> oozie/client/src/main/java/org/apache/oozie/client/BundleJob.java:56: 
> warning: Line has trailing spaces.
> oozie/client/src/main/java/org/apache/oozie/client/rest/JsonUtils.java:59: 
> warning: Line has trailing spaces.
> oozie/client/src/main/java/org/apache/oozie/client/WorkflowAction.java:65: 
> warning: Line has trailing spaces.
> oozie/client/src/main/java/org/apache/oozie/client/WorkflowAction.java:94: 
> warning: Line has trailing spaces.
> oozie/client/src/main/java/org/apache/oozie/client/WorkflowAction.java:101: 
> warning: Line has trailing spaces.
> oozie/client/src/main/java/org/apache/oozie/client/WorkflowAction.java:108: 
> warning: Line has trailing spaces.
> oozie/client/src/main/java/org/apache/oozie/client/WorkflowJob.java:138: 
> warning: Line has trailing spaces.
> {code}



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

Failed: OOZIE-2955 PreCommit Build #644

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.77 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/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
[ERROR] There are [2] new bugs found below threshold in [client].
[DEBUG] You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
[ERROR] There are [2] new bugs found below threshold in total that must be 
fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 3181 bytes
[TRACE] Full summary file size is 2123 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-2955

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
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 [2] new bugs found below threshold in total that must be fixed.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are 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 [2] new bugs found below threshold in [client] that must be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
 The most important FindBugs errors are:
 At OozieCLI.java:[lines 717-752]: Switch statement found in 
org.apache.oozie.cli.OozieCLI.processCommand(CLIParser, CLIParser$Command) 
where default case is missing
 At XOozieClient.java:[line 82]: 
java/io/FileInputStream.(Ljava/lang/String;)V reads a file whose 
location might be specified by user input
 At OozieCLI.java:[line 2215]: At OozieCLI.java:[line 2207]
 At XOozieClient.java:[line 182]: At XOozieClient.java:[line 166]
 At XOozieClient.java:[line 223]: At XOozieClient.java:[line 201]
+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: 2897
+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/644/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  39070 0  100  3907  0   4628 --:--:-- --:--:-- --:--:--  
4623{"self":"https://issues.apache.org/jira/rest/api/2/issue/13080603/comment/16526099","id":"16526099","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/u

[jira] [Commented] (OOZIE-2955) Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2955:
--


Testing JIRA OOZIE-2955

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color: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:red}-1{color} There are [2] new bugs found below threshold in total that 
must be fixed.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color: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:red}-1{color} There are [2] new bugs found below threshold in [client] 
that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
. The most important FindBugs errors are:
. At OozieCLI.java:[lines 717-752]: Switch statement found in 
org.apache.oozie.cli.OozieCLI.processCommand(CLIParser, CLIParser$Command) 
where default case is missing
. At XOozieClient.java:[line 82]: 
java/io/FileInputStream.(Ljava/lang/String;)V reads a file whose 
location might be specified by user input
. At OozieCLI.java:[line 2215]: At OozieCLI.java:[line 2207]
. At XOozieClient.java:[line 182]: At XOozieClient.java:[line 166]
. At XOozieClient.java:[line 223]: At XOozieClient.java:[line 201]
{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: 2897
{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/644/



> Fix Findbugs warnings related to reliance on default encoding in oozie-client
> -
>
> Key: OOZIE-2955
> URL: https://issues.apache.org/jira/browse/OOZIE-2955
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, client
>Reporter: Jan Hentschel
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2955-002.patch, OOZIE-2955-1.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-client* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.CLIParser.showHelp(CommandLine): new 
> java.io.PrintWriter(OutputStream) [org.apache.oozie.cli.CLIParser] At 
> CLIParser.java:[line 169]
> [INFO] Foun

[jira] [Updated] (OOZIE-2955) Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Julia Kinga Marton (JIRA)]

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

Julia Kinga Marton updated OOZIE-2955:
--
Attachment: OOZIE-2955-003.patch

> Fix Findbugs warnings related to reliance on default encoding in oozie-client
> -
>
> Key: OOZIE-2955
> URL: https://issues.apache.org/jira/browse/OOZIE-2955
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, client
>Reporter: Jan Hentschel
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2955-002.patch, OOZIE-2955-003.patch, 
> OOZIE-2955-1.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-client* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.CLIParser.showHelp(CommandLine): new 
> java.io.PrintWriter(OutputStream) [org.apache.oozie.cli.CLIParser] At 
> CLIParser.java:[line 169]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 845]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.validateCommandV41(CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 2171]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.readAuthToken(): new 
> java.io.FileReader(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 218]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.writeAuthToken(AuthenticatedURL$Token):
>  new java.io.FileWriter(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 248]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient.getSupportedProtocolVersions(): new 
> java.io.InputStreamReader(InputStream) [org.apache.oozie.client.OozieClient] 
> At OozieClient.java:[line 412]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BulkResponseStatus.call(HttpURLConnection):
>  new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BulkResponseStatus] At 
> OozieClient.java:[line 1693]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobInfo] At OozieClient.java:[line 
> 1502]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobsStatus] At 
> OozieClient.java:[line 1667]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionInfo] At 
> OozieClient.java:[line 1522]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionsKill.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionsKill] At 
> OozieClient.java:[line 1720]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordIgnore.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordIgnore] At OozieClient.java:[line 
> 1743]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobInfo.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobInfo] At OozieClient.java:[line 
> 1455]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobsStatus] At 
> OozieClient.java:[line 1640]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordRerun.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordRerun] At OozieClient.java:[line 
> 1773]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$GetBuildVersion.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$GetBuildVersion] At 
> OozieClient.java:[line 2168]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli

Re: Review Request 67766: OOZIE-2955 Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Kinga Marton via Review Board]

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

(Updated June 28, 2018, 8:58 a.m.)


Review request for oozie and András Piros.


Repository: oozie-git


Description
---

Currently Findbugs complains about some warnings related to the reliance on the 
default encoding in the oozie-client module:
They should be fixed to get the code more reliable.


Diffs (updated)
-

  client/src/main/java/org/apache/oozie/cli/CLIParser.java bbdb8035 
  client/src/main/java/org/apache/oozie/cli/OozieCLI.java bc234e31 
  client/src/main/java/org/apache/oozie/client/AuthOozieClient.java 98f421f3 
  client/src/main/java/org/apache/oozie/client/OozieClient.java 2cc16923 
  client/src/main/java/org/apache/oozie/client/XOozieClient.java ba60f8e7 


Diff: https://reviews.apache.org/r/67766/diff/2/

Changes: https://reviews.apache.org/r/67766/diff/1-2/


Testing
---


Thanks,

Kinga Marton

[jira] [Commented] (OOZIE-2955) Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2955:
--

PreCommit-OOZIE-Build started


> Fix Findbugs warnings related to reliance on default encoding in oozie-client
> -
>
> Key: OOZIE-2955
> URL: https://issues.apache.org/jira/browse/OOZIE-2955
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, client
>Reporter: Jan Hentschel
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2955-002.patch, OOZIE-2955-003.patch, 
> OOZIE-2955-1.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-client* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.CLIParser.showHelp(CommandLine): new 
> java.io.PrintWriter(OutputStream) [org.apache.oozie.cli.CLIParser] At 
> CLIParser.java:[line 169]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 845]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.validateCommandV41(CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 2171]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.readAuthToken(): new 
> java.io.FileReader(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 218]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.writeAuthToken(AuthenticatedURL$Token):
>  new java.io.FileWriter(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 248]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient.getSupportedProtocolVersions(): new 
> java.io.InputStreamReader(InputStream) [org.apache.oozie.client.OozieClient] 
> At OozieClient.java:[line 412]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BulkResponseStatus.call(HttpURLConnection):
>  new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BulkResponseStatus] At 
> OozieClient.java:[line 1693]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobInfo] At OozieClient.java:[line 
> 1502]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobsStatus] At 
> OozieClient.java:[line 1667]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionInfo] At 
> OozieClient.java:[line 1522]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionsKill.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionsKill] At 
> OozieClient.java:[line 1720]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordIgnore.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordIgnore] At OozieClient.java:[line 
> 1743]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobInfo.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobInfo] At OozieClient.java:[line 
> 1455]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobsStatus] At 
> OozieClient.java:[line 1640]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordRerun.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordRerun] At OozieClient.java:[line 
> 1773]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$GetBuildVersion.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$GetBuildVersion] At 
> OozieClient.java:[line 2168]
> [INFO] Found reliance on default e

[jira] [Commented] (OOZIE-2955) Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2955:
--


Testing JIRA OOZIE-2955

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warning(s)
.{color: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:red}-1{color} There are [1] new bugs found below threshold in total that 
must be fixed.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color: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:red}-1{color} There are [1] new bugs found below threshold in [client] 
that must be fixed.
. You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
. The most important FindBugs errors are:
. At XOozieClient.java:[line 82]: 
java/io/FileInputStream.(Ljava/lang/String;)V reads a file whose 
location might be specified by user input
. At OozieCLI.java:[line 2214]: At OozieCLI.java:[line 2206]
. At XOozieClient.java:[line 182]: At XOozieClient.java:[line 166]
. At XOozieClient.java:[line 223]: At XOozieClient.java:[line 201]
{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: 2897
{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/645/



> Fix Findbugs warnings related to reliance on default encoding in oozie-client
> -
>
> Key: OOZIE-2955
> URL: https://issues.apache.org/jira/browse/OOZIE-2955
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, client
>Reporter: Jan Hentschel
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2955-002.patch, OOZIE-2955-003.patch, 
> OOZIE-2955-1.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-client* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.CLIParser.showHelp(CommandLine): new 
> java.io.PrintWriter(OutputStream) [org.apache.oozie.cli.CLIParser] At 
> CLIParser.java:[line 169]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, CommandLine): new 
> java.io.FileReader(File) [

Failed: OOZIE-2955 PreCommit Build #645

[Apache Jenkins Server]

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.77 MB...]
[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
[ERROR] There are [1] new bugs found below threshold in [client].
[DEBUG] You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
[ERROR] There are [1] new bugs found below threshold in total that must be 
fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 3014 bytes
[TRACE] Full summary file size is 1956 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-2955

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warning(s)
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 [1] new bugs found below threshold in total that must be fixed.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are 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 [1] new bugs found below threshold in [client] that must be fixed.
 You can find the FindBugs diff here (look for the red and orange ones): 
client/findbugs-new.html
 The most important FindBugs errors are:
 At XOozieClient.java:[line 82]: 
java/io/FileInputStream.(Ljava/lang/String;)V reads a file whose 
location might be specified by user input
 At OozieCLI.java:[line 2214]: At OozieCLI.java:[line 2206]
 At XOozieClient.java:[line 182]: At XOozieClient.java:[line 166]
 At XOozieClient.java:[line 223]: At XOozieClient.java:[line 201]
+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: 2897
+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/645/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  37390 0  100  3739  0   4426 --:--:-- --:--:-- --:--:--  
4424{"self":"https://issues.apache.org/jira/rest/api/2/issue/13080603/comment/16526203","id":"16526203","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&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small

[jira] [Commented] (OOZIE-2955) Fix Findbugs warnings related to reliance on default encoding in oozie-client

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2955:
-

Thanks for the contribution [~kmarton] and [~Jan Hentschel]!

[~kmarton], can you please address the only remaining [*{{FINDBUGS_DIFF}} 
issue*|https://github.com/find-sec-bugs/find-sec-bugs/blob/master/plugin/src/main/resources/metadata/messages.xml#L356-L411]?

> Fix Findbugs warnings related to reliance on default encoding in oozie-client
> -
>
> Key: OOZIE-2955
> URL: https://issues.apache.org/jira/browse/OOZIE-2955
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, client
>Reporter: Jan Hentschel
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2955-002.patch, OOZIE-2955-003.patch, 
> OOZIE-2955-1.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-client* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.CLIParser.showHelp(CommandLine): new 
> java.io.PrintWriter(OutputStream) [org.apache.oozie.cli.CLIParser] At 
> CLIParser.java:[line 169]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.getConfiguration(OozieClient, CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 845]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.cli.OozieCLI.validateCommandV41(CommandLine): new 
> java.io.FileReader(File) [org.apache.oozie.cli.OozieCLI] At 
> OozieCLI.java:[line 2171]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.readAuthToken(): new 
> java.io.FileReader(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 218]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.AuthOozieClient.writeAuthToken(AuthenticatedURL$Token):
>  new java.io.FileWriter(File) [org.apache.oozie.client.AuthOozieClient] At 
> AuthOozieClient.java:[line 248]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient.getSupportedProtocolVersions(): new 
> java.io.InputStreamReader(InputStream) [org.apache.oozie.client.OozieClient] 
> At OozieClient.java:[line 412]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BulkResponseStatus.call(HttpURLConnection):
>  new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BulkResponseStatus] At 
> OozieClient.java:[line 1693]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobInfo] At OozieClient.java:[line 
> 1502]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$BundleJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$BundleJobsStatus] At 
> OozieClient.java:[line 1667]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionInfo.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionInfo] At 
> OozieClient.java:[line 1522]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordActionsKill.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordActionsKill] At 
> OozieClient.java:[line 1720]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordIgnore.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordIgnore] At OozieClient.java:[line 
> 1743]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobInfo.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobInfo] At OozieClient.java:[line 
> 1455]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordJobsStatus.call(HttpURLConnection): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordJobsStatus] At 
> OozieClient.java:[line 1640]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.client.OozieClient$CoordRerun.call(HttpURLConnection): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.client.OozieClient$CoordRerun] At OozieClient.java:[line 
> 1773]
> [INFO] Found reliance on default encoding in 
> org.apache.oo

Re: Review Request 67766: OOZIE-2955 Fix Findbugs warnings related to reliance on default encoding in oozie-client

[András Piros via Review Board]

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




client/src/main/java/org/apache/oozie/client/AuthOozieClient.java
Line 218 (original), 221 (patched)


Please address this 
[`FINDBUGS_DIFF`](https://github.com/find-sec-bugs/find-sec-bugs/blob/master/plugin/src/main/resources/metadata/messages.xml#L356-L411)
 issue.


- András Piros


On June 28, 2018, 8:58 a.m., Kinga Marton wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67766/
> ---
> 
> (Updated June 28, 2018, 8:58 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Currently Findbugs complains about some warnings related to the reliance on 
> the default encoding in the oozie-client module:
> They should be fixed to get the code more reliable.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/cli/CLIParser.java bbdb8035 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java bc234e31 
>   client/src/main/java/org/apache/oozie/client/AuthOozieClient.java 98f421f3 
>   client/src/main/java/org/apache/oozie/client/OozieClient.java 2cc16923 
>   client/src/main/java/org/apache/oozie/client/XOozieClient.java ba60f8e7 
> 
> 
> Diff: https://reviews.apache.org/r/67766/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Kinga Marton
> 
>

[jira] [Commented] (OOZIE-2956) Fix Findbugs warnings related to reliance on default encoding in oozie-core

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2956:
-

Thanks for the contribution [~kmarton] [~Jan Hentschel]!

[~kmarton] if so, can you please mark these places with 
{{@SuppressFBWarnings(value, justification)}} just like 
[*here*|https://github.com/apache/oozie/blob/master/client/src/main/java/org/apache/oozie/cli/OozieCLI.java#L1415-L1435]?
 Thanks!

> Fix Findbugs warnings related to reliance on default encoding in oozie-core
> ---
>
> Key: OOZIE-2956
> URL: https://issues.apache.org/jira/browse/OOZIE-2956
> Project: Oozie
>  Issue Type: Sub-task
>  Components: build, core
>Reporter: Jan Hentschel
>Assignee: Julia Kinga Marton
>Priority: Major
> Attachments: OOZIE-2956-003.patch, OOZIE-2956-1.patch, 
> OOZIE-2956-2.patch
>
>
> Currently Findbugs complains about the following warnings related to the 
> reliance on the default encoding in the *oozie-core* module:
> {code}
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.StringBlob.getRawBlob(): String.getBytes() 
> [org.apache.oozie.StringBlob] At StringBlob.java:[line 119]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ActionExecutor.registerError(String, 
> ActionExecutorException$ErrorType, String): 
> java.io.ByteArrayOutputStream.toString() 
> [org.apache.oozie.action.ActionExecutor] At ActionExecutor.java:[line 354]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ActionExecutor.registerError(String, 
> ActionExecutorException$ErrorType, String): new 
> java.io.PrintStream(OutputStream) [org.apache.oozie.action.ActionExecutor] At 
> ActionExecutor.java:[line 353]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper.getRecoveryId(Configuration, 
> Path, String): new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.hadoop.LauncherHelper] At LauncherHelper.java:[line 
> 69]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper.getTag(String): 
> String.getBytes() [org.apache.oozie.action.hadoop.LauncherHelper] At 
> LauncherHelper.java:[line 160]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherHelper$1.run(): new 
> java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1, 
> org.apache.oozie.action.hadoop.LauncherHelper$1] At LauncherHelper.java:[line 
> 271]Another occurrence at LauncherHelper.java:[line 277]Another occurrence at 
> LauncherHelper.java:[line 285]Another occurrence at LauncherHelper.java:[line 
> 293]Another occurrence at LauncherHelper.java:[line 299]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.MapReduceActionExecutor.end(ActionExecutor$Context,
>  WorkflowAction): String.getBytes() 
> [org.apache.oozie.action.hadoop.MapReduceActionExecutor] At 
> MapReduceActionExecutor.java:[line 250]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.SqoopActionExecutor.end(ActionExecutor$Context,
>  WorkflowAction): String.getBytes() 
> [org.apache.oozie.action.hadoop.SqoopActionExecutor] At 
> SqoopActionExecutor.java:[line 186]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ssh.SshActionExecutor.drainBuffers(Process, 
> StringBuffer, StringBuffer, int): new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.action.ssh.SshActionExecutor, 
> org.apache.oozie.action.ssh.SshActionExecutor] At 
> SshActionExecutor.java:[line 684]Another occurrence at 
> SshActionExecutor.java:[line 685]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.ssh.SshActionExecutor.initSshScripts(): new 
> java.io.FileWriter(String) [org.apache.oozie.action.ssh.SshActionExecutor, 
> org.apache.oozie.action.ssh.SshActionExecutor] At 
> SshActionExecutor.java:[line 502]Another occurrence at 
> SshActionExecutor.java:[line 504]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.bundle.BundleSubmitXCommand.readDefinition(String): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.command.bundle.BundleSubmitXCommand] At 
> BundleSubmitXCommand.java:[line 322]
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.command.coord.CoordSubmitXCommand.readDefinition(String): 
> new java.io.InputStreamReader(InputStream) 
> [org.apache.oozie.command.coord.CoordSubmitXCommand] At 
> CoordSubmitXCommand.java:[line 1193]
> [INFO] Found reliance 

Re: Review Request 67763: OOZIE-2956 Fix Findbugs warnings related to reliance on default encoding in oozie-core

[András Piros via Review Board]

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




core/src/main/java/org/apache/oozie/action/ssh/SshActionExecutor.java
Line 122 (original), 125 (patched)


Can you please mark these places with `@SuppressFBWarnings(value, 
justification)` just like 
[here](https://github.com/apache/oozie/blob/master/client/src/main/java/org/apache/oozie/cli/OozieCLI.java#L1415-L1435)?



core/src/main/java/org/apache/oozie/action/ssh/SshActionExecutor.java
Line 525 (original), 522 (patched)


Can you please mark these places with `@SuppressFBWarnings(value, 
justification)` just like 
[here](https://github.com/apache/oozie/blob/master/client/src/main/java/org/apache/oozie/cli/OozieCLI.java#L1415-L1435)?


- András Piros


On June 27, 2018, 6:47 p.m., Kinga Marton wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67763/
> ---
> 
> (Updated June 27, 2018, 6:47 p.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Currently Findbugs complains about the a few warnings related to the reliance 
> on the default encoding in the oozie-core module
> They should be fixed to get the code more reliable.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/StringBlob.java 6c776011 
>   core/src/main/java/org/apache/oozie/action/ActionExecutor.java 919509d3 
>   core/src/main/java/org/apache/oozie/action/hadoop/LauncherHelper.java 
> 21c9b7e4 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/MapReduceActionExecutor.java
>  d0b80742 
>   core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java 
> 69d5e7e9 
>   core/src/main/java/org/apache/oozie/action/ssh/SshActionExecutor.java 
> 128feee7 
>   
> core/src/main/java/org/apache/oozie/command/bundle/BundleSubmitXCommand.java 
> 80e7d5d4 
>   core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
> 8bfa634f 
>   core/src/main/java/org/apache/oozie/command/coord/CoordUpdateXCommand.java 
> 502a800f 
>   core/src/main/java/org/apache/oozie/service/AuthorizationService.java 
> 251838ce 
>   core/src/main/java/org/apache/oozie/service/WorkflowAppService.java 
> c725f493 
>   core/src/main/java/org/apache/oozie/servlet/V1JobServlet.java 361141b0 
>   core/src/main/java/org/apache/oozie/servlet/V2ValidateServlet.java 36a9de22 
>   core/src/main/java/org/apache/oozie/util/AuthUrlClient.java 4fc8f572 
>   core/src/main/java/org/apache/oozie/util/IOUtils.java 3674dc48 
>   core/src/main/java/org/apache/oozie/util/MultiFileReader.java 1ab5a7af 
>   core/src/main/java/org/apache/oozie/util/XConfiguration.java e3591db3 
>   core/src/main/java/org/apache/oozie/util/XmlUtils.java 9db46b36 
> 
> 
> Diff: https://reviews.apache.org/r/67763/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Kinga Marton
> 
>

[jira] [Commented] (OOZIE-3299) CoordStatusTransitXCommand logs shows wrong ACTION value

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3299:
-

[~Prabhu Joseph] so the fix would essentially consist of emptying 
{{DagXLogInfoService.ACTION}} while {{LogUtils#setLogInfo(CoordinatorJobBean 
cBean)}}, right?

> CoordStatusTransitXCommand logs shows wrong ACTION value
> 
>
> Key: OOZIE-3299
> URL: https://issues.apache.org/jira/browse/OOZIE-3299
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.1
>Reporter: Prabhu Joseph
>Priority: Major
>
> ISSUE:
> The logs from CoordStatusTransitXCommand with different coordinators shows 
> wrong ACTION value. The action 0188706-180421101115209-oozie-oozi-W does 
> not belong to any of the coordinators. This is misleading while analyzing the 
> oozie server logs.
> {code}
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,301  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awbti01] GROUP[-] TOKEN[] APP[PVL_data_sync] 
> JOB[0009039-180122185814644-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0009039-180122185814644-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,305  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awbti01] GROUP[-] TOKEN[] APP[sohe] 
> JOB[0182017-180421101115209-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0182017-180421101115209-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,310  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awdlc03] GROUP[-] TOKEN[] APP[PRD_COORDINATOR_INGESTION_CAD] 
> JOB[0005634-171021095136703-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0005634-171021095136703-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,329  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[a004163] GROUP[-] TOKEN[] APP[coordinator_inventory] 
> JOB[0160434-180421101115209-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0160434-180421101115209-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> {code}
> Suspect:
> The logging is a shared service and every commands (or threads) uses it has 
> own values for the fields like USER, GROUP, TOKEN, APP , JOB and ACTION. The 
> CoordinatorJob won't have any ACTION details. While logging, since it does 
> not have a action value, Log Service wrongly uses a value which is in memory 
> and used by some other thread.
> Code Analysis:
> CoordStatusTransitXCommand - at start defines the parameters like GROUP, 
> USER, JOB, TOKEN, APP and it does not have any ACTION.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordStatusTransitXCommand.java#L101
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/util/LogUtils.java#L46
> We need a fix like clear the log prefix before logging from 
> CoordStatusTransitXCommand - which will remove stale ACTION value and won;t 
> show any ACTION details
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/util/LogUtils.java#L172



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

[jira] [Updated] (OOZIE-3290) Distcp action between 2 secure HA hadoop clusters failed

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3290:

Description: 
oozie launcher property set from distcp action does not take effect. Hadoop 
version is 2.6.0 (cdh 5.13.2 which has this patch included 
https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )

When we set the same property from global configuration, this property gets 
picked and we do not see the exception. However setting this property at the 
distcp action level is what is required for us.  
{code:java}
 
   oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
   destCluster  


As a result we end up getting 

0943330-180615101217371-oozie-oozi-W@snapshot-prep  -   JA009   JA009: 
org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL   
 -{code}

> Distcp action between 2 secure HA hadoop clusters failed
> 
>
> Key: OOZIE-3290
> URL: https://issues.apache.org/jira/browse/OOZIE-3290
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
>Reporter: Rohit Pegallapati
>Priority: Major
>
> oozie launcher property set from distcp action does not take effect. Hadoop 
> version is 2.6.0 (cdh 5.13.2 which has this patch included 
> https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )
> When we set the same property from global configuration, this property gets 
> picked and we do not see the exception. However setting this property at the 
> distcp action level is what is required for us.  
> {code:java}
>  
>
> oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
>destCluster  
> 
> As a result we end up getting 
> 0943330-180615101217371-oozie-oozi-W@snapshot-prep-   JA009   JA009: 
> org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
> application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
> Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
> issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
> masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL 
>-{code}



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

[jira] [Updated] (OOZIE-3290) Distcp action between 2 secure HA hadoop clusters failed

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3290:

Environment: (was: oozie launcher property set from distcp action does 
not take effect. Hadoop version is 2.6.0 (cdh 5.13.2 which has this patch 
included https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )

When we set the same property from global configuration, this property gets 
picked and we do not see the exception. However setting this property at the 
distcp action level is what is required for us.  
{code:java}
 
   oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
   destCluster  


As a result we end up getting 

0943330-180615101217371-oozie-oozi-W@snapshot-prep  -   JA009   JA009: 
org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL   
 -{code})

> Distcp action between 2 secure HA hadoop clusters failed
> 
>
> Key: OOZIE-3290
> URL: https://issues.apache.org/jira/browse/OOZIE-3290
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
>Reporter: Rohit Pegallapati
>Priority: Major
>




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

[jira] [Updated] (OOZIE-3290) Distcp action between 2 secure HA hadoop clusters failed

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3290:

Description: 
oozie launcher property set from distcp action does not take effect. Hadoop 
version is 2.6.0 (cdh 5.13.2 which has this patch included 
https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )

When we set the same property from global configuration, this property gets 
picked and we do not see the exception. However setting this property at the 
distcp action level is what is required for us.  
{code:xml}
 
   oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
   destCluster  

{code}

As a result we end up getting:
{noformat}
0943330-180615101217371-oozie-oozi-W@snapshot-prep  -   JA009   JA009: 
org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL   
 -
{noformat}

  was:
oozie launcher property set from distcp action does not take effect. Hadoop 
version is 2.6.0 (cdh 5.13.2 which has this patch included 
https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )

When we set the same property from global configuration, this property gets 
picked and we do not see the exception. However setting this property at the 
distcp action level is what is required for us.  
{code:java}
 
   oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
   destCluster  


As a result we end up getting 

0943330-180615101217371-oozie-oozi-W@snapshot-prep  -   JA009   JA009: 
org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL   
 -{code}


> Distcp action between 2 secure HA hadoop clusters failed
> 
>
> Key: OOZIE-3290
> URL: https://issues.apache.org/jira/browse/OOZIE-3290
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
>Reporter: Rohit Pegallapati
>Priority: Major
>
> oozie launcher property set from distcp action does not take effect. Hadoop 
> version is 2.6.0 (cdh 5.13.2 which has this patch included 
> https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )
> When we set the same property from global configuration, this property gets 
> picked and we do not see the exception. However setting this property at the 
> distcp action level is what is required for us.  
> {code:xml}
>  
>
> oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
>destCluster  
> 
> {code}
> As a result we end up getting:
> {noformat}
> 0943330-180615101217371-oozie-oozi-W@snapshot-prep-   JA009   JA009: 
> org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
> application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
> Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
> issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
> masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL 
>-
> {noformat}



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

[jira] [Commented] (OOZIE-3299) CoordStatusTransitXCommand logs shows wrong ACTION value

[Prabhu Joseph (JIRA)]

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

Prabhu Joseph commented on OOZIE-3299:
--

Yes [~andras.piros]

> CoordStatusTransitXCommand logs shows wrong ACTION value
> 
>
> Key: OOZIE-3299
> URL: https://issues.apache.org/jira/browse/OOZIE-3299
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.1
>Reporter: Prabhu Joseph
>Priority: Major
>
> ISSUE:
> The logs from CoordStatusTransitXCommand with different coordinators shows 
> wrong ACTION value. The action 0188706-180421101115209-oozie-oozi-W does 
> not belong to any of the coordinators. This is misleading while analyzing the 
> oozie server logs.
> {code}
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,301  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awbti01] GROUP[-] TOKEN[] APP[PVL_data_sync] 
> JOB[0009039-180122185814644-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0009039-180122185814644-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,305  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awbti01] GROUP[-] TOKEN[] APP[sohe] 
> JOB[0182017-180421101115209-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0182017-180421101115209-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,310  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awdlc03] GROUP[-] TOKEN[] APP[PRD_COORDINATOR_INGESTION_CAD] 
> JOB[0005634-171021095136703-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0005634-171021095136703-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,329  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[a004163] GROUP[-] TOKEN[] APP[coordinator_inventory] 
> JOB[0160434-180421101115209-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0160434-180421101115209-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> {code}
> Suspect:
> The logging is a shared service and every commands (or threads) uses it has 
> own values for the fields like USER, GROUP, TOKEN, APP , JOB and ACTION. The 
> CoordinatorJob won't have any ACTION details. While logging, since it does 
> not have a action value, Log Service wrongly uses a value which is in memory 
> and used by some other thread.
> Code Analysis:
> CoordStatusTransitXCommand - at start defines the parameters like GROUP, 
> USER, JOB, TOKEN, APP and it does not have any ACTION.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordStatusTransitXCommand.java#L101
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/util/LogUtils.java#L46
> We need a fix like clear the log prefix before logging from 
> CoordStatusTransitXCommand - which will remove stale ACTION value and won;t 
> show any ACTION details
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/util/LogUtils.java#L172



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

[jira] [Assigned] (OOZIE-3299) CoordStatusTransitXCommand logs shows wrong ACTION value

[Prabhu Joseph (JIRA)]

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

Prabhu Joseph reassigned OOZIE-3299:


Assignee: Prabhu Joseph

> CoordStatusTransitXCommand logs shows wrong ACTION value
> 
>
> Key: OOZIE-3299
> URL: https://issues.apache.org/jira/browse/OOZIE-3299
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.1
>Reporter: Prabhu Joseph
>Assignee: Prabhu Joseph
>Priority: Major
>
> ISSUE:
> The logs from CoordStatusTransitXCommand with different coordinators shows 
> wrong ACTION value. The action 0188706-180421101115209-oozie-oozi-W does 
> not belong to any of the coordinators. This is misleading while analyzing the 
> oozie server logs.
> {code}
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,301  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awbti01] GROUP[-] TOKEN[] APP[PVL_data_sync] 
> JOB[0009039-180122185814644-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0009039-180122185814644-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,305  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awbti01] GROUP[-] TOKEN[] APP[sohe] 
> JOB[0182017-180421101115209-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0182017-180421101115209-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,310  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[awdlc03] GROUP[-] TOKEN[] APP[PRD_COORDINATOR_INGESTION_CAD] 
> JOB[0005634-171021095136703-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0005634-171021095136703-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> oozie.log-2018-06-07-16:2018-06-07 16:13:17,329  INFO 
> CoordStatusTransitXCommand:520 - SERVER[bigdata2.openstacklocal] 
> USER[a004163] GROUP[-] TOKEN[] APP[coordinator_inventory] 
> JOB[0160434-180421101115209-oozie-oozi-C] 
> ACTION[0188706-180421101115209-oozie-oozi-W@fs-move] Set coordinator job 
> [0160434-180421101115209-oozie-oozi-C] status to 'RUNNING' from 'RUNNING'
> {code}
> Suspect:
> The logging is a shared service and every commands (or threads) uses it has 
> own values for the fields like USER, GROUP, TOKEN, APP , JOB and ACTION. The 
> CoordinatorJob won't have any ACTION details. While logging, since it does 
> not have a action value, Log Service wrongly uses a value which is in memory 
> and used by some other thread.
> Code Analysis:
> CoordStatusTransitXCommand - at start defines the parameters like GROUP, 
> USER, JOB, TOKEN, APP and it does not have any ACTION.
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/command/coord/CoordStatusTransitXCommand.java#L101
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/util/LogUtils.java#L46
> We need a fix like clear the log prefix before logging from 
> CoordStatusTransitXCommand - which will remove stale ACTION value and won;t 
> show any ACTION details
> https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/util/LogUtils.java#L172



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

[jira] [Commented] (OOZIE-3290) Distcp action between 2 secure HA hadoop clusters failed

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3290:
-

[~rohit.peg] thanks for calling the attention to this issue! Do you happen to 
encounter this bug also on Oozie 5.0.0 / 4.3.1 as well?

> Distcp action between 2 secure HA hadoop clusters failed
> 
>
> Key: OOZIE-3290
> URL: https://issues.apache.org/jira/browse/OOZIE-3290
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
>Reporter: Rohit Pegallapati
>Priority: Major
>
> oozie launcher property set from distcp action does not take effect. Hadoop 
> version is 2.6.0 (cdh 5.13.2 which has this patch included 
> https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )
> When we set the same property from global configuration, this property gets 
> picked and we do not see the exception. However setting this property at the 
> distcp action level is what is required for us.  
> {code:xml}
>  
>
> oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
>destCluster  
> 
> {code}
> As a result we end up getting:
> {noformat}
> 0943330-180615101217371-oozie-oozi-W@snapshot-prep-   JA009   JA009: 
> org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
> application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
> Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
> issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
> masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL 
>-
> {noformat}



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

[jira] [Commented] (OOZIE-3291) Oozie workflow hangs in running state even when the underlying action failed

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3291:
-

[~rohit.peg] can you please post relevant parts of your {{workflow.xml}} / 
{{coordinator.xml}}? Do you also encounter the issue on a newer Oozie like 
5.0.0 / 4.3.1?

> Oozie workflow hangs in running state even when the underlying action failed
> 
>
> Key: OOZIE-3291
> URL: https://issues.apache.org/jira/browse/OOZIE-3291
> Project: Oozie
>  Issue Type: Bug
>  Components: workflow
>Affects Versions: 4.1.0
>Reporter: Rohit Pegallapati
>Priority: Major
>
> We have mutiple distcp actions in fork join. We use hadoop 2.6.0 (cdh 5.5.1). 
> We are hitting 
> https://issues.apache.org/jira/browse/MAPREDUCE-6478
> at this time the distcp action fails with the below exception.
> {code:java}
> 2018-06-10 15:19:39,179 INFO [AsyncDispatcher event handler] 
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics 
> report from attempt_1520068304865_972654_m_00_0: 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException):
>  No lease on 
> /user/xxx/oozie-oozi/1951586-180303074950833-oozie-oozi-W/distcp-to-dr-0-update-action--distcp/output/_temporary/1/_temporary/attempt_1520068304865_972654_m_00_0/part-0
>  (inode 192492374): File does not exist. Holder 
> DFSClient_NONMAPREDUCE_-2068852542_1 does not have any open files.
> at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkLease(FSNamesystem.java:3604)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.completeFileInternal(FSNamesystem.java:3690)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.completeFile(FSNamesystem.java:3660)
> at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.complete(NameNodeRpcServer.java:738)
> at 
> org.apache.hadoop.hdfs.server.namenode.AuthorizationProviderProxyClientProtocol.complete(AuthorizationProviderProxyClientProtocol.java:243)
> at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.complete(ClientNamenodeProtocolServerSideTranslatorPB.java:528)
> at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:617)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1060)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2086)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2082)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2080)
> {code}
> At this time we expect that WF should be killed and subsequent WF should 
> start. But this WF is stuck in RUNNING state and other WFs get stacked up 
> through the coordinator, leaving no option but to kill the running WF. After 
> this defective WF is killed, other WF's process perfectly fine  



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

[jira] [Commented] (OOZIE-3290) Distcp action between 2 secure HA hadoop clusters failed

[Rohit Pegallapati (JIRA)]

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

Rohit Pegallapati commented on OOZIE-3290:
--

Hi [~andras.piros] , in our setup we use cloudera cdh 5.13.2 which ships with 
oozie 4.1.0. We do not have a setup to test 5.0 of oozie. But essentially, we 
are going to live with cdh 5.13.2 for foreseeable future. So it makes sense for 
us to get this fixed in 4.1.0 and ask cloudera to port this fix.   

> Distcp action between 2 secure HA hadoop clusters failed
> 
>
> Key: OOZIE-3290
> URL: https://issues.apache.org/jira/browse/OOZIE-3290
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
>Reporter: Rohit Pegallapati
>Priority: Major
>
> oozie launcher property set from distcp action does not take effect. Hadoop 
> version is 2.6.0 (cdh 5.13.2 which has this patch included 
> https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )
> When we set the same property from global configuration, this property gets 
> picked and we do not see the exception. However setting this property at the 
> distcp action level is what is required for us.  
> {code:xml}
>  
>
> oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
>destCluster  
> 
> {code}
> As a result we end up getting:
> {noformat}
> 0943330-180615101217371-oozie-oozi-W@snapshot-prep-   JA009   JA009: 
> org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
> application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
> Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
> issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
> masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL 
>-
> {noformat}



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

[jira] [Commented] (OOZIE-3290) Distcp action between 2 secure HA hadoop clusters failed

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3290:
-

[~rohit.peg] can you post relevant {{workflow.xml}} details with {{global}} 
level working, but {{action}} level not working? Thanks!

> Distcp action between 2 secure HA hadoop clusters failed
> 
>
> Key: OOZIE-3290
> URL: https://issues.apache.org/jira/browse/OOZIE-3290
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
>Reporter: Rohit Pegallapati
>Priority: Major
>
> oozie launcher property set from distcp action does not take effect. Hadoop 
> version is 2.6.0 (cdh 5.13.2 which has this patch included 
> https://issues.apache.org/jira/browse/YARN-3021?attachmentOrder=asc )
> When we set the same property from global configuration, this property gets 
> picked and we do not see the exception. However setting this property at the 
> distcp action level is what is required for us.  
> {code:xml}
>  
>
> oozie.launcher.mapreduce.job.hdfs-servers.tokenrenewal.exclude 
>destCluster  
> 
> {code}
> As a result we end up getting:
> {noformat}
> 0943330-180615101217371-oozie-oozi-W@snapshot-prep-   JA009   JA009: 
> org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit 
> application_1529074835014_0830 to YARN : Failed to renew token: Kind: kms-dt, 
> Service: xxx:16000, Ident: (kms-dt owner=xxx, renewer=yarn, realUser=oozie, 
> issueDate=1529101158245, maxDate=1531520358245, sequenceNumber=446, 
> masterKeyId=2)   --snapshot-prep 0   -   java-   START_MANUAL 
>-
> {noformat}



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

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (95 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3274  Remove slf4j
https://issues.apache.org/jira/browse/OOZIE-3274
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-3208  "It should never happen" error messages should be more specific to 
root cause
https://issues.apache.org/jira/browse/OOZIE-3208
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-3193  Applications are not killed when submitted via subworkflow
https://issues.apache.org/jira/browse/OOZIE-3193
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-3109  Escape log-streaming's HTML-specific characters
https://issues.apache.org/jira/browse/OOZIE-3109
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-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-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  [examples] Fix Findbugs warnings
https://issues.apache.org/jira/browse/OOZIE-2942
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-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/browse/OOZIE-2829
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-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2736  Reduce the number of threads during test execu