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

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2645:
---

+1

> Deprecate 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
>
> Attachments: OOZIE-2645.001.patch, OOZIE-2645.002.patch, 
> OOZIE-2645.003.patch, OOZIE-2645.004.patch
>
>
> 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.
> 
> Update: for 5.0.0 we only deprecate {{InstrumentationService}}, and make 
> {{MetricsInstrumentationService}} the default.



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

[jira] [Commented] (OOZIE-2726) Flaky test due to daylight saving changes

[Peter Cseh (JIRA)]

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

Peter Cseh commented on OOZIE-2726:
---

Thanks for fixing this one [~andras.piros] and [~satishsaley]!
+1

> Flaky test due to daylight saving changes
> -
>
> Key: OOZIE-2726
> URL: https://issues.apache.org/jira/browse/OOZIE-2726
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Satish Subhashrao Saley
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2726-1.patch, OOZIE-2726-2.patch, 
> OOZIE-2726-3.patch, OOZIE-2726-4.patch, OOZIE-2726-5.patch, 
> OOZIE-2726.006.patch, OOZIE-2726.007.patch, OOZIE-2726.008.patch
>
>
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup
> {code}
> Error Message
> expected: but was:
> Stacktrace
> junit.framework.AssertionFailedError: expected: 
> but was:
>   at junit.framework.Assert.fail(Assert.java:50)
>   at junit.framework.Assert.failNotEquals(Assert.java:287)
>   at junit.framework.Assert.assertEquals(Assert.java:67)
>   at junit.framework.Assert.assertEquals(Assert.java:74)
>   at 
> org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand.testMaterizationLookup(TestCoordMaterializeTransitionXCommand.java:582)
>   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:483)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:243)
>   at junit.framework.TestSuite.run(TestSuite.java:238)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:24)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   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:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[DISCUSS] Wondering why 5.0 beta not using fluido skin

[Artem Ervits]

If you look at
https://oozie.apache.org/docs/5.0.0-beta1/DG_SparkActionExtension.html

I'd have the old look and feel, I know there was a Jira to switch to Fluido
skin that made things pop, see difference on main page

https://oozie.apache.org/

Even worse it works with 4.3.0 but now with 5.0, does this Jira need to be
applied to Branch 5.x and master?

https://issues.apache.org/jira/plugins/servlet/mobile#issue/OOZIE-3163

Re: Review Request 66084: Oozie-core fails with checkstyle errors.

[András Piros via Review Board]

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


Ship it!




Ship It!

- András Piros


