[jira] [Commented] (OOZIE-3048) Check El Functions for the coordinator action

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-3048:
---

+1

> Check El Functions for the coordinator action
> -
>
> Key: OOZIE-3048
> URL: https://issues.apache.org/jira/browse/OOZIE-3048
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3048-1.patch
>
>
> In OOZIE-2873, we tried introduce check for EL functions before submitting 
> the coordinator. But this not possible as described 
> [here|https://issues.apache.org/jira/browse/OOZIE-2873?focusedCommentId=15999124=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15999124].
>  Instead, we can do this check in CoordActionInputCheckXCommand when we 
> resolve coordinator configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62387: OOZIE-3048 Check El Functions for the coordinator action

[Rohini Palaniswamy]

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


Ship it!




- Rohini Palaniswamy


On Sept. 19, 2017, 1 a.m., Satish Saley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62387/
> ---
> 
> (Updated Sept. 19, 2017, 1 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-3048
> https://issues.apache.org/jira/browse/OOZIE-3048
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3048 Check El Functions for the coordinator action
> 
> 
> Diffs
> -
> 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
>  650e7f8c 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordPushDependencyCheckXCommand.java
>  0ad39703 
>   core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java fd2f92dc 
>   core/src/main/java/org/apache/oozie/coord/ElException.java PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionInputCheckXCommand.java
>  bbe9ea7a 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordPushDependencyCheckXCommand.java
>  25f250ce 
>   core/src/test/resources/coord-hcatinput-invalid-elfunction.xml PRE-CREATION 
>   core/src/test/resources/coord-hdfsinput-invalid-elfunction.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62387/diff/2/
> 
> 
> Testing
> ---
> 
> tested locally
> 
> 
> Thanks,
> 
> Satish Saley
> 
>

Failed: OOZIE-3058 PreCommit Build #31

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1.68 MB...]
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [core].
 +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/streaming].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [examples].
+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: 2029
Tests failed: 0
Tests errors: 1

The patch failed the following testcases:

  

Tests failing with errors:
  testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation)

+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/31/

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100 3706k  100 3706k0 0  3461k  0  0:00:01  0:00:01 --:--:-- 5450k
Adding comment to JIRA
Comment added.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3058
Archiving artifacts
[Fast Archiver] Compressed 1.89 MB of artifacts by 19.9% relative to #29
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation

Error Message:
Unable to open socket file: target process not responding or HotSpot VM not 
loaded

Stack Trace:
com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: 
target process not responding or HotSpot VM not loaded
at 
sun.tools.attach.LinuxVirtualMachine.(LinuxVirtualMachine.java:106)
at 
sun.tools.attach.LinuxAttachProvider.attachVirtualMachine(LinuxAttachProvider.java:78)
at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:250)
at 
org.apache.oozie.util.TestMetricsInstrumentation.testJMXInstrumentation(TestMetricsInstrumentation.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at 

[jira] [Commented] (OOZIE-2645) Drop Instrumentation in favor of Metrics

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2645:
--

The very minimum here is to make Metrics the default, and leave the cleanup for 
later.

> Drop Instrumentation in favor of Metrics
> 
>
> Key: OOZIE-2645
> URL: https://issues.apache.org/jira/browse/OOZIE-2645
> Project: Oozie
>  Issue Type: Improvement
>  Components: monitoring
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0
>
>
> OOZIE-1817 added the option to use DropWizard Metrics instead of our 
> homegrown Instrumentation.  We left the Instrumentation as the default for 
> compatibility; in Oozie 5, we should drop Instrumentation and only have 
> Metrics.
> We can also use this opportunity to clean up the code and interface for 
> Metrics, which currently has to conform to Instrumentation for pluggability.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2406) Completely rewrite GraphGenerator code

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2406:
--

1. The advantage of removing the {{JungRenderer}} is that we could remove the 
jung and Commons-Collections fork dependencies.  I'm okay with leaving it for 
now if we want to give the {{GraphvizRenderer}} more time to bake.  However, it 
looks like {{GraphGenerator}} is hardcoded to use {{GraphvizRenderer}} so you 
can't use the {{JungRenderer}} anyway.
2. We should add Metrics/Instrumentation in key areas of the generator code.  
That might be helpful for performance testing, and would be a useful thing to 
expose anyway.  e.g. how long it takes to generate the graph, how long it takes 
to render the png, etc

