[jira] [Commented] (OOZIE-3109) Escape log-streaming's HTML-specific characters
[ https://issues.apache.org/jira/browse/OOZIE-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356976#comment-16356976 ] Hadoop QA commented on OOZIE-3109: -- PreCommit-OOZIE-Build started > Escape log-streaming's HTML-specific characters > --- > > Key: OOZIE-3109 > URL: https://issues.apache.org/jira/browse/OOZIE-3109 > Project: Oozie > Issue Type: Bug >Affects Versions: 4.3.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Major > Attachments: OOZIE-3109-v001.patch > > > That can be a security problem if we do not encode the stream read from log > files before transferred to the web browser. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode
[
https://issues.apache.org/jira/browse/OOZIE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356995#comment-16356995
]
Peter Cseh commented on OOZIE-3173:
---
I don't like the amount of flaky tests we have - again - in our pre-commit hook.
> Coordinator job with frequency using cron syntax creates only one action in
> catchup mode
>
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time
> lies also in the past), would create only one action, independent of
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now,
> endTime), startTime + frequency * throttle)}}.
> Some examples, {{frequency="0 * * * *"}}:
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{1}} -> one action should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{3}} -> three actions should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{15}} -> ten actions should be created
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode
[
https://issues.apache.org/jira/browse/OOZIE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356995#comment-16356995
]
Peter Cseh edited comment on OOZIE-3173 at 2/8/18 2:25 PM:
---
I don't like the amount of flaky tests we have - again - in our pre-commit hook.
+1, thanks for the fix!
was (Author: gezapeti):
I don't like the amount of flaky tests we have - again - in our pre-commit hook.
> Coordinator job with frequency using cron syntax creates only one action in
> catchup mode
>
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time
> lies also in the past), would create only one action, independent of
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now,
> endTime), startTime + frequency * throttle)}}.
> Some examples, {{frequency="0 * * * *"}}:
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{1}} -> one action should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{3}} -> three actions should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{15}} -> ten actions should be created
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3172) Upgrade non-transitive Jackson dependencies from org.codehaus.jackson to com.fasterxml.jackson
[
https://issues.apache.org/jira/browse/OOZIE-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356996#comment-16356996
]
Peter Cseh commented on OOZIE-3172:
---
I'll take a look at dependencies, but in theory the server's version of jackson
should not affect the version of jackson shipped in the sharelibs.
> Upgrade non-transitive Jackson dependencies from org.codehaus.jackson to
> com.fasterxml.jackson
> --
>
> Key: OOZIE-3172
> URL: https://issues.apache.org/jira/browse/OOZIE-3172
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3172.001.patch, OOZIE-3172.002.patch
>
>
> Jackson 1.9.3 is way too old, and has several security vulnerabilities as
> well. Jackson 2.9.2 covers most of these.
> Let's switch from {{org.codehaus.jackson}} to {{com.fasterxml.jackson}} in
> Oozie's direct (non-transitive) dependencies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3163) Improve documentation rendering: use fluido skin and better config
[ https://issues.apache.org/jira/browse/OOZIE-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357001#comment-16357001 ] Peter Cseh commented on OOZIE-3163: --- [~rkanter], is it ok to use the new skin for 4.3.1 without creating a new RC? > Improve documentation rendering: use fluido skin and better config > -- > > Key: OOZIE-3163 > URL: https://issues.apache.org/jira/browse/OOZIE-3163 > Project: Oozie > Issue Type: Task > Components: docs >Affects Versions: 4.3.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 5.0.0 > > Attachments: 34.patch, oozie-docs-coordinator-fs-fluido.png, > oozie-docs-coordinator-fs-old.png, oozie-docs-index-fluido.png, > oozie-docs-index-old.png > > > Current output is really ugly: as Maven maintainer, I can't let Oozie with > such awful result :) > Even with old maven-site-plugin 2.0-beta-6 (we'll see later how to upgrade), > using Fluido skin would improve output a lot > Pull Request coming -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3121) bump all maven plugins to latest versions
[ https://issues.apache.org/jira/browse/OOZIE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357046#comment-16357046 ] Peter Cseh commented on OOZIE-3121: --- +1, test passes locally. The warnings are related to the new versions of the plugins, we'll burn them down eventually > bump all maven plugins to latest versions > - > > Key: OOZIE-3121 > URL: https://issues.apache.org/jira/browse/OOZIE-3121 > Project: Oozie > Issue Type: Improvement >Affects Versions: 4.3.0 >Reporter: Artem Ervits >Assignee: Artem Ervits >Priority: Major > Fix For: 5.0.0 > > Attachments: OOZIE-3121-02.patch, OOZIE-3121.patch > > > bump all maven plugins to latest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3109) Escape log-streaming's HTML-specific characters
[
https://issues.apache.org/jira/browse/OOZIE-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357096#comment-16357096
]
Hadoop QA commented on OOZIE-3109:
--
Testing JIRA OOZIE-3109
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 1 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {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/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
. {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 [client].
{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: 2089
.Tests failed: 17
.Tests errors: 12
.The patch failed the following testcases:
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
.Tests failing with errors:
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLADurationMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectio
Failed: OOZIE-3109 PreCommit Build #384
Jira: https://issues.apache.org/jira/browse/OOZIE-3109
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/384/
###
## LAST 100 LINES OF THE CONSOLE
###
[...truncated 1.61 MB...]
-1 the patch does not add/modify any testcase
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
+1 There are no new bugs found in [examples].
+1 There are no new bugs found in [core].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/pig].
+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/hcatalog].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [webapp].
+1 There are no new bugs found in [tools].
+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 [client].
+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: 2089
Tests failed: 17
Tests errors: 12
The patch failed the following testcases:
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
Tests failing with errors:
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLADurationMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestPurgeXCommand#testPurgeCoordWithWFChild2MoreThanLimit
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch
-1 Overall result, please check the reported -1(s)
There is at least one warning, please check
The full output of the test-patch run is available at
https://builds.apache.org/job/PreCommit-OOZIE-Build/384/
Adding comment to JIRA
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0100 55430 0 100 5543 0 9256 --:--:-- --:--:-- --:--:--
9253{"self":"https://issues.apache.org/jira/rest/api/2/issue/13116394/comment/16357096","id":"16357096","author":{"self":"https://issues.apache.org/jira/r
[jira] [Commented] (OOZIE-3061) Kill only those child jobs which are not already killed
[ https://issues.apache.org/jira/browse/OOZIE-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357099#comment-16357099 ] Peter Cseh commented on OOZIE-3061: --- Yeah, YarnClient could be more clever about this. Can you upload a cumulative patch that contains changes to both classes in question? Also, instead of checking against KILLED status I think we should only kill an application if the yarnClient.getFinalApplicationStatus() is UNDEFINED, meaning the application is still running. There is no gain in killing already succeeded/failed applications. > 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 >Affects Versions: 4.3.0 >Reporter: Satish Subhashrao Saley >Assignee: Mate Juhasz >Priority: Trivial > Labels: newbie, newbiee > Fix For: 5.0.0 > > Attachments: OOZIE-3061-001.patch, OOZIE-3061-002.patch, > OOZIE-3061-003.patch > > > 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 (v7.6.3#76005)
[jira] [Commented] (OOZIE-3175) PurgeService should detect and delete orphaned jobs/actions
[
https://issues.apache.org/jira/browse/OOZIE-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357179#comment-16357179
]
Attila Sasvari commented on OOZIE-3175:
---
An example SQL query to detect orphan workflow actions:
{{SELECT a.id, a.wf_id FROM WF_ACTIONS a WHERE NOT EXISTS (SELECT 1 FROM
WF_JOBS j WHERE j.id=a.wf_id);}}
> PurgeService should detect and delete orphaned jobs/actions
>
>
> Key: OOZIE-3175
> URL: https://issues.apache.org/jira/browse/OOZIE-3175
> Project: Oozie
> Issue Type: Improvement
> Components: core
>Affects Versions: trunk
>Reporter: Attila Sasvari
>Priority: Major
>
> Improvement idea: the purge service could look for orphaned jobs/actions and
> delete those. It would help the cases where the user went in and only
> partially removed things.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1
[
https://issues.apache.org/jira/browse/OOZIE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357184#comment-16357184
]
Peter Cseh commented on OOZIE-3120:
---
Thanks for picking this up!
I don't know much about the assembly-plugin and don't have the time right no to
dig into it. It certainly looks like we're misusing something in the current
build so it'd be nice to clean things up abit.
> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
> Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [ 0.972
> s]
> [INFO] Apache Oozie Client SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server SKIPPED
> [INFO] Apache Oozie Distro SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on
> project oozie-main: No formats specified in the execution parameters or the
> assembly descriptor. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> ERROR, Oozie distro creation failed
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3163) Improve documentation rendering: use fluido skin and better config
[ https://issues.apache.org/jira/browse/OOZIE-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357250#comment-16357250 ] Robert Kanter commented on OOZIE-3163: -- Hmmm, it would be okay with me, but I think technically we would need a new RC because of the tagging, md5, etc. Let's leave the RC as-is (so the release will have the old docs), but we can put the new skin on the 4.3.1 docs on the Oozie website. I imagine most users look at the docs there anyway, rather than on the copy in the Oozie Server. > Improve documentation rendering: use fluido skin and better config > -- > > Key: OOZIE-3163 > URL: https://issues.apache.org/jira/browse/OOZIE-3163 > Project: Oozie > Issue Type: Task > Components: docs >Affects Versions: 4.3.0 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: 5.0.0 > > Attachments: 34.patch, oozie-docs-coordinator-fs-fluido.png, > oozie-docs-coordinator-fs-old.png, oozie-docs-index-fluido.png, > oozie-docs-index-old.png > > > Current output is really ugly: as Maven maintainer, I can't let Oozie with > such awful result :) > Even with old maven-site-plugin 2.0-beta-6 (we'll see later how to upgrade), > using Fluido skin would improve output a lot > Pull Request coming -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (111 issues) Subscriber: ooziedaily Key Summary OOZIE-3129 Fix test TestConfigurationService.testOozieConfig https://issues-test.apache.org/jira/browse/OOZIE-3129 OOZIE-3127 Remove redundant check for user https://issues-test.apache.org/jira/browse/OOZIE-3127 OOZIE-3126 Add option to allow list of users to access system config https://issues-test.apache.org/jira/browse/OOZIE-3126 OOZIE-3121 bump all maven plugins to latest versions https://issues-test.apache.org/jira/browse/OOZIE-3121 OOZIE-3118 fix for error: self-closing element not allowed https://issues-test.apache.org/jira/browse/OOZIE-3118 OOZIE-3117 fix for warning: no @throws for https://issues-test.apache.org/jira/browse/OOZIE-3117 OOZIE-3116 fix for warning: no description for @throws https://issues-test.apache.org/jira/browse/OOZIE-3116 OOZIE-3115 fix for javadoc warning: empty tag https://issues-test.apache.org/jira/browse/OOZIE-3115 OOZIE-3113 Retry for ZK lock release https://issues-test.apache.org/jira/browse/OOZIE-3113 OOZIE-3112 SparkConfigrationService overwrites properties provided via --properties-file option in SparkAction https://issues-test.apache.org/jira/browse/OOZIE-3112 OOZIE-3105 testJMXInstrumentation from the org.apache.oozie.util.TestMetricsInstrumentation class is flaky https://issues-test.apache.org/jira/browse/OOZIE-3105 OOZIE-3094 fix for grammar mistake https://issues-test.apache.org/jira/browse/OOZIE-3094 OOZIE-3091 Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper" https://issues-test.apache.org/jira/browse/OOZIE-3091 OOZIE-3083 Make improved version Info backward compatible https://issues-test.apache.org/jira/browse/OOZIE-3083 OOZIE-3071 Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0 https://issues-test.apache.org/jira/browse/OOZIE-3071 OOZIE-3063 Sanitizing variables that are part of openjpa.ConnectionProperties https://issues-test.apache.org/jira/browse/OOZIE-3063 OOZIE-3062 Set HADOOP_CONF_DIR for spark action https://issues-test.apache.org/jira/browse/OOZIE-3062 OOZIE-3002 address findbugs errors in client lib https://issues-test.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-test.apache.org/jira/browse/OOZIE-2975 OOZIE-2973 Make sure Oozie works with Hadoop 3 https://issues-test.apache.org/jira/browse/OOZIE-2973 OOZIE-2969 Drop support for Java 1.7 https://issues-test.apache.org/jira/browse/OOZIE-2969 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-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
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (104 issues) Subscriber: ooziedaily Key Summary OOZIE-3173 Coordinator job with frequency using cron syntax creates only one action in catchup mode https://issues.apache.org/jira/browse/OOZIE-3173 OOZIE-3172 Upgrade non-transitive Jackson dependencies from org.codehaus.jackson to com.fasterxml.jackson https://issues.apache.org/jira/browse/OOZIE-3172 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 OOZIE-3134 Potential inconsistency between the in-memory SLA map and the Oozie database https://issues.apache.org/jira/browse/OOZIE-3134 OOZIE-3109 Escape log-streaming's HTML-specific characters https://issues.apache.org/jira/browse/OOZIE-3109 OOZIE-3105 testJMXInstrumentation from the org.apache.oozie.util.TestMetricsInstrumentation class is flaky https://issues.apache.org/jira/browse/OOZIE-3105 OOZIE-3094 fix for grammar mistake https://issues.apache.org/jira/browse/OOZIE-3094 OOZIE-3091 Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper" https://issues.apache.org/jira/browse/OOZIE-3091 OOZIE-3071 Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0 https://issues.apache.org/jira/browse/OOZIE-3071 OOZIE-3063 Sanitizing variables that are part of openjpa.ConnectionProperties https://issues.apache.org/jira/browse/OOZIE-3063 OOZIE-3062 Set HADOOP_CONF_DIR for spark action https://issues.apache.org/jira/browse/OOZIE-3062 OOZIE-3061 Kill only those child jobs which are not already killed https://issues.apache.org/jira/browse/OOZIE-3061 OOZIE-3002 address findbugs errors in client lib https://issues.apache.org/jira/browse/OOZIE-3002 OOZIE-2975 code clean up in pig sharelib, replace Exception with more explicit, add try with resources, StringBuilder instead of StringBuffer https://issues.apache.org/jira/browse/OOZIE-2975 OOZIE-2957 Documentation states that starting a coordinator is possible https://issues.apache.org/jira/browse/OOZIE-2957 OOZIE-2956 Fix Findbugs warnings related to reliance on default encoding in oozie-core https://issues.apache.org/jira/browse/OOZIE-2956 OOZIE-2955 Fix Findbugs warnings related to reliance on default encoding in oozie-client https://issues.apache.org/jira/browse/OOZIE-2955 OOZIE-2954 Fix Checkstyle issues in oozie-client https://issues.apache.org/jira/browse/OOZIE-2954 OOZIE-2953 Fix Checkstyle issues in oozie-tools https://issues.apache.org/jira/browse/OOZIE-2953 OOZIE-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2949 Escape quotes whitespaces in Sqoop field https://issues.apache.org/jira/browse/OOZIE-2949 OOZIE-2942 Fix Findbugs warnings in oozie-examples https://issues.apache.org/jira/browse/OOZIE-2942 OOZIE-2937 Remove redundant groupId from the child pom's https://issues.apache.org/jira/browse/OOZIE-2937 OOZIE-2934 Fix "Exceptional return value of java.io.File.mkdirs() ignored" Findbugs error in oozie-sharelib-spark https://issues.apache.org/jira/browse/OOZIE-2934 OOZIE-2927 Append new line character for Hive2 query using query tag https://issues.apache.org/jira/browse/OOZIE-2927 OOZIE-2914 Consolidate Trim https://issues.apache.org/jira/browse/OOZIE-2914 OOZIE-2883 OOZIE throw the error "Missing [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups] property" https://issues.apache.org/jira/browse/OOZIE-2883 OOZIE-2877 Oozie Git Action https://issues.apache.org/jira/browse/OOZIE-2877 OOZIE-2867 Timezone handling for Coordinators: emphasize "Continent/City" format https://issues.apache.org/jira/browse/OOZIE-2867 OOZIE-2834 ParameterVerifier logging non-useful warning for workflow definition https://issues.apache.org/jira/browse/OOZIE-2834 OOZIE-2833 when using uber mode the regex pattern used in the extractHeapSizeMB method does not allow heap sizes specified in bytes. https://issues.apache.org/jira/browse/OOZIE-2833 OOZIE-2829 Improve sharelib upload to accept multiple source folders 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-2814 OYA: Update example workflows to newest schemas https://issues.apache.org/jira/browse/OOZIE-2814 OOZIE-2812 SparkConfigurationService should support loading configurations from multiple Spark versions https://issues.apache.org/jira/browse