On March 20, 2018, 5:36 a.m., Alisha Prabhu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66084/
> ---
> 
> (Updated March 20, 2018, 5:36 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-3176
> https://issues.apache.org/jira/browse/OOZIE-3176
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/BundleActionBean.java eeec549 
>   core/src/main/java/org/apache/oozie/BundleJobBean.java dec0967 
>   core/src/main/java/org/apache/oozie/CoordinatorActionBean.java ddec1e6 
>   core/src/main/java/org/apache/oozie/CoordinatorJobBean.java 5999f40 
>   core/src/main/java/org/apache/oozie/CoordinatorJobInfo.java 04c5bc9 
>   core/src/main/java/org/apache/oozie/DagELFunctions.java 22ac624 
>   core/src/main/java/org/apache/oozie/SLAEventBean.java b30867b 
>   core/src/main/java/org/apache/oozie/WorkflowActionBean.java 6b05b89 
>   core/src/main/java/org/apache/oozie/WorkflowJobBean.java cb06bec 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> 122dfd0 
>   core/src/main/java/org/apache/oozie/client/rest/JsonBean.java c8bd7c2 
>   
> core/src/main/java/org/apache/oozie/command/bundle/BundleJobSuspendXCommand.java
>  669ac5e 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
>  179cc45 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionStartXCommand.java
>  16d7036 
>   core/src/main/java/org/apache/oozie/command/coord/CoordChangeXCommand.java 
> ff7bf8a 
>   core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
> fbc6152 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java
>  2b91253 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordPushDependencyCheckXCommand.java
>  1e864ea 
>   core/src/main/java/org/apache/oozie/command/coord/CoordResumeXCommand.java 
> 1998924 
>   core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java 
> 42bdc99 
>   core/src/main/java/org/apache/oozie/command/coord/CoordSuspendXCommand.java 
> 1195ef0 
>   core/src/main/java/org/apache/oozie/command/wf/ActionEndXCommand.java 
> 86ee1cc 
>   core/src/main/java/org/apache/oozie/command/wf/ActionKillXCommand.java 
> 61891b8 
>   core/src/main/java/org/apache/oozie/command/wf/ActionStartXCommand.java 
> 71c29cd 
>   core/src/main/java/org/apache/oozie/command/wf/ActionXCommand.java 29ccd32 
>   core/src/main/java/org/apache/oozie/coord/CoordUtils.java 2874bf6 
>   core/src/main/java/org/apache/oozie/coord/HCatELFunctions.java f40f406 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/BundleJobsGetRunningOrPendingJPAExecutor.java
>  18ceb10 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/CoordActionRemoveJPAExecutor.java
>  02a4f68 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/CoordJobGetRunningActionsCountJPAExecutor.java
>  274b3c1 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/WorkflowActionRetryManualGetJPAExecutor.java
>  51449db 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/WorkflowInfoWithActionsSubsetGetJPAExecutor.java
>  43c7d08 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/WorkflowJobsBasicInfoFromParentId.java
>  4b8adfb 
>   core/src/main/java/org/apache/oozie/service/AuthorizationService.java 
> d76e1ea 
>   core/src/main/java/org/apache/oozie/service/PurgeService.java c2c966b 
>   core/src/main/java/org/apache/oozie/servlet/JsonRestServlet.java 404d3cd 
>   core/src/main/java/org/apache/oozie/servlet/ServletUtilities.java 9cdd915 
>   core/src/main/java/org/apache/oozie/servlet/V0AdminServlet.java d4a0989 
>   core/src/main/java/org/apache/oozie/servlet/V0JobsServlet.java ff50f3d 
>   core/src/main/java/org/apache/oozie/servlet/V1JobServlet.java 0d275fd 
>   core/src/main/java/org/apache/oozie/sla/SLARegistrationBean.java 5eac78c 
>   core/src/main/java/org/apache/oozie/sla/SLASummaryBean.java e9ea9ba 
>   core/src/main/java/org/apache/oozie/sla/listener/SLAEmailEventListener.java 
> d08521c 
>   core/src/main/java/org/apache/oozie/store/WorkflowStore.java 821abc5 
>   core/src/main/java/org/apache/oozie/util/OozieRollingPolicy.java 625053c 
>   core/src/main/java/org/apache/oozie/util/ParameterVerifier.java f3f4630 
>   core/src/main/java/org/apache/oozie/util/ParameterVerifierException.java 
> ef9a591 
>   core/src/main/java/org/apache/oozie/ut

[jira] [Commented] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3176:
-

Thanks for the contribution [~alishap]! +1

> Oozie-core fails with checkstyle errors.
> 
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: Checkstyle-erros.txt, OOZIE-3176-001.patch, 
> OOZIE-3176-002.patch
>
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
> I have attached the Checkstyle-errors.txt file, that has the errors occurred 
> while building.



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

Re: [DISCUSS] Wondering why 5.0 beta not using fluido skin

[Andras Piros]

Hi Artem,

*OOZIE-3163 * has been
merged to master after 5.0.0-beta1.

Will be part of 5.0.0 (we haven't branched yet), so we'll have Fluido skin
:)

Andras

On Tue, Mar 27, 2018 at 11:23 AM, Artem Ervits 
wrote:

> If you look at
> https://oozie.apache.org/docs/5.0.0-beta1/DG_SparkActionExtension.html
>
> I'd have the old look and feel, I know there was a Jira to switch to Fluido
> skin that made things pop, see difference on main page
>
> https://oozie.apache.org/
>
> Even worse it works with 4.3.0 but now with 5.0, does this Jira need to be
> applied to Branch 5.x and master?
>
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/OOZIE-3163
>

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors

[Andras Piros (JIRA)]

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

Andras Piros updated OOZIE-3176:

Summary: Oozie-core fails with checkstyle errors  (was: Oozie-core fails 
with checkstyle errors.)

> Oozie-core fails with checkstyle errors
> ---
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: Checkstyle-erros.txt, OOZIE-3176-001.patch, 
> OOZIE-3176-002.patch
>
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
> I have attached the Checkstyle-errors.txt file, that has the errors occurred 
> while building.



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

Review Request 66305: OOZIE-3199 Let system property restriction configurable

[Denes Bodo]

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

Review request for oozie and András Piros.


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


Repository: oozie-git


Description
---

Let system property restriction configurable


Diffs
-

  core/src/main/java/org/apache/oozie/service/ConfigurationService.java 618d5e6 
  core/src/main/resources/oozie-default.xml 6f89258 


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


Testing
---

Tested on private Hadoop cluster.


Thanks,

Denes Bodo

[jira] [Commented] (OOZIE-3199) Let system property restriction configurable

[Denes Bodo (JIRA)]

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

Denes Bodo commented on OOZIE-3199:
---

[~andras.piros] I managed to upload the diff. Thanks for your time.
https://reviews.apache.org/r/66305/


> Let system property restriction configurable
> 
>
> Key: OOZIE-3199
> URL: https://issues.apache.org/jira/browse/OOZIE-3199
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Attachments: OOZIE-3199-001.patch, OOZIE-3199-002.patch
>
>
> Currently Oozie restricts resolution of system properties by default. In some 
> cases that would be nice if as an administrator I could set a whitelist of 
> enabled system property names.
> Suggestion will be provided asap.



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

[jira] [Comment Edited] (OOZIE-3199) Let system property restriction configurable

[Denes Bodo (JIRA)]

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

Denes Bodo edited comment on OOZIE-3199 at 3/27/18 12:02 PM:
-

[~andras.piros] I managed to upload the diff. Thanks for your time.
https://reviews.apache.org/r/66305/

I know there are no test cases regarding this change. First I would like to 
consult the community what is the opinion about this.


was (Author: dionusos):
[~andras.piros] I managed to upload the diff. Thanks for your time.
https://reviews.apache.org/r/66305/


> Let system property restriction configurable
> 
>
> Key: OOZIE-3199
> URL: https://issues.apache.org/jira/browse/OOZIE-3199
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Attachments: OOZIE-3199-001.patch, OOZIE-3199-002.patch
>
>
> Currently Oozie restricts resolution of system properties by default. In some 
> cases that would be nice if as an administrator I could set a whitelist of 
> enabled system property names.
> Suggestion will be provided asap.



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

[VOTE] Release Oozie 5.0.0 (candidate 0)

[Andras Piros]

Hi there,

I have created a build for Oozie 5.0.0, release candidate 0.

This release introduces major changes:
- moved launcher from MapReduce AM to YARN AM,
- switched from Tomcat to embedded Jetty,
- updated third party libraries,
- completely rewritten workflow graph generator,
- JDK 8 support,
- deprecated Instrumentation in favor of Metrics,
- added indexes to speed up DB queries,
- fixed CVE-2017-15712

Keys to verify the signature of the release artifact are available at

 http://www.apache.org/dist/oozie/KEYS

Please download, test, and try it out:

http://people.apache.org/~andras/oozie-5.0.0-rc0/

The release candidate, sha512 signature, gpg signature, and rat report can
all be found
at the above address.

The vote is open until Saturday, March 31, 2018 at 12:00am PDT.

Thanks,

Andras Piros

[jira] [Commented] (OOZIE-3196) Authorization: restrict world readability by user

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3196:
-

I heard from another client who's only concerned with who submitted the job and 
when etc,  as underlining actions are already governed by their respective 
authorization mechanisms, in their case Ranger.

> Authorization: restrict world readability by user
> -
>
> Key: OOZIE-3196
> URL: https://issues.apache.org/jira/browse/OOZIE-3196
> Project: Oozie
>  Issue Type: New Feature
>  Components: bundle, coordinator, workflow
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Priority: Major
>
> The [*current authorization 
> model*|https://issues.apache.org/jira/browse/OOZIE-228] does not fit the 
> enterprise requirements as everything is readable and writable by everyone by 
> default.
> Write access can be restricted using authorization but restricting read 
> rights is only possible via Yarn ACLs and HDFS rights which still does not 
> prevent accessing the workflow, coordinator or bundle job’s configurations 
> for everyone.
> Improve authorization so it’s possible to configure read/write access for 
> workflows, coordinators, and bundles in a more granular way. Could involve 
> Sentry during implementation or create and design a new system that fits the 
> needs.



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

[jira] [Commented] (OOZIE-3199) Let system property restriction configurable

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-3199:
-

[~dionusos] thanks for the contribution!

Leaving my overall opinion on ReviewBoard for the WIP patch.

> Let system property restriction configurable
> 
>
> Key: OOZIE-3199
> URL: https://issues.apache.org/jira/browse/OOZIE-3199
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Attachments: OOZIE-3199-001.patch, OOZIE-3199-002.patch
>
>
> Currently Oozie restricts resolution of system properties by default. In some 
> cases that would be nice if as an administrator I could set a whitelist of 
> enabled system property names.
> Suggestion will be provided asap.



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

Re: Review Request 66305: OOZIE-3199 Let system property restriction configurable

[András Piros via Review Board]

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



Interesting idea!

However, in the existing approach within `ConfigurationService#loadConf()` 
following handling of system properties is implemented:

* `ConfigurationService#IGNORE_SYS_PROPS` defines the system properties that 
should never be overwritten, neither from config file nor from `-D` option
* `ConfigurationService#IGNORE_SYS_PROPS` contains both hard coded and 
additionally configured entries
* `ConfigurationService#CONF_SYS_PROPS` defines a fixed set of system 
properties. When the actual system property is present, and isn't contained in 
`ConfigurationService#IGNORE_SYS_PROPS`, a `Configuration` entry is inserted
* in addition to `ConfigurationService#CONF_SYS_PROPS`, all the already 
existing `Configuration` entries are checked for existence as a system 
property. If present and not contained in 
`ConfigurationService#IGNORE_SYS_PROPS`, the appropriare `Configuration` entry 
is updated

I'd suggest that the handling of the extra, admin-allowed system properties 
happens as the last step, and an extra filtering should also be taken for 
absence inside `ConfigurationService#IGNORE_SYS_PROPS`. The prefix should also 
be `oozie.`

- András Piros


On March 27, 2018, 11:59 a.m., Denes Bodo wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66305/
> ---
> 
> (Updated March 27, 2018, 11:59 a.m.)
> 
> 
> Review request for oozie and András Piros.
> 
> 
> Bugs: OOZIE-3199
> https://issues.apache.org/jira/browse/OOZIE-3199
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Let system property restriction configurable
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/service/ConfigurationService.java 
> 618d5e6 
>   core/src/main/resources/oozie-default.xml 6f89258 
> 
> 
> Diff: https://reviews.apache.org/r/66305/diff/1/
> 
> 
> Testing
> ---
> 
> Tested on private Hadoop cluster.
> 
> 
> Thanks,
> 
> Denes Bodo
> 
>

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (105 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
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-3185  Conflicting JARs org.apache.derby exist in Oozie
https://issues.apache.org/jira/browse/OOZIE-3185
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3134  Potential inconsistency between the in-memory SLA map and the Oozie 
database
https://issues.apache.org/jira/browse/OOZIE-3134
OOZIE-3109  Escape log-streaming's HTML-specific characters
https://issues.apache.org/jira/browse/OOZIE-3109
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/brows