> Completely rewrite GraphGenerator code
> --
>
> Key: OOZIE-2406
> URL: https://issues.apache.org/jira/browse/OOZIE-2406
> Project: Oozie
>  Issue Type: New Feature
>Affects Versions: 4.2.0
>Reporter: Robert Kanter
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: graphviz-10-action-nodes.png, 
> graphviz-25-action-nodes.png, graphviz-50-action-nodes.png, 
> graphviz-many-nodes.png, jung-many-nodes.png, OOZIE-2406.004.patch, 
> OOZIE-2406.004.patch, OOZIE-2406.005.patch, OOZIE-2406.006.patch
>
>
> The Web UI currently generates a graph of the workflow DAG as a png image 
> that it can show to the user ({{GraphGenerator}} class).  Unfortunately, 
> there are a number of downsides to the current implementation:
> # The image is generated server-side, which doesn't scale well and eats up 
> lots of memory
> #- To help combat this issue, we only generate graphs for workflows with less 
> than 25 nodes and we disabled the refresh button in the UI
> # It's slow
> # It uses a library ({{net.sf.jung}} from http://jung.sourceforge.net), which 
> hasn't been updated since 2010.  
> #- This library also has a dependency on a fork of Commons-Collections 
> ({{net.sourceforge.collections}} from 
> http://sourceforge.net/projects/collections/), which similarly hasn't been 
> updated since 2010.  This is a problem because we can't update 
> Commons-Collections when there are security concerns such as COLLECTIONS-580 
> (though Oozie is *not* susceptible to this attack).
> It would be good to do a complete rewrite, using a different library and 
> remove Jung and the Commons-Collections fork.  Whatever we choose, it should 
> an svg which will draw the image on the browser.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OOZIE-3061) Kill only those child jobs which are not already killed

[Satish Subhashrao Saley (JIRA)]

Satish Subhashrao Saley created OOZIE-3061:
--

 Summary: Kill only those child jobs which are not already killed
 Key: OOZIE-3061
 URL: https://issues.apache.org/jira/browse/OOZIE-3061
 Project: Oozie
  Issue Type: Bug
Reporter: Satish Subhashrao Saley
Priority: Trivial


Here we kill all child jobs. 
https://github.com/apache/oozie/blob/master/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMain.java#L265
We should check before killing for already killed application.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 61560: OOZIE-2909 LauncherAM: rewrite UGI calls

[Peter Cseh]

> On Sept. 18, 2017, 3:25 p.m., Attila Sasvari wrote:
> > core/src/main/java/org/apache/oozie/ErrorCode.java
> > Lines 92 (patched)
> > 
> >
> > typo

Where?


- Peter


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


On Sept. 17, 2017, 7:06 a.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61560/
> ---
> 
> (Updated Sept. 17, 2017, 7:06 a.m.)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Bacsko, Robert Kanter, and 
> Rohini Palaniswamy.
> 
> 
> Bugs: OOZIE-2909
> https://issues.apache.org/jira/browse/OOZIE-2909
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Changing UGI calls and cleaning up things around requesting tokens.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/ErrorCode.java 
> 662e1edc9c4b23b3606c751bf5ed4b531ee7ac62 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProperties.java 
> 20f93ce57618a529b1bd83b398add2cd1d96b36e 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProviderFactory.java
>  5ca8d3e80942840a5bba51a06694350929044042 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentialHelper.java 
> 9804c7b673a899cd9c778850c9a64731cc642fb3 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java 
> 52abbf17afa71e702d7871d10a4a190a4d21e47b 
>   core/src/main/java/org/apache/oozie/action/hadoop/HDFSCredentials.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/HadoopTokenHelper.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
> 4add5f14cb20ab77c755b81eff939335c0c5fddc 
>   core/src/main/java/org/apache/oozie/action/hadoop/Hive2Credentials.java 
> 0b495f75842b0033a3337ef6728a334bf5651770 
>   core/src/main/java/org/apache/oozie/action/hadoop/JHSCredentials.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 49fd4b8560b21aef725c3268f0ec0e7f46a46ee9 
>   core/src/main/java/org/apache/oozie/action/hadoop/YarnRMCredentials.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java 
> 187cee2290ba4bbe358913d28a052d9c75f2369a 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestHadoopTokenHelper.java 
> PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> d1d78fd527a425b076edd7bb23ba56ebdba62664 
>   core/src/test/java/org/apache/oozie/action/hadoop/TestShellMain.java 
> a7d6c18a645b50fc35657515480da9967fa74e2e 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowActionKillXCommand.java
>  cf77f18c4bdbe95ea66f63aa115ce6f34c90c855 
>   core/src/test/java/org/apache/oozie/service/TestHadoopAccessorService.java 
> 960c2f9750062c98fdf7a2b456d3668069e07ca5 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/AMRMClientAsyncFactory.java
>  b4cbb4b1d9b52aaebfb562c02edc91e15a2a9a2e 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/HdfsOperations.java
>  874d371664ced3ae19a7b5d615c67d4c72e7cfdd 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
> 6a98d6ef3a09a7a75272f3f0f9a9c2fc5472e76d 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/ShellMain.java 
> bde7f1daf123d663d47f5d2fb2350cfa1ac33ed8 
>   
> sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/TestHdfsOperations.java
>  68c0f4bafe0322ff0d1007297cd6e8f38c92020a 
>   
> sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAM.java
>  37af3dd9ed43f4504ff3909484237e2d05665c6c 
> 
> 
> Diff: https://reviews.apache.org/r/61560/diff/7/
> 
> 
> Testing
> ---
> 
> We're running tests on a Kerberized cluster with these changes.
> 
> 
> Thanks,
> 
> Peter Cseh
> 
>

