[jira] [Commented] (OOZIE-2406) Completely rewrite GraphGenerator code
[
https://issues.apache.org/jira/browse/OOZIE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167142#comment-16167142
]
Robert Kanter commented on OOZIE-2406:
--
[~andras.piros], thanks for working on this; I'm glad to see us move forward on
this issue. The graphviz diagram looks better too :)
Can you post your patch to ReviewBoard?
> 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-many-nodes.png, jung-many-nodes.png,
> OOZIE-2406.004.patch, OOZIE-2406.004.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] [Commented] (OOZIE-2406) Completely rewrite GraphGenerator code
[
https://issues.apache.org/jira/browse/OOZIE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167081#comment-16167081
]
Hadoop QA commented on OOZIE-2406:
--
Testing JIRA OOZIE-2406
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:red}-1{color} the patch contains 5 line(s) longer than 132
characters
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
.{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [17] new bugs found below threshold in total
that must be fixed.
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:red}-1{color} There are [17] new bugs found below threshold in [core]
that must be fixed, listing only the first [5] ones.
. You can find the FindBugs diff here (look for the red and orange ones):
core/findbugs-new.html
. The top [5] most important FindBugs errors are:
. At GraphGenerator.java:[line 84]: The use of XMLReader.parse(...) is
vulnerable to XML External Entity attacks
. At JungRenderer.java:[line 61]: Unread field:
org.apache.oozie.util.graph.JungRenderer.xIncr; should this field be static?
. At JungRenderer.java:[line 59]: Unread field:
org.apache.oozie.util.graph.JungRenderer.xMargin; should this field be static?
. At JungRenderer.java:[line 62]: Unread field:
org.apache.oozie.util.graph.JungRenderer.yIncr; should this field be static?
. At JungRenderer.java:[line 60]: Unread field:
org.apache.oozie.util.graph.JungRenderer.yMargin; should this field be static?
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {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/spark].
{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: 2015
.Tests rerun: 43
.Tests failed at first run:
org.apache.oozie.action.hadoop.TestJavaActionExecutor,
{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/21/
> 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-many-nodes.png, jung-many-nodes.png,
> OOZIE-2406.004.patch, OOZIE-2406.004.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
Failed: OOZIE-2406 PreCommit Build #21
Jira: https://issues.apache.org/jira/browse/OOZIE-2406 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/21/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 1.93 MB...] +1 the patch does not seem to introduce new javac warnings -1 There are [17] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [server]. +1 There are no new bugs found in [client]. -1 There are [17] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. You can find the FindBugs diff here (look for the red and orange ones): core/findbugs-new.html The top [5] most important FindBugs errors are: At GraphGenerator.java:[line 84]: The use of XMLReader.parse(...) is vulnerable to XML External Entity attacks At JungRenderer.java:[line 61]: Unread field: org.apache.oozie.util.graph.JungRenderer.xIncr; should this field be static? At JungRenderer.java:[line 59]: Unread field: org.apache.oozie.util.graph.JungRenderer.xMargin; should this field be static? At JungRenderer.java:[line 62]: Unread field: org.apache.oozie.util.graph.JungRenderer.yIncr; should this field be static? At JungRenderer.java:[line 60]: Unread field: org.apache.oozie.util.graph.JungRenderer.yMargin; should this field be static? +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [tools]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/hive]. +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/spark]. +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: 2015 Tests rerun: 43 Tests failed at first run: org.apache.oozie.action.hadoop.TestJavaActionExecutor, +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/21/ % 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 100 3706k 100 3706k0 0 4813k 0 --:--:-- --:--:-- --:--:-- 4813k Adding comment to JIRA Comment added. test-patch exit code: 1 Build step 'Execute shell' marked build as failure [description-setter] Description set: OOZIE-2406 Archiving artifacts [Fast Archiver] Compressed 2.14 MB of artifacts by 36.5% relative to #10 Recording test results Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Updated] (OOZIE-2406) Completely rewrite GraphGenerator code
[
https://issues.apache.org/jira/browse/OOZIE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-2406:
Attachment: OOZIE-2406.004.patch
> 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-many-nodes.png, jung-many-nodes.png,
> OOZIE-2406.004.patch, OOZIE-2406.004.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] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166807#comment-16166807
]
Hadoop QA commented on OOZIE-2949:
--
Testing JIRA OOZIE-2949
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
.{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [client].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 2014
.Tests failed: 0
.Tests errors: 1
.The patch failed the following testcases:
.
.Tests failing with errors:
. testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration)
{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/20/
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2949-0.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Failed: OOZIE-2949 PreCommit Build #20
Jira: https://issues.apache.org/jira/browse/OOZIE-2949 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/20/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 1.59 MB...] +1 There are no new bugs found in total. +1 There are no new bugs found in [client]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [server]. +1 There are no new bugs found in [core]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [tools]. +1 BACKWARDS_COMPATIBILITY +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations +1 the patch does not modify JPA files -1 TESTS Tests run: 2014 Tests failed: 0 Tests errors: 1 The patch failed the following testcases: Tests failing with errors: testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration) +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/20/ % 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 11 3706k 11 413k0 0 563k 0 0:00:06 --:--:-- 0:00:06 563k100 3706k 100 3706k0 0 4581k 0 --:--:-- --:--:-- --:--:-- 43.4M Adding comment to JIRA Comment added. test-patch exit code: 1 Build step 'Execute shell' marked build as failure [description-setter] Description set: OOZIE-2949 Archiving artifacts [Fast Archiver] Compressed 1.79 MB of artifacts by 54.0% relative to #10 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.event.TestEventGeneration.testCoordinatorActionEvent Error Message: E1018: Coord Job Rerun Error: part or all actions are not eligible to rerun! Stack Trace: org.apache.oozie.command.CommandException: E1018: Coord Job Rerun Error: part or all actions are not eligible to rerun! at org.apache.oozie.command.coord.CoordRerunXCommand.rerunChildren(CoordRerunXCommand.java:400) at org.apache.oozie.command.RerunTransitionXCommand.execute(RerunTransitionXCommand.java:97) at org.apache.oozie.command.XCommand.call(XCommand.java:290) at org.apache.oozie.event.TestEventGeneration.testCoordinatorActionEvent(TestEventGeneration.java:363) 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-2687) Create XML schema for launcher configurations
[ https://issues.apache.org/jira/browse/OOZIE-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166649#comment-16166649 ] Attila Sasvari commented on OOZIE-2687: --- Many thanks for the reviews. I've got a Ship it from [~rkanter] on reviewboard https://reviews.apache.org/r/61529/ . I will commit changes to master soon if there are no further comments. > 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)
Failed: OOZIE-2406 PreCommit Build #19
Jira: https://issues.apache.org/jira/browse/OOZIE-2406 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/19/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 671.45 KB...] [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Oozie Main .. SUCCESS [ 2.204 s] [INFO] Apache Oozie Client SUCCESS [ 19.629 s] [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 15.463 s] [INFO] Apache Oozie Share Lib HCatalog SUCCESS [ 8.389 s] [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 6.463 s] [INFO] Apache Oozie Core .. SUCCESS [01:23 min] [INFO] Apache Oozie Share Lib Streaming ... SUCCESS [ 9.877 s] [INFO] Apache Oozie Share Lib Pig . SUCCESS [ 9.521 s] [INFO] Apache Oozie Share Lib Hive SUCCESS [ 10.050 s] [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 10.571 s] [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [ 7.491 s] [INFO] Apache Oozie Examples .. SUCCESS [ 10.452 s] [INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 12.407 s] [INFO] Apache Oozie Share Lib . SUCCESS [ 0.022 s] [INFO] Apache Oozie Docs .. SUCCESS [ 4.208 s] [INFO] Apache Oozie WebApp SUCCESS [ 3.363 s] [INFO] Apache Oozie Tools . SUCCESS [ 12.830 s] [INFO] Apache Oozie MiniOozie . SUCCESS [ 2.688 s] [INFO] Apache Oozie Server SUCCESS [ 12.586 s] [INFO] Apache Oozie Distro SUCCESS [ 2.261 s] [INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [ 4.079 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 04:09 min [INFO] Finished at: 2017-09-14T16:35:49Z [INFO] Final Memory: 625M/1918M [INFO] [TRACE] FindBugs output in HEAD verified and saved Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Applying patch fatal: unrecognized input fatal: unrecognized input Patch failed to apply to head of branch % 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 3706k0 28960 0 5194 0 0:12:10 --:--:-- 0:12:10 5194100 3706k 100 3706k0 0 4914k 0 --:--:-- --:--:-- --:--:-- 18.4M Adding comment to JIRA Comment added. test-patch exit code: 1 Build step 'Execute shell' marked build as failure [description-setter] Description set: OOZIE-2406 Archiving artifacts [Fast Archiver] Compressed 835.73 KB of artifacts by 84.2% relative to #10 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (OOZIE-2406) Completely rewrite GraphGenerator code
[
https://issues.apache.org/jira/browse/OOZIE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166553#comment-16166553
]
Hadoop QA commented on OOZIE-2406:
--
Testing JIRA OOZIE-2406
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> 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-many-nodes.png, jung-many-nodes.png,
> OOZIE-2406.004.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] [Assigned] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Ervits reassigned OOZIE-2949:
---
Assignee: Peter Cseh (was: Artem Ervits)
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Fix For: 5.0.0
>
> Attachments: OOZIE-2949-0.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166492#comment-16166492
]
Artem Ervits commented on OOZIE-2949:
-
[~gezapeti] please go ahead, I'm pretty busy in my day job now to work on this.
Thank you
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
> Fix For: 5.0.0
>
> Attachments: OOZIE-2949-0.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field
[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166466#comment-16166466
]
Peter Cseh commented on OOZIE-2949:
---
I would like to have this fixed @dbist13. Do you have the time to work on this
or can I take this over to continue on your patch?
> Escape quotes whitespaces in Sqoop field
> --
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 4.3.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
> Fix For: 5.0.0
>
> Attachments: OOZIE-2949-0.patch
>
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OOZIE-2406) Completely rewrite GraphGenerator code
[
https://issues.apache.org/jira/browse/OOZIE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-2406:
Attachment: graphviz-many-nodes.png
jung-many-nodes.png
Images generated by both {{GraphRenderer}} implementations {{GraphvizRenderer}}
and {{JungRenderer}}.
> 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-many-nodes.png, jung-many-nodes.png,
> OOZIE-2406.004.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] [Updated] (OOZIE-2406) Completely rewrite GraphGenerator code
[
https://issues.apache.org/jira/browse/OOZIE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-2406:
Attachment: OOZIE-2406.004.patch
[~rkanter] this is how it looks like at the moment.
Currently, two implementations of {{GraphRenderer}} are present:
* {{JungRenderer}}: the one using the old {{net.sf.jung}} dependency
* {{GraphvizRenderer}}: the one using the new {{guru.nidi.graphviz-java}}
dependency
Please have a look.
> 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: OOZIE-2406.004.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] [Commented] (OOZIE-3041) TestWorkflowActionRetryInfoXCommand fails in oozie core module.
[
https://issues.apache.org/jira/browse/OOZIE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166321#comment-16166321
]
Parita Johari commented on OOZIE-3041:
--
Thanks for the fix.
> TestWorkflowActionRetryInfoXCommand fails in oozie core module.
> ---
>
> Key: OOZIE-3041
> URL: https://issues.apache.org/jira/browse/OOZIE-3041
> Project: Oozie
> Issue Type: Test
> Components: tests
>Affects Versions: 4.3.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Andras Piros
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-3041.001.patch, OOZIE-3041.002.patch,
> OOZIE-3041.003.patch
>
>
> Stacktrace
> {code:java}
> junit.framework.ComparisonFailure: expected:<... 25 Aug 2017 19:31:2[8] GMT>
> but was:<... 25 Aug 2017 19:31:2[9] GMT>
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
> at junit.framework.TestCase.assertEquals(TestCase.java:269)
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.validateRetryConsoleUrl(TestWorkflowActionRetryInfoXCommand.java:178)
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.testRetryConsoleUrlForked(TestWorkflowActionRetryInfoXCommand.java:123)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OOZIE-2687) Create XML schema for launcher configurations
[
https://issues.apache.org/jira/browse/OOZIE-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166096#comment-16166096
]
Attila Sasvari commented on OOZIE-2687:
---
Thanks [~rkanter] for your response! I opened OOZIE-3056.
In the mean time, jenkins build job finished with Patch 11:
https://builds.apache.org/job/PreCommit-OOZIE-Build/18/console
Results:
{code}
+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 contains 5 line(s) longer than 132 characters
+1 the patch does adds/modifies 9 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 77 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
0 There are [2] new bugs found in total that would be nice to have fixed.
+1 There are no new bugs found in [docs].
+1 There are no new bugs found in [examples].
+1 There are no new bugs found in [tools].
0 There are [2] new bugs found in [core] that would be nice to have fixed.
You can find the FindBugs diff here: core/findbugs-new.html
+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 [sharelib/distcp].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [sharelib/hcatalog].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/pig].
+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 rerun: 53
Tests failed at first run:
org.apache.oozie.command.coord.TestCoordActionsKillXCommand,org.apache.oozie.action.hadoop.TestJavaActionExecutor,
+1 DISTRO
+1 distro tarball builds with the patch
{code}
Only issue: {{-1 the patch contains 5 line(s) longer than 132 characters}}
For some reason, comment was not added here:
{code}
Adding comment to JIRA
Could not find issue with key: 'OOZIE-2687'
Remote error: ; nested exception is:
java.net.SocketException: Connection reset
{code}
[~gezapeti], [~pbacsko], [~rkanter] please take a look at the latest patch and
let me if you have any other review comments. Documentation will be done as
part of OOZIE-2600.
> 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] [Created] (OOZIE-3056) Implement new mechanism to specify ShareLibs for workflow actions
Attila Sasvari created OOZIE-3056:
-
Summary: Implement new mechanism to specify ShareLibs for workflow
actions
Key: OOZIE-3056
URL: https://issues.apache.org/jira/browse/OOZIE-3056
Project: Oozie
Issue Type: New Feature
Components: core
Affects Versions: 5.0.0
Reporter: Attila Sasvari
OOZIE-2687 introduces the {{launcher}} element for workflows:
{code}
1024
1
-Dsome.property=true -XX:+RandomJVMSwitch
key=value
root.oozie
spark,hive
{code}
The purpose of this ticket is to discuss and implement new mechanism for
handling ShareLib.
{{addActionShareLib}} in {{JavaActionExecutor}} should adjusted. Regarding
"precedence order":
if global and an action level {{launcher}} and {{configuration}} (e.g.
{{oozie.action.sharelib.for.#ACTIONTYPE#}}) tries to override the sharelib the
following should apply:
{quote}
config properties defined in an action's have priority over an
action's , which has priority over the global section's
and , which has priority over the action defaults in
oozie-site, and so on.
{quote}
Here we have multiple choices how to handle sharelib:
- Alternative 1: override sharelib in a way that is consistent with current way
of handling Oozie configuration settings.
- Alternative 2: make sharelib additive
-- For example, if there is a global {{launcher}} with {{sharelib}} element in
a workflow that includes multiple ShareLibs (e.g. A,B), and
{{oozie.action.sharelib.for.#ACTIONTYPE#}} is also specified for an action's
configuration (e.g. C,D), then we take the union of the specified entities
(A,B,C,D would be included).
-- It's inconsistent with everything else
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OOZIE-3055) Release Oozie 5.0.0
Andras Piros created OOZIE-3055:
---
Summary: Release Oozie 5.0.0
Key: OOZIE-3055
URL: https://issues.apache.org/jira/browse/OOZIE-3055
Project: Oozie
Issue Type: Task
Affects Versions: 4.3.0
Reporter: Andras Piros
Fix For: 5.0.0
It's been a while where we had a decent {{4.3.0}} release. Let's roll for
{{5.0.0}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OOZIE-3041) TestWorkflowActionRetryInfoXCommand fails in oozie core module.
[
https://issues-test.apache.org/jira/browse/OOZIE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3041:
Attachment: OOZIE-3041.003.patch
> TestWorkflowActionRetryInfoXCommand fails in oozie core module.
> ---
>
> Key: OOZIE-3041
> URL: https://issues-test.apache.org/jira/browse/OOZIE-3041
> Project: Oozie
> Issue Type: Test
> Components: tests
>Affects Versions: 4.3.0
> Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Parita Johari
>Assignee: Andras Piros
>Priority: Minor
> Fix For: 5.0.0
>
> Attachments: OOZIE-3041.001.patch, OOZIE-3041.002.patch,
> OOZIE-3041.003.patch
>
>
> Stacktrace
> {code:java}
> junit.framework.ComparisonFailure: expected:<... 25 Aug 2017 19:31:2[8] GMT>
> but was:<... 25 Aug 2017 19:31:2[9] GMT>
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
> at junit.framework.TestCase.assertEquals(TestCase.java:269)
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.validateRetryConsoleUrl(TestWorkflowActionRetryInfoXCommand.java:178)
> at
> org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand.testRetryConsoleUrlForked(TestWorkflowActionRetryInfoXCommand.java:123)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.0.11#70121)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (105 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-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 for Oozie CLI during packaging https://issues.apache.org/jira/browse/OOZIE-2795 OOZIE-2791 ShareLib
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (106 issues) Subscriber: ooziedaily Key Summary OOZIE-3041 TestWorkflowActionRetryInfoXCommand fails in oozie core module. https://issues-test.apache.org/jira/browse/OOZIE-3041 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-2916 Set a job name for the MR Action's child job https://issues-test.apache.org/jira/browse/OOZIE-2916 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
