[jira] [Commented] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-3182:
--

PreCommit-OOZIE-Build started


> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-004.patch, 
> error-log.txt, log-OOZIE-3182-004.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: OOZIE-3182-004.patch

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-004.patch, 
> error-log.txt, log-OOZIE-3182-004.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: error-log.txt

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, error-log.txt, 
> log-OOZIE-3182-004.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: (was: log-OOZIE-3182-003.txt)

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, error-log.txt, 
> log-OOZIE-3182-004.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: (was: error-log.txt)

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, error-log.txt, 
> log-OOZIE-3182-004.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: log-OOZIE-3182-004.txt

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, error-log.txt, 
> log-OOZIE-3182-004.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] Subscription: Oozie Patch Available

2018-02-14 Thread jira
Issue Subscription
Filter: Oozie Patch Available (105 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3182  Oozie components fail with checkstyle errors
https://issues.apache.org/jira/browse/OOZIE-3182
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3176  Oozie-core fails with checkstyle errors.
https://issues.apache.org/jira/browse/OOZIE-3176
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

[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: (was: OOZIE-3182-003.patch)

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, error-log.txt, 
> log-OOZIE-3182-003.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: (was: OOZIE-3182-002.patch)

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, error-log.txt, 
> log-OOZIE-3182-003.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


Apache EU Roadshow CFP Closing Soon (23 February)

2018-02-14 Thread Sharan F

Hello Everyone

This is an initial reminder to let you all know that we are holding an 
Apache EU Roadshow co-located with FOSS Backstage in Berlin on 13^th and 
14^th June 2018. https://s.apache.org/tCHx


The Call for Proposals (CFP) for the Apache EU Roadshow is currently 
open and will close at the end of next week, so if you have been 
delaying making a submission because the closing date seemed a long way 
off, then it's time to start getting your proposals submitted.


So what are we looking for?
We will have 2 Apache Devrooms available during the 2 day Roadshow so 
are looking for projects including incubating ones, to submit 
presentations, panel discussions, BoFs, or workshop proposals. The main 
focus of the Roadshow will be IoT, Cloud, Httpd and Tomcat so if your 
project is involved in or around any of these technologies at Apache 
then we are very interested in hearing from you.


Community and collaboration is important at Apache so if your project is 
interested in organising a project sprint, meetup or hackathon during 
the Roadshow, then please submit it inthe CFP as we do have some space 
available to allocate for these.


If you are wanting to submit a talk on open source community related 
topics such as the Apache Way, governance or legal aspects then please 
submit these to the CFP for FOSS Backstage.


Tickets for the Apache EU Roadshow are included as part of the 
registration for FOSS Backstage, so to attend the Roadshow you will need 
to register for FOSS Backstage. Early Bird tickets are still available 
until the 21^st February 2018.


Please see below for important URLs to remember:

-  To submit a CFP for the Apache EU Roadshow 
:http://apachecon.com/euroadshow18/ 


-  To submit a CFP for FOSS Backstage : 
https://foss-backstage.de/call-papers


-  To register to attend the Apache EU Roadshow and/or FOSS Backstage : 
https://foss-backstage.de/tickets


For further updates and information about the Apache EU Roadshowplease 
check http://apachecon.com/euroadshow18/


Thanks
Sharan Foga, VP Apache Community Development


Re: [ANNOUNCE] Apache Oozie 4.3.1 released

2018-02-14 Thread sebb
What is the project about? Why should I be interested in it?
[rhetorical questions]

The Announce emails are sent to people not on the developer or user lists.
Most will have no idea what the project is about.

So the e-mails should contain at least brief details of what the
product does, and some info on why the new release might be of
interest to them.

Readers should not have to click the link to find out the basic information
(although of course it is useful to have such links for further detail).

Also it's not actually all that obvious how to find the download page for 4.3.1

Please can you add that information to future announce mails?

Thanks.


On 14 February 2018 at 12:56, Gézapeti Cseh  wrote:
> Hello Oozie community,
>
> The Apache Oozie team is pleased to announce the release of Oozie 4.3.1.
> Oozie 4.3.1 includes bug fixes and minor improvements.
>
> The details of the release and download location can be found at
> http://oozie.apache.org

It's not that easy to find the release notes or even the download page.

> Thanks to all developers, QA's, users, and committers for making this
> release happen.
>
> gp


[jira] [Comment Edited] (OOZIE-2814) OYA: Update example workflows to newest schemas

2018-02-14 Thread Peter Cseh (JIRA)

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

Peter Cseh edited comment on OOZIE-2814 at 2/14/18 2:51 PM:


The patch looks good overall.
Have you tried running the old examples after the code changes to check on 
backwards compatibility?


was (Author: gezapeti):
The patch looks good overall.
Have you tried running the old examples after the code changes to check on 
backwards 
compatibility?https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16363929#

> OYA: Update example workflows to newest schemas
> ---
>
> Key: OOZIE-2814
> URL: https://issues.apache.org/jira/browse/OOZIE-2814
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
>Priority: Blocker
> Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, 
> OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, 
> OOZIE-2814-05.patch, OOZIE-2814-06.patch
>
>
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric.  Most, if not all, examples currently use pretty old versions 
> of the schemas.  We should take this opportunity to update the examples to 
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> It may make sense to keep the older schemas too, to show that older workflows 
> still work.  We have some examples where we have two workflow XML files that 
> do the same thing in different ways.



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


[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas

2018-02-14 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-2814:
---

The patch looks good overall.
Have you tried running the old examples after the code changes to check on 
backwards 
compatibility?https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16363929#

> OYA: Update example workflows to newest schemas
> ---
>
> Key: OOZIE-2814
> URL: https://issues.apache.org/jira/browse/OOZIE-2814
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
>Priority: Blocker
> Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, 
> OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, 
> OOZIE-2814-05.patch, OOZIE-2814-06.patch
>
>
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric.  Most, if not all, examples currently use pretty old versions 
> of the schemas.  We should take this opportunity to update the examples to 
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> It may make sense to keep the older schemas too, to show that older workflows 
> still work.  We have some examples where we have two workflow XML files that 
> do the same thing in different ways.



--
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

2018-02-14 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-3172:
-

Thanks [~gezapeti]! Committed to {{master}}.

> 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, 
> OOZIE-3172.003.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-3183) Better logging for SshActionExecutor and extended HA capability when calling to remote host

2018-02-14 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-3183:
---

+1 
Improving logging is always a good idea. Also Oracle's documentation of 
waitFor() states that it uses exitCode() by default, but it should be improved 
by the native implementations.

> Better logging for SshActionExecutor and extended HA capability when calling 
> to remote host
> ---
>
> Key: OOZIE-3183
> URL: https://issues.apache.org/jira/browse/OOZIE-3183
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3183.001.patch
>
>
> In some High Availability environments, when an SSH action's 
> {{SshActionExecutor#start()}} runs on another node than 
> {{SshActionExecutor#check()}}, it can happen that due to network bandwidth 
> reasons calling {{Process#exitValue()}} is not enough - but calling 
> {{Process#waitFor()}} is better.
> Also, for better error root cause analysis, enhance logging along 
> {{SshActionExecutor}} for the critical parts.



--
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

2018-02-14 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-3172:
---

I don't see the servers' jackson versions messing with the sharelibs. +1

> 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, 
> OOZIE-3172.003.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-3183) Better logging for SshActionExecutor and extended HA capability when calling to remote host

2018-02-14 Thread Andras Piros (JIRA)

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

Andras Piros commented on OOZIE-3183:
-

Failing test {{TestHiveActionExecutor#testHiveAction()}} is unrelated. FindBugs 
warnings come from untouched parts. [~gezapeti] can you please review?

> Better logging for SshActionExecutor and extended HA capability when calling 
> to remote host
> ---
>
> Key: OOZIE-3183
> URL: https://issues.apache.org/jira/browse/OOZIE-3183
> Project: Oozie
>  Issue Type: Improvement
>  Components: action
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3183.001.patch
>
>
> In some High Availability environments, when an SSH action's 
> {{SshActionExecutor#start()}} runs on another node than 
> {{SshActionExecutor#check()}}, it can happen that due to network bandwidth 
> reasons calling {{Process#exitValue()}} is not enough - but calling 
> {{Process#waitFor()}} is better.
> Also, for better error root cause analysis, enhance logging along 
> {{SshActionExecutor}} for the critical parts.



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


[jira] [Commented] (OOZIE-3163) Improve documentation rendering: use fluido skin and better config

2018-02-14 Thread Peter Cseh (JIRA)

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

Peter Cseh commented on OOZIE-3163:
---

The 4.3.1 documentation looks way nicer :)
https://oozie.apache.org/docs/4.3.1/

Thanks [~hboutemy]!

> 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-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-3182:
--


Testing JIRA OOZIE-3182

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch




> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt, log-OOZIE-3182-003.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


Failed: OOZIE-3182 PreCommit Build #400

2018-02-14 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-3182
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/400/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 752.87 KB...]
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/main/resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/main/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
oozie-zookeeper-security-tests ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ 
oozie-zookeeper-security-tests ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
oozie-zookeeper-security-tests ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target/test-classes
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Some input files use or override a deprecated API.
[INFO] 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/test/java/org/apache/oozie/util/TestZKUtilsWithSecurity.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.5:check (default-cli) > :findbugs @ 
oozie-zookeeper-security-tests >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:findbugs (findbugs) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.5:check (default-cli) < :findbugs @ 
oozie-zookeeper-security-tests <<<
[INFO] 
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.5:check (default-cli) @ 
oozie-zookeeper-security-tests ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Oozie Main .. SUCCESS [  1.703 s]
[INFO] Apache Oozie Client  SUCCESS [ 17.231 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 12.663 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  6.423 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  4.756 s]
[INFO] Apache Oozie Core .. SUCCESS [01:14 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  7.406 s]
[INFO] Apache Oozie Share Lib Pig . SUCCESS [  7.305 s]
[INFO] Apache Oozie Share Lib Hive  SUCCESS [  7.976 s]
[INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  9.209 s]
[INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  5.411 s]
[INFO] Apache Oozie Examples .. SUCCESS [  8.315 s]
[INFO] Apache Oozie Share Lib Spark ... SUCCESS [  9.452 s]
[INFO] Apache Oozie Share Lib . SUCCESS [  0.024 s]
[INFO] Apache Oozie Docs .. SUCCESS [  3.054 s]
[INFO] Apache Oozie WebApp  SUCCESS [  7.618 s]
[INFO] Apache Oozie Tools . SUCCESS [ 12.361 s]
[INFO] Apache Oozie MiniOozie . SUCCESS [  1.611 s]
[INFO] Apache Oozie Server  SUCCESS [ 10.066 s]
[INFO] Apache Oozie Distro  SUCCESS [  2.138 s]
[INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [  3.572 s]
[INFO] 
[INFO] BUILD SUCCESS

[jira] [Commented] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-3182:
--

PreCommit-OOZIE-Build started


> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt, log-OOZIE-3182-003.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas

2018-02-14 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2814:
--


Testing JIRA OOZIE-2814

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 2 line(s) longer than 132 
characters
.{color:green}+1{color} the patch 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 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:orange}0{color} There are [1] new bugs found in total that would be nice 
to have fixed.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:orange}0{color} There are [1] new bugs found in [core] that would be 
nice to have fixed.
. You can find the FindBugs diff here: core/findbugs-new.html
. {color:green}+1{color} There are no new bugs found in [tools].
. {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/distcp].
. {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/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/oozie].
. {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/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {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 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: 2097
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor)

.Tests failing with errors:


.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandDate
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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/399/



> OYA: Update example workflows to newest schemas
> ---
>
> Key: OOZIE-2814
> URL: https://issues.apache.org/jira/browse/OOZIE-2814
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
>Priority: Blocker
> Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, 
> OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, 
> OOZIE-2814-05.patch, OOZIE-2814-06.patch
>
>
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric.  Most, if not all, examples currently use pretty old versions 
> of the schemas.  We should take this opportunity to update the examples to 
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> It may make sense to keep the older schemas too, to show that older workflows 
> still work.  We have some examples where we have two workflow XML files that 
> do the same thing in different ways.



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


Failed: OOZIE-2814 PreCommit Build #399

2018-02-14 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/OOZIE-2814
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/399/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.72 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[WARN] There are [1] new bugs found in total that would be nice to have fixed.
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2380 bytes
[TRACE] Full summary file size is 1444 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-2814

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 2 line(s) longer than 132 characters
+1 the patch adds/modifies 2 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 100 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 [1] new bugs found in total that would be nice to have fixed.
 +1 There are no new bugs found in [webapp].
 0 There are [1] 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 [tools].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/distcp].
 +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/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [server].
+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: 2097
Tests failed: 1
Tests errors: 0

The patch failed the following testcases:

testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor)

Tests failing with errors:


Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandDate
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/399/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  35280 0  100  3528  0   4102 --:--:-- --:--:-- --:--:--  
4102{"self":"https://issues.apache.org/jira/rest/api/2/issue/13049362/comment/16363929","id":"16363929","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small=hadoopqa=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall=hadoopqa=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium=hadoopqa=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-2814\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:red}-1 
RAW_PATCH_ANALYSIS{color}\n.{color:green}+1{color} the patch does not 
introduce any @author tags\n.{color:green}+1{color} the patch does not 

Re: Review Request 65636: OOZIE-3179 - Adding a configurable config-default.xml location to a workflow

2018-02-14 Thread Jason Phelps via Review Board

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

(Updated Feb. 14, 2018, 1:03 p.m.)


Review request for oozie.


Changes
---

Had the scenerio done, but forgot the assertion test. Added it in


Repository: oozie-git


Description
---

Added another client property: `oozie.default.configuration.path` which allows 
for a comma seperated list of HDFS XML property files to be applied to the job. 
This is useful if multiple workflows have shared properties (i.e. database 
names, table names for Sqoop or Hive, spark arguments, etc). This is similar to 
the `oozie.libpath` property which allows user's to define common paths 
workflows to load jars.


Diffs (updated)
-

  client/src/main/java/org/apache/oozie/client/OozieClient.java e581e50 
  core/src/main/java/org/apache/oozie/command/wf/SubmitXCommand.java a4d3e2f 
  core/src/test/java/org/apache/oozie/command/wf/TestSubmitXCommand.java 
e71a662 


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

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


Testing
---


Thanks,

Jason Phelps



[ANNOUNCE] Apache Oozie 4.3.1 released

2018-02-14 Thread Gézapeti Cseh
Hello Oozie community,

The Apache Oozie team is pleased to announce the release of Oozie 4.3.1.
Oozie 4.3.1 includes bug fixes and minor improvements.

The details of the release and download location can be found at
http://oozie.apache.org

Thanks to all developers, QA's, users, and committers for making this
release happen.

gp


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: log-OOZIE-3182-003.txt

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt, log-OOZIE-3182-003.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: error-log.txt

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: (was: log-OOZIE-3182-002.txt)

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: (was: error-log.txt)

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Commented] (OOZIE-2814) OYA: Update example workflows to newest schemas

2018-02-14 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-2814:
--

PreCommit-OOZIE-Build started


> OYA: Update example workflows to newest schemas
> ---
>
> Key: OOZIE-2814
> URL: https://issues.apache.org/jira/browse/OOZIE-2814
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
>Priority: Blocker
> Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, 
> OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, 
> OOZIE-2814-05.patch, OOZIE-2814-06.patch
>
>
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric.  Most, if not all, examples currently use pretty old versions 
> of the schemas.  We should take this opportunity to update the examples to 
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> It may make sense to keep the older schemas too, to show that older workflows 
> still work.  We have some examples where we have two workflow XML files that 
> do the same thing in different ways.



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


[jira] [Updated] (OOZIE-2814) OYA: Update example workflows to newest schemas

2018-02-14 Thread Attila Sasvari (JIRA)

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

Attila Sasvari updated OOZIE-2814:
--
Attachment: OOZIE-2814-06.patch

> OYA: Update example workflows to newest schemas
> ---
>
> Key: OOZIE-2814
> URL: https://issues.apache.org/jira/browse/OOZIE-2814
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
>Priority: Blocker
> Attachments: OOZIE-2814-00.patch, OOZIE-2814-01.patch, 
> OOZIE-2814-02.patch, OOZIE-2814-03.patch, OOZIE-2814-04.patch, 
> OOZIE-2814-05.patch, OOZIE-2814-06.patch
>
>
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric.  Most, if not all, examples currently use pretty old versions 
> of the schemas.  We should take this opportunity to update the examples to 
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> It may make sense to keep the older schemas too, to show that older workflows 
> still work.  We have some examples where we have two workflow XML files that 
> do the same thing in different ways.



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


Re: Review Request 65606: OOZIE-2814 OYA: Update example workflows to newest schemas

2018-02-14 Thread Attila Sasvari via Review Board

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

(Updated Feb. 14, 2018, 11:13 a.m.)


Review request for oozie.


Changes
---

- addressing review comments on changes in GlobalSectionData


Repository: oozie-git


Description
---

OOZIE-2687 will add in a whole set of newer schemas that are more Yarn-centric. 
Most, if not all, examples currently use pretty old versions of the schemas. We 
should take this opportunity to update the examples to the newest schemas added 
by OOZIE-2687, which should help demonstrate them.

It may make sense to keep the older schemas too, to show that older workflows 
still work. We have some examples where we have two workflow XML files that do 
the same thing in different ways.


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
bc0f4050bb3788988d3a5352a15220fbc4fa219d 
  core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
c236dafa5965403c33e1a400509e7c374fe2637c 
  core/src/main/resources/oozie-default.xml 
e53b17b3cf201b4cf7bc5371503e66327eae2126 
  core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
1cc569d8d7a0e61905ad6c4e940cefb00da1343d 
  
core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
 2cdbde4d2fc86a07b35beadc56012c438baf8d54 
  examples/src/main/apps/aggregator/coordinator-with-offset.xml 
4c351677f4afc6e85f807106d426bb2f922a28b1 
  examples/src/main/apps/aggregator/coordinator.xml 
948edc1adbe09dfb6f7bffb5eebc82f3670658cc 
  examples/src/main/apps/aggregator/job-with-offset.properties 
9a28ae13e50c40f70db4b0f583a63eb42f97388d 
  examples/src/main/apps/aggregator/job.properties 
aaf4edf7b9d030b5044610698b27a564b008f77b 
  examples/src/main/apps/aggregator/workflow.xml 
4a801090e31acba23ea49da1c59a8ce4b951c654 
  examples/src/main/apps/bundle/job.properties 
c06edeb3f42e2eba3367b9486982dabb4caf6436 
  examples/src/main/apps/coord-input-logic/job.properties 
2cd137b94999c7e1f68bb54928f1c3ce2838d59d 
  examples/src/main/apps/coord-input-logic/workflow.xml 
80d31457eff6e78710ad1fb4d4f1b372c0d1e43c 
  examples/src/main/apps/cron-schedule/coordinator.xml 
48a7de76245e02397b9736a95fa0132504067f9a 
  examples/src/main/apps/cron-schedule/job.properties 
5b5eb43ca2bf9d8cd1b263ca3b94a552b562a20d 
  examples/src/main/apps/cron-schedule/workflow.xml 
b53922c8f40e691cb637b91cb182172794296a04 
  examples/src/main/apps/cron/coordinator.xml 
744d14e870b59d0b89f65a78fea63fffa3ff4b8e 
  examples/src/main/apps/cron/job.properties 
42875fd5a5ce393cd11717bcc55fc1bb91e0fcd3 
  examples/src/main/apps/cron/workflow.xml 
63dff976f9e35a26b0ad09078778748d3d02bc3b 
  examples/src/main/apps/custom-main/job.properties 
b897512a1c6246308ca17b019ce400f3ec06cd7b 
  examples/src/main/apps/custom-main/workflow.xml 
828dfaa0594aac0539c4e08ae8e37cb89d17eb54 
  examples/src/main/apps/datelist-java-main/job.properties 
e8356e3a4a2e1ae41e09f5ea124fb5360bd6e8b6 
  examples/src/main/apps/datelist-java-main/workflow.xml 
b59a12ebd1fc21c9e26f6a5b0348eb9c76375c03 
  examples/src/main/apps/demo/job.properties 
d70d3208df77e0b612005196907cecd97d7c5d21 
  examples/src/main/apps/demo/job.windows.properties 
ea948b20009685e1286053549fc1974669819682 
  examples/src/main/apps/demo/workflow.xml 
0ceca507adc68c0674b794420c9eb733cb320879 
  examples/src/main/apps/distcp/job.properties 
ec9422caddcdecfa6ee9a58868cf68d7457ad4db 
  examples/src/main/apps/distcp/workflow.xml 
6deecb377901613a5bb28fc18bf5beff2d30f252 
  examples/src/main/apps/hadoop-el/job.properties 
1d13c27056ac58ad359b5298f12ec046bb4cc61d 
  examples/src/main/apps/hadoop-el/workflow.xml 
d4094d44136a7de2f85f5c9be042d5aab24b90be 
  examples/src/main/apps/hcatalog/job.properties 
e0aa18c264a2fa92b6c3d501d18fa39733d863ff 
  examples/src/main/apps/hcatalog/job.properties.security 
2fbcc6ee9e5d94d3bba63810e6e788607747940b 
  examples/src/main/apps/hcatalog/workflow.xml 
d6593df1b9104179d79262d663135d73de8b55ec 
  examples/src/main/apps/hcatalog/workflow.xml.security 
aa3522ae4d5b6cb178f80c2e72e45c4c3de9aab5 
  examples/src/main/apps/hive/job.properties 
dbc7ad2a0b135b8c9f0b6e575086ee8260072756 
  examples/src/main/apps/hive/workflow.xml 
449d62d35f2e69d01d9e59f35a0cc9ad057342d2 
  examples/src/main/apps/hive/workflow.xml.security 
35321319dcbb0576c5870952e6e805209b8dc240 
  examples/src/main/apps/hive2/job.properties 
2640402472d3b2120941834e4653d363fb49914b 
  examples/src/main/apps/hive2/job.properties.security 
ac980cd3cc37e3b3b359c2e3fefe180cf88b56bc 
  examples/src/main/apps/hive2/workflow.xml 
5f1ccc4fd0791f850c0942452d637048acce13d1 
  examples/src/main/apps/hive2/workflow.xml.security 
6f7304def80317429e58cecddc63fe4c1d3edaa6 
  examples/src/main/apps/java-main/job.properties 
519c53e7313b6a5b54ab54cb2dd31f123819a0f9 
  

Re: Review Request 65606: OOZIE-2814 OYA: Update example workflows to newest schemas

2018-02-14 Thread Attila Sasvari via Review Board


> On Feb. 14, 2018, 10:50 a.m., Peter Bacsko wrote:
> > core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java
> > Lines 2349 (patched)
> > 
> >
> > Can't we accidentally skip the PREP phase? If the WF quickly makes a 
> > transition to the next state, then the test will fail.

We cannot, look at existing tests.


- Attila


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


On Feb. 12, 2018, 4:19 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65606/
> ---
> 
> (Updated Feb. 12, 2018, 4:19 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric. Most, if not all, examples currently use pretty old versions of 
> the schemas. We should take this opportunity to update the examples to the 
> newest schemas added by OOZIE-2687, which should help demonstrate them.
> 
> It may make sense to keep the older schemas too, to show that older workflows 
> still work. We have some examples where we have two workflow XML files that 
> do the same thing in different ways.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> bc0f4050bb3788988d3a5352a15220fbc4fa219d 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
> c236dafa5965403c33e1a400509e7c374fe2637c 
>   core/src/main/resources/oozie-default.xml 
> e53b17b3cf201b4cf7bc5371503e66327eae2126 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> 1cc569d8d7a0e61905ad6c4e940cefb00da1343d 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  2cdbde4d2fc86a07b35beadc56012c438baf8d54 
>   examples/src/main/apps/aggregator/coordinator-with-offset.xml 
> 4c351677f4afc6e85f807106d426bb2f922a28b1 
>   examples/src/main/apps/aggregator/coordinator.xml 
> 948edc1adbe09dfb6f7bffb5eebc82f3670658cc 
>   examples/src/main/apps/aggregator/job-with-offset.properties 
> 9a28ae13e50c40f70db4b0f583a63eb42f97388d 
>   examples/src/main/apps/aggregator/job.properties 
> aaf4edf7b9d030b5044610698b27a564b008f77b 
>   examples/src/main/apps/aggregator/workflow.xml 
> 4a801090e31acba23ea49da1c59a8ce4b951c654 
>   examples/src/main/apps/bundle/job.properties 
> c06edeb3f42e2eba3367b9486982dabb4caf6436 
>   examples/src/main/apps/coord-input-logic/job.properties 
> 2cd137b94999c7e1f68bb54928f1c3ce2838d59d 
>   examples/src/main/apps/coord-input-logic/workflow.xml 
> 80d31457eff6e78710ad1fb4d4f1b372c0d1e43c 
>   examples/src/main/apps/cron-schedule/coordinator.xml 
> 48a7de76245e02397b9736a95fa0132504067f9a 
>   examples/src/main/apps/cron-schedule/job.properties 
> 5b5eb43ca2bf9d8cd1b263ca3b94a552b562a20d 
>   examples/src/main/apps/cron-schedule/workflow.xml 
> b53922c8f40e691cb637b91cb182172794296a04 
>   examples/src/main/apps/cron/coordinator.xml 
> 744d14e870b59d0b89f65a78fea63fffa3ff4b8e 
>   examples/src/main/apps/cron/job.properties 
> 42875fd5a5ce393cd11717bcc55fc1bb91e0fcd3 
>   examples/src/main/apps/cron/workflow.xml 
> 63dff976f9e35a26b0ad09078778748d3d02bc3b 
>   examples/src/main/apps/custom-main/job.properties 
> b897512a1c6246308ca17b019ce400f3ec06cd7b 
>   examples/src/main/apps/custom-main/workflow.xml 
> 828dfaa0594aac0539c4e08ae8e37cb89d17eb54 
>   examples/src/main/apps/datelist-java-main/job.properties 
> e8356e3a4a2e1ae41e09f5ea124fb5360bd6e8b6 
>   examples/src/main/apps/datelist-java-main/workflow.xml 
> b59a12ebd1fc21c9e26f6a5b0348eb9c76375c03 
>   examples/src/main/apps/demo/job.properties 
> d70d3208df77e0b612005196907cecd97d7c5d21 
>   examples/src/main/apps/demo/job.windows.properties 
> ea948b20009685e1286053549fc1974669819682 
>   examples/src/main/apps/demo/workflow.xml 
> 0ceca507adc68c0674b794420c9eb733cb320879 
>   examples/src/main/apps/distcp/job.properties 
> ec9422caddcdecfa6ee9a58868cf68d7457ad4db 
>   examples/src/main/apps/distcp/workflow.xml 
> 6deecb377901613a5bb28fc18bf5beff2d30f252 
>   examples/src/main/apps/hadoop-el/job.properties 
> 1d13c27056ac58ad359b5298f12ec046bb4cc61d 
>   examples/src/main/apps/hadoop-el/workflow.xml 
> d4094d44136a7de2f85f5c9be042d5aab24b90be 
>   examples/src/main/apps/hcatalog/job.properties 
> e0aa18c264a2fa92b6c3d501d18fa39733d863ff 
>   examples/src/main/apps/hcatalog/job.properties.security 
> 2fbcc6ee9e5d94d3bba63810e6e788607747940b 
>   examples/src/main/apps/hcatalog/workflow.xml 
> d6593df1b9104179d79262d663135d73de8b55ec 
>   

Re: Review Request 65606: OOZIE-2814 OYA: Update example workflows to newest schemas

2018-02-14 Thread Peter Bacsko via Review Board

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




core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java
Lines 394 (patched)


My comment applies to the readFiels() methods too, obviously.



core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java
Lines 2349 (patched)


Can't we accidentally skip the PREP phase? If the WF quickly makes a 
transition to the next state, then the test will fail.


- Peter Bacsko


On febr. 12, 2018, 4:19 du, Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65606/
> ---
> 
> (Updated febr. 12, 2018, 4:19 du)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric. Most, if not all, examples currently use pretty old versions of 
> the schemas. We should take this opportunity to update the examples to the 
> newest schemas added by OOZIE-2687, which should help demonstrate them.
> 
> It may make sense to keep the older schemas too, to show that older workflows 
> still work. We have some examples where we have two workflow XML files that 
> do the same thing in different ways.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> bc0f4050bb3788988d3a5352a15220fbc4fa219d 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
> c236dafa5965403c33e1a400509e7c374fe2637c 
>   core/src/main/resources/oozie-default.xml 
> e53b17b3cf201b4cf7bc5371503e66327eae2126 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> 1cc569d8d7a0e61905ad6c4e940cefb00da1343d 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  2cdbde4d2fc86a07b35beadc56012c438baf8d54 
>   examples/src/main/apps/aggregator/coordinator-with-offset.xml 
> 4c351677f4afc6e85f807106d426bb2f922a28b1 
>   examples/src/main/apps/aggregator/coordinator.xml 
> 948edc1adbe09dfb6f7bffb5eebc82f3670658cc 
>   examples/src/main/apps/aggregator/job-with-offset.properties 
> 9a28ae13e50c40f70db4b0f583a63eb42f97388d 
>   examples/src/main/apps/aggregator/job.properties 
> aaf4edf7b9d030b5044610698b27a564b008f77b 
>   examples/src/main/apps/aggregator/workflow.xml 
> 4a801090e31acba23ea49da1c59a8ce4b951c654 
>   examples/src/main/apps/bundle/job.properties 
> c06edeb3f42e2eba3367b9486982dabb4caf6436 
>   examples/src/main/apps/coord-input-logic/job.properties 
> 2cd137b94999c7e1f68bb54928f1c3ce2838d59d 
>   examples/src/main/apps/coord-input-logic/workflow.xml 
> 80d31457eff6e78710ad1fb4d4f1b372c0d1e43c 
>   examples/src/main/apps/cron-schedule/coordinator.xml 
> 48a7de76245e02397b9736a95fa0132504067f9a 
>   examples/src/main/apps/cron-schedule/job.properties 
> 5b5eb43ca2bf9d8cd1b263ca3b94a552b562a20d 
>   examples/src/main/apps/cron-schedule/workflow.xml 
> b53922c8f40e691cb637b91cb182172794296a04 
>   examples/src/main/apps/cron/coordinator.xml 
> 744d14e870b59d0b89f65a78fea63fffa3ff4b8e 
>   examples/src/main/apps/cron/job.properties 
> 42875fd5a5ce393cd11717bcc55fc1bb91e0fcd3 
>   examples/src/main/apps/cron/workflow.xml 
> 63dff976f9e35a26b0ad09078778748d3d02bc3b 
>   examples/src/main/apps/custom-main/job.properties 
> b897512a1c6246308ca17b019ce400f3ec06cd7b 
>   examples/src/main/apps/custom-main/workflow.xml 
> 828dfaa0594aac0539c4e08ae8e37cb89d17eb54 
>   examples/src/main/apps/datelist-java-main/job.properties 
> e8356e3a4a2e1ae41e09f5ea124fb5360bd6e8b6 
>   examples/src/main/apps/datelist-java-main/workflow.xml 
> b59a12ebd1fc21c9e26f6a5b0348eb9c76375c03 
>   examples/src/main/apps/demo/job.properties 
> d70d3208df77e0b612005196907cecd97d7c5d21 
>   examples/src/main/apps/demo/job.windows.properties 
> ea948b20009685e1286053549fc1974669819682 
>   examples/src/main/apps/demo/workflow.xml 
> 0ceca507adc68c0674b794420c9eb733cb320879 
>   examples/src/main/apps/distcp/job.properties 
> ec9422caddcdecfa6ee9a58868cf68d7457ad4db 
>   examples/src/main/apps/distcp/workflow.xml 
> 6deecb377901613a5bb28fc18bf5beff2d30f252 
>   examples/src/main/apps/hadoop-el/job.properties 
> 1d13c27056ac58ad359b5298f12ec046bb4cc61d 
>   examples/src/main/apps/hadoop-el/workflow.xml 
> d4094d44136a7de2f85f5c9be042d5aab24b90be 
>   examples/src/main/apps/hcatalog/job.properties 
> e0aa18c264a2fa92b6c3d501d18fa39733d863ff 
>   examples/src/main/apps/hcatalog/job.properties.security 
> 2fbcc6ee9e5d94d3bba63810e6e788607747940b 
>   

Re: Review Request 65606: OOZIE-2814 OYA: Update example workflows to newest schemas

2018-02-14 Thread Peter Bacsko via Review Board

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




core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java
Lines 394 (patched)


This class is a Writable. How do we serialize this new boolean? I can't see 
changes in the write() method. If we don't have to, then pls add a comment.


- Peter Bacsko


On febr. 12, 2018, 4:19 du, Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65606/
> ---
> 
> (Updated febr. 12, 2018, 4:19 du)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric. Most, if not all, examples currently use pretty old versions of 
> the schemas. We should take this opportunity to update the examples to the 
> newest schemas added by OOZIE-2687, which should help demonstrate them.
> 
> It may make sense to keep the older schemas too, to show that older workflows 
> still work. We have some examples where we have two workflow XML files that 
> do the same thing in different ways.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> bc0f4050bb3788988d3a5352a15220fbc4fa219d 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
> c236dafa5965403c33e1a400509e7c374fe2637c 
>   core/src/main/resources/oozie-default.xml 
> e53b17b3cf201b4cf7bc5371503e66327eae2126 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> 1cc569d8d7a0e61905ad6c4e940cefb00da1343d 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  2cdbde4d2fc86a07b35beadc56012c438baf8d54 
>   examples/src/main/apps/aggregator/coordinator-with-offset.xml 
> 4c351677f4afc6e85f807106d426bb2f922a28b1 
>   examples/src/main/apps/aggregator/coordinator.xml 
> 948edc1adbe09dfb6f7bffb5eebc82f3670658cc 
>   examples/src/main/apps/aggregator/job-with-offset.properties 
> 9a28ae13e50c40f70db4b0f583a63eb42f97388d 
>   examples/src/main/apps/aggregator/job.properties 
> aaf4edf7b9d030b5044610698b27a564b008f77b 
>   examples/src/main/apps/aggregator/workflow.xml 
> 4a801090e31acba23ea49da1c59a8ce4b951c654 
>   examples/src/main/apps/bundle/job.properties 
> c06edeb3f42e2eba3367b9486982dabb4caf6436 
>   examples/src/main/apps/coord-input-logic/job.properties 
> 2cd137b94999c7e1f68bb54928f1c3ce2838d59d 
>   examples/src/main/apps/coord-input-logic/workflow.xml 
> 80d31457eff6e78710ad1fb4d4f1b372c0d1e43c 
>   examples/src/main/apps/cron-schedule/coordinator.xml 
> 48a7de76245e02397b9736a95fa0132504067f9a 
>   examples/src/main/apps/cron-schedule/job.properties 
> 5b5eb43ca2bf9d8cd1b263ca3b94a552b562a20d 
>   examples/src/main/apps/cron-schedule/workflow.xml 
> b53922c8f40e691cb637b91cb182172794296a04 
>   examples/src/main/apps/cron/coordinator.xml 
> 744d14e870b59d0b89f65a78fea63fffa3ff4b8e 
>   examples/src/main/apps/cron/job.properties 
> 42875fd5a5ce393cd11717bcc55fc1bb91e0fcd3 
>   examples/src/main/apps/cron/workflow.xml 
> 63dff976f9e35a26b0ad09078778748d3d02bc3b 
>   examples/src/main/apps/custom-main/job.properties 
> b897512a1c6246308ca17b019ce400f3ec06cd7b 
>   examples/src/main/apps/custom-main/workflow.xml 
> 828dfaa0594aac0539c4e08ae8e37cb89d17eb54 
>   examples/src/main/apps/datelist-java-main/job.properties 
> e8356e3a4a2e1ae41e09f5ea124fb5360bd6e8b6 
>   examples/src/main/apps/datelist-java-main/workflow.xml 
> b59a12ebd1fc21c9e26f6a5b0348eb9c76375c03 
>   examples/src/main/apps/demo/job.properties 
> d70d3208df77e0b612005196907cecd97d7c5d21 
>   examples/src/main/apps/demo/job.windows.properties 
> ea948b20009685e1286053549fc1974669819682 
>   examples/src/main/apps/demo/workflow.xml 
> 0ceca507adc68c0674b794420c9eb733cb320879 
>   examples/src/main/apps/distcp/job.properties 
> ec9422caddcdecfa6ee9a58868cf68d7457ad4db 
>   examples/src/main/apps/distcp/workflow.xml 
> 6deecb377901613a5bb28fc18bf5beff2d30f252 
>   examples/src/main/apps/hadoop-el/job.properties 
> 1d13c27056ac58ad359b5298f12ec046bb4cc61d 
>   examples/src/main/apps/hadoop-el/workflow.xml 
> d4094d44136a7de2f85f5c9be042d5aab24b90be 
>   examples/src/main/apps/hcatalog/job.properties 
> e0aa18c264a2fa92b6c3d501d18fa39733d863ff 
>   examples/src/main/apps/hcatalog/job.properties.security 
> 2fbcc6ee9e5d94d3bba63810e6e788607747940b 
>   examples/src/main/apps/hcatalog/workflow.xml 
> d6593df1b9104179d79262d663135d73de8b55ec 
>   examples/src/main/apps/hcatalog/workflow.xml.security 
> aa3522ae4d5b6cb178f80c2e72e45c4c3de9aab5 
>   

Re: Review Request 65606: OOZIE-2814 OYA: Update example workflows to newest schemas

2018-02-14 Thread Peter Cseh via Review Board

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




core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java
Line 109 (original), 109 (patched)


Please deprecate this constant



core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java
Line 123 (original), 126 (patched)


Please remove defaultJobTracker and use the defaultRM only



core/src/main/resources/oozie-default.xml
Lines 3035-3042 (original), 3035-3042 (patched)


I think this could be removed from oozie-default.xml as part of this cleanup


- Peter Cseh


On Feb. 12, 2018, 4:19 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65606/
> ---
> 
> (Updated Feb. 12, 2018, 4:19 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2687 will add in a whole set of newer schemas that are more 
> Yarn-centric. Most, if not all, examples currently use pretty old versions of 
> the schemas. We should take this opportunity to update the examples to the 
> newest schemas added by OOZIE-2687, which should help demonstrate them.
> 
> It may make sense to keep the older schemas too, to show that older workflows 
> still work. We have some examples where we have two workflow XML files that 
> do the same thing in different ways.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> bc0f4050bb3788988d3a5352a15220fbc4fa219d 
>   
> core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java 
> c236dafa5965403c33e1a400509e7c374fe2637c 
>   core/src/main/resources/oozie-default.xml 
> e53b17b3cf201b4cf7bc5371503e66327eae2126 
>   
> core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java 
> 1cc569d8d7a0e61905ad6c4e940cefb00da1343d 
>   
> core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowAppParser.java
>  2cdbde4d2fc86a07b35beadc56012c438baf8d54 
>   examples/src/main/apps/aggregator/coordinator-with-offset.xml 
> 4c351677f4afc6e85f807106d426bb2f922a28b1 
>   examples/src/main/apps/aggregator/coordinator.xml 
> 948edc1adbe09dfb6f7bffb5eebc82f3670658cc 
>   examples/src/main/apps/aggregator/job-with-offset.properties 
> 9a28ae13e50c40f70db4b0f583a63eb42f97388d 
>   examples/src/main/apps/aggregator/job.properties 
> aaf4edf7b9d030b5044610698b27a564b008f77b 
>   examples/src/main/apps/aggregator/workflow.xml 
> 4a801090e31acba23ea49da1c59a8ce4b951c654 
>   examples/src/main/apps/bundle/job.properties 
> c06edeb3f42e2eba3367b9486982dabb4caf6436 
>   examples/src/main/apps/coord-input-logic/job.properties 
> 2cd137b94999c7e1f68bb54928f1c3ce2838d59d 
>   examples/src/main/apps/coord-input-logic/workflow.xml 
> 80d31457eff6e78710ad1fb4d4f1b372c0d1e43c 
>   examples/src/main/apps/cron-schedule/coordinator.xml 
> 48a7de76245e02397b9736a95fa0132504067f9a 
>   examples/src/main/apps/cron-schedule/job.properties 
> 5b5eb43ca2bf9d8cd1b263ca3b94a552b562a20d 
>   examples/src/main/apps/cron-schedule/workflow.xml 
> b53922c8f40e691cb637b91cb182172794296a04 
>   examples/src/main/apps/cron/coordinator.xml 
> 744d14e870b59d0b89f65a78fea63fffa3ff4b8e 
>   examples/src/main/apps/cron/job.properties 
> 42875fd5a5ce393cd11717bcc55fc1bb91e0fcd3 
>   examples/src/main/apps/cron/workflow.xml 
> 63dff976f9e35a26b0ad09078778748d3d02bc3b 
>   examples/src/main/apps/custom-main/job.properties 
> b897512a1c6246308ca17b019ce400f3ec06cd7b 
>   examples/src/main/apps/custom-main/workflow.xml 
> 828dfaa0594aac0539c4e08ae8e37cb89d17eb54 
>   examples/src/main/apps/datelist-java-main/job.properties 
> e8356e3a4a2e1ae41e09f5ea124fb5360bd6e8b6 
>   examples/src/main/apps/datelist-java-main/workflow.xml 
> b59a12ebd1fc21c9e26f6a5b0348eb9c76375c03 
>   examples/src/main/apps/demo/job.properties 
> d70d3208df77e0b612005196907cecd97d7c5d21 
>   examples/src/main/apps/demo/job.windows.properties 
> ea948b20009685e1286053549fc1974669819682 
>   examples/src/main/apps/demo/workflow.xml 
> 0ceca507adc68c0674b794420c9eb733cb320879 
>   examples/src/main/apps/distcp/job.properties 
> ec9422caddcdecfa6ee9a58868cf68d7457ad4db 
>   examples/src/main/apps/distcp/workflow.xml 
> 6deecb377901613a5bb28fc18bf5beff2d30f252 
>   examples/src/main/apps/hadoop-el/job.properties 
> 1d13c27056ac58ad359b5298f12ec046bb4cc61d 
>   examples/src/main/apps/hadoop-el/workflow.xml 
> d4094d44136a7de2f85f5c9be042d5aab24b90be 
>   examples/src/main/apps/hcatalog/job.properties 
> 

Re: Review Request 65636: OOZIE-3179 - Adding a configurable config-default.xml location to a workflow

2018-02-14 Thread Peter Cseh via Review Board

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




core/src/test/java/org/apache/oozie/command/wf/TestSubmitXCommand.java
Line 423 (original), 506-518 (patched)


I don't see the case where the same property is set in 
extra-config-default.xml and config-default.xml as well and config-default.xml 
takes precedence


- Peter Cseh


On Feb. 13, 2018, 3:07 p.m., Jason Phelps wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65636/
> ---
> 
> (Updated Feb. 13, 2018, 3:07 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Added another client property: `oozie.default.configuration.path` which 
> allows for a comma seperated list of HDFS XML property files to be applied to 
> the job. This is useful if multiple workflows have shared properties (i.e. 
> database names, table names for Sqoop or Hive, spark arguments, etc). This is 
> similar to the `oozie.libpath` property which allows user's to define common 
> paths workflows to load jars.
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/oozie/client/OozieClient.java e581e50 
>   core/src/main/java/org/apache/oozie/command/wf/SubmitXCommand.java a4d3e2f 
>   core/src/test/java/org/apache/oozie/command/wf/TestSubmitXCommand.java 
> e71a662 
> 
> 
> Diff: https://reviews.apache.org/r/65636/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Jason Phelps
> 
>



[jira] [Commented] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on OOZIE-3182:
--

PreCommit-OOZIE-Build started


> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt, log-OOZIE-3182-002.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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


[jira] [Updated] (OOZIE-3182) Oozie components fail with checkstyle errors

2018-02-14 Thread Alisha Prabhu (JIRA)

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

Alisha Prabhu updated OOZIE-3182:
-
Attachment: OOZIE-3182-003.patch

> Oozie components fail with checkstyle errors
> 
>
> Key: OOZIE-3182
> URL: https://issues.apache.org/jira/browse/OOZIE-3182
> Project: Oozie
>  Issue Type: Bug
>  Components: client, examples
>Affects Versions: 5.0.0b1
> Environment: uname -a
> Linux pts00607-vm1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 
> 2016 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Major
> Attachments: OOZIE-3182-001.patch, OOZIE-3182-002.patch, 
> OOZIE-3182-003.patch, error-log.txt, log-OOZIE-3182-002.txt
>
>
> There are multiple checkstyle violations in the oozie-client, oozie-examples, 
> oozie-mini, oozie-sharelib-oozie, oozie-sharelib module.
> Maven command used is mvn clean install -DskipTests



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