Re: Review Request 62387: OOZIE-3048 Check El Functions for the coordinator action

[Rohini Palaniswamy]

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




core/src/test/java/org/apache/oozie/command/coord/TestCoordPushDependencyCheckXCommand.java
Lines 443 (patched)


Can you rename the files as coord-hcatinput-invalid-elfunction.xml and 
coord-hdfsinput-invalid-elfunction.xml?


- Rohini Palaniswamy


On Sept. 18, 2017, 5:05 p.m., Satish Saley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62387/
> ---
> 
> (Updated Sept. 18, 2017, 5:05 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-3048
> https://issues.apache.org/jira/browse/OOZIE-3048
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-3048 Check El Functions for the coordinator action
> 
> 
> Diffs
> -
> 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
>  650e7f8c 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordPushDependencyCheckXCommand.java
>  0ad39703 
>   core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java fd2f92dc 
>   core/src/main/java/org/apache/oozie/coord/ElException.java PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionInputCheckXCommand.java
>  bbe9ea7a 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordPushDependencyCheckXCommand.java
>  25f250ce 
>   core/src/test/resources/coord-action-for-invalid-elfunction.xml 
> PRE-CREATION 
>   core/src/test/resources/coord-job-for-invalid-elfunction.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62387/diff/1/
> 
> 
> Testing
> ---
> 
> tested locally
> 
> 
> Thanks,
> 
> Satish Saley
> 
>

[jira] [Commented] (OOZIE-3058) nocleanup option is missing in oozie-coordinator-0.5.xsd

[Rohini Palaniswamy (JIRA)]

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

Rohini Palaniswamy commented on OOZIE-3058:
---

+1

> nocleanup option is missing in oozie-coordinator-0.5.xsd
> 
>
> Key: OOZIE-3058
> URL: https://issues.apache.org/jira/browse/OOZIE-3058
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3058-1.patch
>
>
> nocleanup option is missing in oozie-coordinator-0.5.xsd which is there in 
> [oozie-coordinator-0.4.xsd|https://github.com/apache/oozie/blob/master/client/src/main/resources/oozie-coordinator-0.4.xsd#L119].
>  And it is missing in documentation for versions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Review Request 62387: OOZIE-3048 Check El Functions for the coordinator action

[Satish Saley]

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

Review request for oozie.


Bugs: OOZIE-3048
https://issues.apache.org/jira/browse/OOZIE-3048


Repository: oozie-git


Description
---

OOZIE-3048 Check El Functions for the coordinator action


Diffs
-

  
core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
 650e7f8c 
  
core/src/main/java/org/apache/oozie/command/coord/CoordPushDependencyCheckXCommand.java
 0ad39703 
  core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java fd2f92dc 
  core/src/main/java/org/apache/oozie/coord/ElException.java PRE-CREATION 
  
core/src/test/java/org/apache/oozie/command/coord/TestCoordActionInputCheckXCommand.java
 bbe9ea7a 
  
core/src/test/java/org/apache/oozie/command/coord/TestCoordPushDependencyCheckXCommand.java
 25f250ce 
  core/src/test/resources/coord-action-for-invalid-elfunction.xml PRE-CREATION 
  core/src/test/resources/coord-job-for-invalid-elfunction.xml PRE-CREATION 


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


Testing
---

tested locally


Thanks,

Satish Saley

[jira] [Commented] (OOZIE-3058) nocleanup option is missing in oozie-coordinator-0.5.xsd

[Satish Subhashrao Saley (JIRA)]

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

Satish Subhashrao Saley commented on OOZIE-3058:


It is for output event not for input dataset. 

> nocleanup option is missing in oozie-coordinator-0.5.xsd
> 
>
> Key: OOZIE-3058
> URL: https://issues.apache.org/jira/browse/OOZIE-3058
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-3058-1.patch
>
>
> nocleanup option is missing in oozie-coordinator-0.5.xsd which is there in 
> [oozie-coordinator-0.4.xsd|https://github.com/apache/oozie/blob/master/client/src/main/resources/oozie-coordinator-0.4.xsd#L119].
>  And it is missing in documentation for versions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OOZIE-2296) Add an Oozie diagnostic bundle tool

[Attila Sasvari (JIRA)]

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

Attila Sasvari updated OOZIE-2296:
--
Attachment: OOZIE-2296-001.patch

[~rkanter] I tested your patch and made a minor modification in 
{{saveThreadDumpPage}}  to use the proper API call to get JVM info (sending 
request to {{OOZIE_BASE_URL/admin/jvminfo.jsp}}  instead of 
{{OOZIE_BASE_URL//admin/jvminfo.jsp}}). 

Example run:
{code}
$ bin/oozie-diag-bundle-collector.sh  -jobs 
001-170918144116149-oozie-asas-W -oozie http://localhost:11000/oozie 
-output .
Using Temporary Directory: 
/var/folders/9q/f8p_r6gj0wbck49_dc092q_mgp/T/1505741327859-0
Getting Sharelib Information...Done
Getting Configuration...Done
Getting OS Environment Variables...Done
Getting Java System Properties...Done
Getting Instrumentation...Done
Getting Metrics...Skipping (Metrics are unavailable)
Getting Queue Dump...Done
Getting Thread Dump...Done
Getting Details for 001-170918144116149-oozie-asas-W...Done
Creating Zip File: 
/Users/asasvari/workspace/apache/oozie_dup/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/./oozie-diag-bundle-1505741328389.zip...Done

$ unzip -l 
/Users/asasvari/workspace/apache/oozie_dup/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/./oozie-diag-bundle-1505748797206.zip

Archive:  
/Users/asasvari/workspace/apache/oozie_dup/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/./oozie-diag-bundle-1505748797206.zip
  Length Date   TimeName
    
 2574  09-18-17 17:33   /001-170918144116149-oozie-asas-W/info.txt
  308  09-18-17 17:33   /001-170918144116149-oozie-asas-W/job.properties
 6808  09-18-17 17:33   /001-170918144116149-oozie-asas-W/log.txt
0  09-18-17 17:33   
/001-170918144116149-oozie-asas-W/resolved-actions/
 2045  09-18-17 17:33   
/001-170918144116149-oozie-asas-W/resolved-actions/mr-node.xml
 2559  09-18-17 17:33   /001-170918144116149-oozie-asas-W/workflow.xml
64567  09-18-17 17:33   /effective-oozie-site.xml
27462  09-18-17 17:33   /instrumentation.txt
32359  09-18-17 17:33   /java-sys-props.txt
 3557  09-18-17 17:33   /os-env-vars.txt
  279  09-18-17 17:33   /queue-dump.txt
38906  09-18-17 17:33   /sharelib.txt
   102263  09-18-17 17:33   /thread-dump.html
    ---
   283687   13 files
{code}

Tests and documentation are still missing.

> Add an Oozie diagnostic bundle tool
> ---
>
> Key: OOZIE-2296
> URL: https://issues.apache.org/jira/browse/OOZIE-2296
> Project: Oozie
>  Issue Type: New Feature
>  Components: tools
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-2296-001.patch
>
>
> To help with our support cases, I've built a tool that collects a bunch of 
> job and other information from Oozie that throws it all in a tarball.  The 
> idea is that the user can just click a button in Cloudera Manager, and it 
> will run this tool.  
> This tool could be useful for others as an easy way to get information out of 
> Oozie, so I thought I'd contribute it here.  It's built as a "tool" (so it 
> sits next to the sharelib and database tools), and simply uses the Oozie 
> client for getting pretty much everything, so it doesn't require anything 
> special.
> Here's the information that it can get:
> # Sharelib: {{ooze admin -shareliblist}} and {{oozie admin -shareliblist 
> }}
> # Oozie Server's resolved loaded configuration (from admin endpoint)
> # Other admin commands output (queue dump, env vars, etc)
> # Thread dump (HOST:11000/oozie/admin/jvminfo.jsp)
> # Details from last n jobs and/or specific list of jobs
> #- job.properties contents
> #- XML definition
> #- verbose status for each job and each action etc
> #- Oozie logs
> #- Unfortunately, we can't get the launcher jobs' logs from Hadoop
> # Metrics/Instrumentation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 61560: OOZIE-2909 LauncherAM: rewrite UGI calls

[Attila Sasvari]

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




core/src/main/java/org/apache/oozie/ErrorCode.java
Lines 92 (patched)


typo



core/src/main/java/org/apache/oozie/action/hadoop/JHSCredentials.java
Lines 82 (patched)


getDelegationTokenFromJHS



core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
Line 1092 (original), 1045 (patched)


extract method



sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java
Lines 177 (patched)


``Token \"\" is not removed : `` or something 
would help to understand what is happenning



sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/ShellMain.java
Line 69 (original), 69 (patched)


Could you explain why it is necessary to kill child yarn jobs? If it is the 
first job, then it does not look necessary



sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/TestLauncherAM.java
Line 234 (original), 233 (patched)


what do you test here? Is the testname 
``testLauncherJobConfCannotBeLoaded`` still correct?


- Attila Sasvari


On Sept. 17, 2017, 7:06 a.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61560/
> ---
> 
> (Updated Sept. 17, 2017, 7:06 a.m.)
> 
> 
> Review request for oozie, Attila Sasvari, Peter Bacsko, Robert Kanter, and 
> Rohini Palaniswamy.
> 
> 
> Bugs: OOZIE-2909
> https://issues.apache.org/jira/browse/OOZIE-2909
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Changing UGI calls and cleaning up things around requesting tokens.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/ErrorCode.java 
> 662e1edc9c4b23b3606c751bf5ed4b531ee7ac62 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProperties.java 
> 20f93ce57618a529b1bd83b398add2cd1d96b36e 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProviderFactory.java
>  5ca8d3e80942840a5bba51a06694350929044042 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentialHelper.java 
> 9804c7b673a899cd9c778850c9a64731cc642fb3 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentials.java 
> 52abbf17afa71e702d7871d10a4a190a4d21e47b 
>   core/src/main/java/org/apache/oozie/action/hadoop/HDFSCredentials.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/HadoopTokenHelper.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
> 4add5f14cb20ab77c755b81eff939335c0c5fddc 
>   core/src/main/java/org/apache/oozie/action/hadoop/Hive2Credentials.java 
> 0b495f75842b0033a3337ef6728a334bf5651770 
>   core/src/main/java/org/apache/oozie/action/hadoop/JHSCredentials.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 49fd4b8560b21aef725c3268f0ec0e7f46a46ee9 
>   core/src/main/java/org/apache/oozie/action/hadoop/YarnRMCredentials.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java 
> 187cee2290ba4bbe358913d28a052d9c75f2369a 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestHadoopTokenHelper.java 
> PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> d1d78fd527a425b076edd7bb23ba56ebdba62664 
>   core/src/test/java/org/apache/oozie/action/hadoop/TestShellMain.java 
> a7d6c18a645b50fc35657515480da9967fa74e2e 
>   
> core/src/test/java/org/apache/oozie/command/wf/TestWorkflowActionKillXCommand.java
>  cf77f18c4bdbe95ea66f63aa115ce6f34c90c855 
>   core/src/test/java/org/apache/oozie/service/TestHadoopAccessorService.java 
> 960c2f9750062c98fdf7a2b456d3668069e07ca5 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/AMRMClientAsyncFactory.java
>  b4cbb4b1d9b52aaebfb562c02edc91e15a2a9a2e 
>   
> sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/HdfsOperations.java
>  874d371664ced3ae19a7b5d615c67d4c72e7cfdd 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
> 6a98d6ef3a09a7a75272f3f0f9a9c2fc5472e76d 
>   sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/ShellMain.java 
> bde7f1daf123d663d47f5d2fb2350cfa1ac33ed8 
>   
> sharelib/oozie/src/test/java/org/apache/oozie/action/hadoop/TestHdfsOperations.java
>  68c0f4bafe0322ff0d1007297cd6e8f38c92020a 
>   
> 

[jira] [Commented] (OOZIE-2687) Create XML schema for launcher configurations

[Attila Sasvari (JIRA)]

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

Attila Sasvari commented on OOZIE-2687:
---

Committed to master!

> Create XML schema for launcher configurations
> -
>
> Key: OOZIE-2687
> URL: https://issues.apache.org/jira/browse/OOZIE-2687
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
>Priority: Critical
> Fix For: 5.0.0
>
> Attachments: OOZIE-2687-001.patch, OOZIE-2687-002.patch, 
> OOZIE-2687-003.patch, OOZIE-2687-008.patch, OOZIE-2687-009.patch, 
> OOZIE-2687-010.patch, OOZIE-2687-011.patch
>
>
> It was possible to manipulate the MapperLauncher's environment through 
> properties like:
> # mapreduce.map.memory.mb 
> # mapreduce.map.cpu.vcores
> # mapred.child.env
> # mapred.child.java.opts  
> # mapred.job.queue.name  - ability to set launcher queue
> E.g. We were using mapred.child.env to pass SPARK_HOME to the LauncherMapper 
> and make PySpark work. 
> Fixing OOZIE-2596 added a hack. We should decide how we support or break 
> compatibility and how we allow the manipulation of the Launcher environment.
> Verify if the new launcher section in global applies to actions in 
> sub-workflows as well. It did not use to work before and was only fixed in 
> OOZIE-2030. It would be good to have that testcase 
> (TestSubWorkflowActionExecutor. testParentGlobalConf) updated with the new 
> launcher section as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2909) LauncherAM: rewrite UGI calls

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2909:
---

[~rkanter], [~pbacsko], [~asasvari] please review my last changeset.

> LauncherAM: rewrite UGI calls
> -
>
> Key: OOZIE-2909
> URL: https://issues.apache.org/jira/browse/OOZIE-2909
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>Assignee: Peter Cseh
>Priority: Blocker
> Attachments: OOZIE-2909-001.patch, OOZIE-2909-002.patch, 
> OOZIE-2909-003.patch, OOZIE-2909-004.patch, OOZIE-2909-005.patch, 
> OOZIE-2909-006.patch, OOZIE-2909-007.patch
>
>
> There are two problems in LauncherAM:
> 1) In a kerberized cluster, we have to use {{UGI.getLoginUser()}} even though 
> a call to {{createRemoteUser()}} should be enough, just like in 
> {{MRAppMaster.java}}. Reference code:
> https://github.com/apache/hadoop/blob/3ed3062fe3979ff55a411b730a8eee2b2c96d6b3/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java#L1718-L1726
> 2) It's enough if we wrap the whole LauncherAM logic in a single {{doAs()}} 
> call. No need for multiple {{doAs()}}, just makes the whole thing more 
> complicated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OOZIE-2687) Create XML schema for launcher configurations

[Peter Bacsko (JIRA)]

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

Peter Bacsko commented on OOZIE-2687:
-

+1

> Create XML schema for launcher configurations
> -
>
> Key: OOZIE-2687
> URL: https://issues.apache.org/jira/browse/OOZIE-2687
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Attila Sasvari
>Priority: Critical
> Attachments: OOZIE-2687-001.patch, OOZIE-2687-002.patch, 
> OOZIE-2687-003.patch, OOZIE-2687-008.patch, OOZIE-2687-009.patch, 
> OOZIE-2687-010.patch, OOZIE-2687-011.patch
>
>
> It was possible to manipulate the MapperLauncher's environment through 
> properties like:
> # mapreduce.map.memory.mb 
> # mapreduce.map.cpu.vcores
> # mapred.child.env
> # mapred.child.java.opts  
> # mapred.job.queue.name  - ability to set launcher queue
> E.g. We were using mapred.child.env to pass SPARK_HOME to the LauncherMapper 
> and make PySpark work. 
> Fixing OOZIE-2596 added a hack. We should decide how we support or break 
> compatibility and how we allow the manipulation of the Launcher environment.
> Verify if the new launcher section in global applies to actions in 
> sub-workflows as well. It did not use to work before and was only fixed in 
> OOZIE-2030. It would be good to have that testcase 
> (TestSubWorkflowActionExecutor. testParentGlobalConf) updated with the new 
> launcher section as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (106 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3054  Disable erasure coding for sharelib if Oozie runs on Hadoop 3
https://issues-test.apache.org/jira/browse/OOZIE-3054
OOZIE-3031  Coord job with only unresolved dependencies doesn't timeout
https://issues-test.apache.org/jira/browse/OOZIE-3031
OOZIE-3022  fix for warning has no file and won't be listed in dependency files 
details
https://issues-test.apache.org/jira/browse/OOZIE-3022
OOZIE-3002  address findbugs errors in client lib
https://issues-test.apache.org/jira/browse/OOZIE-3002
OOZIE-3001  core library has many instances of warnings with trailing spaces 
and lines longer than 132 chars
https://issues-test.apache.org/jira/browse/OOZIE-3001
OOZIE-2997  files contain trailing white spaces in client lib
https://issues-test.apache.org/jira/browse/OOZIE-2997
OOZIE-2996  add option for -UseGCOverheadLimit to maven opts as sometimes local 
testing fails
https://issues-test.apache.org/jira/browse/OOZIE-2996
OOZIE-2978  Remove code that handles Pig versions before 0.8 
https://issues-test.apache.org/jira/browse/OOZIE-2978
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues-test.apache.org/jira/browse/OOZIE-2975
OOZIE-2969  Drop support for Java 1.7
https://issues-test.apache.org/jira/browse/OOZIE-2969
OOZIE-2964  Add -Xdoclint:none to javadoc opts to avoid warnings
https://issues-test.apache.org/jira/browse/OOZIE-2964
OOZIE-2963  getting error in build ArtifactNotFoundException: Could not find 
artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
https://issues-test.apache.org/jira/browse/OOZIE-2963
OOZIE-2962  bump maven-javadoc-plugin to 2.10.4
https://issues-test.apache.org/jira/browse/OOZIE-2962
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues-test.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues-test.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues-test.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues-test.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues-test.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues-test.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues-test.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-test.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues-test.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues-test.apache.org/jira/browse/OOZIE-2914
OOZIE-2909  LauncherAM: rewrite UGI calls
https://issues-test.apache.org/jira/browse/OOZIE-2909
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues-test.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues-test.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues-test.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues-test.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-test.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues-test.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues-test.apache.org/jira/browse/OOZIE-2826
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (107 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3054  Disable erasure coding for sharelib if Oozie runs on Hadoop 3
https://issues.apache.org/jira/browse/OOZIE-3054
OOZIE-3048  Check El Functions for the coordinator action
https://issues.apache.org/jira/browse/OOZIE-3048
OOZIE-3031  Coord job with only unresolved dependencies doesn't timeout
https://issues.apache.org/jira/browse/OOZIE-3031
OOZIE-3022  fix for warning has no file and won't be listed in dependency files 
details
https://issues.apache.org/jira/browse/OOZIE-3022
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-3001  core library has many instances of warnings with trailing spaces 
and lines longer than 132 chars
https://issues.apache.org/jira/browse/OOZIE-3001
OOZIE-2997  files contain trailing white spaces in client lib
https://issues.apache.org/jira/browse/OOZIE-2997
OOZIE-2996  add option for -UseGCOverheadLimit to maven opts as sometimes local 
testing fails
https://issues.apache.org/jira/browse/OOZIE-2996
OOZIE-2978  Remove code that handles Pig versions before 0.8 
https://issues.apache.org/jira/browse/OOZIE-2978
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-2969  Drop support for Java 1.7
https://issues.apache.org/jira/browse/OOZIE-2969
OOZIE-2964  Add -Xdoclint:none to javadoc opts to avoid warnings
https://issues.apache.org/jira/browse/OOZIE-2964
OOZIE-2963  getting error in build ArtifactNotFoundException: Could not find 
artifact org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde
https://issues.apache.org/jira/browse/OOZIE-2963
OOZIE-2962  bump maven-javadoc-plugin to 2.10.4
https://issues.apache.org/jira/browse/OOZIE-2962
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-2909  LauncherAM: rewrite UGI calls
https://issues.apache.org/jira/browse/OOZIE-2909
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
https://issues.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues.apache.org/jira/browse/OOZIE-2826
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