date:20171206

[jira] Subscription: Oozie Patch Available

2017-12-06 Thread jira

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

[jira] Subscription: Oozie Patch Available

2017-12-06 Thread jira

Issue Subscription
Filter: Oozie Patch Available (103 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3127  Remove redundant check for user
https://issues.apache.org/jira/browse/OOZIE-3127
OOZIE-3121  bump all maven plugins to latest versions
https://issues.apache.org/jira/browse/OOZIE-3121
OOZIE-3113  Retry for ZK lock release
https://issues.apache.org/jira/browse/OOZIE-3113
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-3083  Make improved version Info backward compatible
https://issues.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.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-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-2973  Make sure Oozie works with Hadoop 3 
https://issues.apache.org/jira/browse/OOZIE-2973
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-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE-2812
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2784  Include WEEK as

Re: Oozie 5.0.0-beta1

2017-12-06 Thread Robert Kanter

Sounds good to me!

On Wed, Dec 6, 2017 at 5:17 AM, Andras Piros 
wrote:

> Good idea Gezapeti!
>
> Time to wrap things up towards a stable 5.0.0 - a release candidate on
> 5.0.0b1 is a good first step.
>
> Since other components that Oozie uses like Pig and Hive do not (fully)
> support Hadoop 3, we have to wait with OOZIE-2973
> .
>
> Thanks,
>
> Andras
>
> On Wed, Dec 6, 2017 at 1:50 PM, Peter Cseh  wrote:
>
> > Hi everyone!
> >
> > Now that OOZIE-2969 
> is
> > committed I'd like to start the process of creating the branch for
> 5.0.0b1
> > and building a release from there.
> > It's unfortunate that we won't be able to support Hadoop 3 in the beta
> for
> > reasons described in OOZIE-2973
> > 
> > I don't see any more blockers for the beta1 and I hope we won't find
> > hard-to-fix major issues so we can release Oozie 5.0.0 in early 2018.
> > Please let me know if you have any suggestions.
> > Thanks
> > gp
> >
> > --
> > Peter Cseh
> > Software Engineer
> > 
> >
>

Re: Oozie 5.0.0-beta1

2017-12-06 Thread Andras Piros

Good idea Gezapeti!

Time to wrap things up towards a stable 5.0.0 - a release candidate on
5.0.0b1 is a good first step.

Since other components that Oozie uses like Pig and Hive do not (fully)
support Hadoop 3, we have to wait with OOZIE-2973
.

Thanks,

Andras

On Wed, Dec 6, 2017 at 1:50 PM, Peter Cseh  wrote:

> Hi everyone!
>
> Now that OOZIE-2969  is
> committed I'd like to start the process of creating the branch for 5.0.0b1
> and building a release from there.
> It's unfortunate that we won't be able to support Hadoop 3 in the beta for
> reasons described in OOZIE-2973
> 
> I don't see any more blockers for the beta1 and I hope we won't find
> hard-to-fix major issues so we can release Oozie 5.0.0 in early 2018.
> Please let me know if you have any suggestions.
> Thanks
> gp
>
> --
> Peter Cseh
> Software Engineer
> 
>

[jira] [Commented] (OOZIE-2973) Make sure Oozie works with Hadoop 3

2017-12-06 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-2973:
-

[~gezapeti] I agree with pushing out this from 5.0.0b1 as the components you 
mentioned and Oozie uses need more time to mature with Hadoop 3.

> Make sure Oozie works with Hadoop 3 
> 
>
> Key: OOZIE-2973
> URL: https://issues.apache.org/jira/browse/OOZIE-2973
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Peter Cseh
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2973.001.patch, OOZIE-2973.002.patch
>
>
> This JIRA is to track that Oozie works with Hadoop 3. 
> - Build Oozie with latest hadoop 3 (e.g. assuming Apache Hadoop 3.0.0-alpha3 
> pass {{-D-Dhadoop.version=3.0.0-alpha3}} to maven) and execute tests
> - It would be nice to create an Apache jenkins job that runs Oozie tests with 
> hadoop 3 (also with other component) 



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

Oozie 5.0.0-beta1

2017-12-06 Thread Peter Cseh

Hi everyone!

Now that OOZIE-2969  is
committed I'd like to start the process of creating the branch for 5.0.0b1
and building a release from there.
It's unfortunate that we won't be able to support Hadoop 3 in the beta for
reasons described in OOZIE-2973

I don't see any more blockers for the beta1 and I hope we won't find
hard-to-fix major issues so we can release Oozie 5.0.0 in early 2018.
Please let me know if you have any suggestions.
Thanks
gp

-- 
Peter Cseh
Software Engineer

[jira] [Updated] (OOZIE-3105) testJMXInstrumentation from the org.apache.oozie.util.TestMetricsInstrumentation class is flaky

2017-12-06 Thread Peter Cseh (JIRA)


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

Peter Cseh updated OOZIE-3105:
--
Fix Version/s: (was: 5.0.0b1)

> testJMXInstrumentation from the 
> org.apache.oozie.util.TestMetricsInstrumentation class is flaky
> ---
>
> Key: OOZIE-3105
> URL: https://issues.apache.org/jira/browse/OOZIE-3105
> Project: Oozie
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 4.3.0
> Environment: mvn: 3.5.0
> java: 1.8.0.144
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Attachments: OOZIE-3105-00.patch
>
>
> I'm able to reproduce the test failure consistently by running test in 
> isolation with the following command
> {code}
> mvn clean 
> -Dtest=org.apache.oozie.util.TestMetricsInstrumentation#testJMXInstrumentation
>  test
> {code}
> the test succeeds consistently with the following
> {code}
> mvn clean -Dtest=org.apache.oozie.util.TestMetricsInstrumentation test
> {code}



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

[jira] [Updated] (OOZIE-3094) fix for grammar mistake

2017-12-06 Thread Peter Cseh (JIRA)


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

Peter Cseh updated OOZIE-3094:
--
Fix Version/s: (was: 5.0.0b1)

> fix for grammar mistake
> ---
>
> Key: OOZIE-3094
> URL: https://issues.apache.org/jira/browse/OOZIE-3094
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Attachments: OOZIE-3094.patch
>
>
> HBase does not require any additional properties since the hbase-site.xml on 
> the Oozie server provides necessary information to the obtain delegation 
> token; though properties can be overwritten here if desired. 
> https://oozie.apache.org/docs/4.3.0/DG_ActionAuthentication.html



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

[jira] [Updated] (OOZIE-2921) Document FS move action can copy files only, i.e. /parentdir/childdir/* /targetdir

2017-12-06 Thread Peter Cseh (JIRA)


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

Peter Cseh updated OOZIE-2921:
--
Fix Version/s: (was: 5.0.0b1)

> Document FS move action can copy files only, i.e. /parentdir/childdir/* 
> /targetdir
> --
>
> Key: OOZIE-2921
> URL: https://issues.apache.org/jira/browse/OOZIE-2921
> Project: Oozie
>  Issue Type: Task
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
>
> It is not widely documented that you can do move command on the files within 
> directory rather than directory where files are located. Provide examples



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

[jira] [Updated] (OOZIE-2973) Make sure Oozie works with Hadoop 3

2017-12-06 Thread Peter Cseh (JIRA)


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

Peter Cseh updated OOZIE-2973:
--
Fix Version/s: (was: 5.0.0b1)
   5.0.0

> Make sure Oozie works with Hadoop 3 
> 
>
> Key: OOZIE-2973
> URL: https://issues.apache.org/jira/browse/OOZIE-2973
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Peter Cseh
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2973.001.patch, OOZIE-2973.002.patch
>
>
> This JIRA is to track that Oozie works with Hadoop 3. 
> - Build Oozie with latest hadoop 3 (e.g. assuming Apache Hadoop 3.0.0-alpha3 
> pass {{-D-Dhadoop.version=3.0.0-alpha3}} to maven) and execute tests
> - It would be nice to create an Apache jenkins job that runs Oozie tests with 
> hadoop 3 (also with other component) 



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

[jira] [Comment Edited] (OOZIE-3139) Oozie validates workflow incorrectly

2017-12-06 Thread Denes Bodo (JIRA)


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

Denes Bodo edited comment on OOZIE-3139 at 12/6/17 12:35 PM:
-

[~pbacsko] thanks, I did not notice that.


was (Author: dionusos):
[~pbacsko] thanks, I did not noticed that.

> Oozie validates workflow incorrectly
> 
>
> Key: OOZIE-3139
> URL: https://issues.apache.org/jira/browse/OOZIE-3139
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
> Attachments: OOZIE-3139.001.patch, OOZIE-3139.002.patch, 
> OOZIE-3139.003.patch, OOZIE-3139.004.patch, exception.log, workflow.pdf
>
>
> We found that after OOZIE-1978 the attached workflow becomes invalid. Aa we 
> found out the following line brings the problem: 
> https://github.com/apache/oozie/commit/8e9b9042b3270dc5ff975c44a5c977fcc41250e4#diff-a38ae78886b7c3afb711d32cfb4dbbbdR267
>  . The parameter "okPath" changed from okPath to true.
> The following workflow is problematic:
> {noformat}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
>  
>
> 
> Shell action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> {noformat}



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

[jira] [Updated] (OOZIE-3139) Oozie validates workflow incorrectly

2017-12-06 Thread Denes Bodo (JIRA)


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

Denes Bodo updated OOZIE-3139:
--
Attachment: OOZIE-3139.004.patch

[~pbacsko] thanks, I did not noticed that.

> Oozie validates workflow incorrectly
> 
>
> Key: OOZIE-3139
> URL: https://issues.apache.org/jira/browse/OOZIE-3139
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
> Attachments: OOZIE-3139.001.patch, OOZIE-3139.002.patch, 
> OOZIE-3139.003.patch, OOZIE-3139.004.patch, exception.log, workflow.pdf
>
>
> We found that after OOZIE-1978 the attached workflow becomes invalid. Aa we 
> found out the following line brings the problem: 
> https://github.com/apache/oozie/commit/8e9b9042b3270dc5ff975c44a5c977fcc41250e4#diff-a38ae78886b7c3afb711d32cfb4dbbbdR267
>  . The parameter "okPath" changed from okPath to true.
> The following workflow is problematic:
> {noformat}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
>  
>
> 
> Shell action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> {noformat}



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

[jira] [Commented] (OOZIE-3139) Oozie validates workflow incorrectly

2017-12-06 Thread Peter Bacsko (JIRA)


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

Peter Bacsko commented on OOZIE-3139:
-

Sorry I my suggestion above was incorrect - you're not building the WF from 
objects, instead it's loaded from an XML, so it doesn't work.

However, I'd like to ask one final (minor) change in the two new tests:

{noformat}
LiteWorkflowApp app = 
parser.validateAndParse(IOUtils.getResourceAsReader(
   "wf-multiple-error-parent.xml", -1), new Configuration());
{noformat]

The {{app}} variable is unused, therefore it generates a warning. Just drop the 
variable declaration and ignore the return value of "parser".

> Oozie validates workflow incorrectly
> 
>
> Key: OOZIE-3139
> URL: https://issues.apache.org/jira/browse/OOZIE-3139
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
> Attachments: OOZIE-3139.001.patch, OOZIE-3139.002.patch, 
> OOZIE-3139.003.patch, exception.log, workflow.pdf
>
>
> We found that after OOZIE-1978 the attached workflow becomes invalid. Aa we 
> found out the following line brings the problem: 
> https://github.com/apache/oozie/commit/8e9b9042b3270dc5ff975c44a5c977fcc41250e4#diff-a38ae78886b7c3afb711d32cfb4dbbbdR267
>  . The parameter "okPath" changed from okPath to true.
> The following workflow is problematic:
> {noformat}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
>  
>
> 
> Shell action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> {noformat}



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

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

2017-12-06 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2969:
--

Testing JIRA OOZIE-2969

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:green}+1{color} the patch does not introduce any line longer than 
132
.{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: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 [core].
. {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:green}+1 TESTS{color}
.Tests run: 2075
.Tests rerun: 64
.Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.service.TestPartitionDependencyManagerEhcache,org.apache.oozie.command.coord.TestCoordActionsKillXCommand,
{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}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/276/

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2969-0.patch, OOZIE-2969-0.patch, 
> OOZIE-2969-1.patch, OOZIE-2969-2.patch, OOZIE-2969-3.patch, screenshot-1.png
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



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

Failed: OOZIE-2969 PreCommit Build #276

2017-12-06 Thread Apache Jenkins Server

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.59 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/oozie].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/pig].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/hive].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [sharelib/spark].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [docs].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [server].
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2111 bytes
[TRACE] Full summary file size is 1248 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-2969

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 does not introduce any line longer than 132
-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
+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 [core].
 +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: 2075
Tests rerun: 64
Tests failed at first run: 
org.apache.oozie.action.hadoop.TestJavaActionExecutor,org.apache.oozie.service.TestPartitionDependencyManagerEhcache,org.apache.oozie.command.coord.TestCoordActionsKillXCommand,
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/276/

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

test-patch exit code: 1

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

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

2017-12-06 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2969:
--

Testing JIRA OOZIE-2969

Cleaning local git workspace



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



> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2969-0.patch, OOZIE-2969-0.patch, 
> OOZIE-2969-1.patch, OOZIE-2969-2.patch, screenshot-1.png
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



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

[jira] [Comment Edited] (OOZIE-2969) Drop support for Java 1.7

2017-12-06 Thread Peter Cseh (JIRA)


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

Peter Cseh edited comment on OOZIE-2969 at 12/6/17 9:09 AM:


I've triggered a job for this to see if the distro builds correctly. If so I 
think we can close this off.
https://builds.apache.org/job/PreCommit-OOZIE-Build/275/


was (Author: gezapeti):
I've triggered a job for this to see if the distro builds correctly. If so I 
think we can close this off.

> Drop support for Java 1.7
> -
>
> Key: OOZIE-2969
> URL: https://issues.apache.org/jira/browse/OOZIE-2969
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2969-0.patch, OOZIE-2969-0.patch, 
> OOZIE-2969-1.patch, OOZIE-2969-2.patch, screenshot-1.png
>
>
>  I see the last jira to drop 1.6 support only resolved end of 2016 with 
> release of 4.3 but wondering if 5.0 is a good time to drop 1.7 support? 5.0 
> will support Hadoop 3 and minimum required version to support it is 1.8. 
> Happy to pick it up if there's interest.



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

[jira] [Resolved] (OOZIE-2905) fix for warning no description for @param

2017-12-06 Thread Peter Cseh (JIRA)


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

Peter Cseh resolved OOZIE-2905.
---
Resolution: Duplicate

> fix for warning no description for @param
> -
>
> Key: OOZIE-2905
> URL: https://issues.apache.org/jira/browse/OOZIE-2905
> Project: Oozie
>  Issue Type: Sub-task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.0.0b1
>
>
> I ran {code}mvn javadoc:javadoc{code} and found 
> {noformat}
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/cli/CLIParser.java:67:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/cli/OozieCLI.java:550:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:259:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:523:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:524:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:541:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:542:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1130:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1131:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1156:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1157:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1243:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1244:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1245:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1246:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1256:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1257:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1258:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:1834:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:2029:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:3089:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:3090:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:3106:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:3107:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/OozieClient.java:3108:
>  warning: no description for @param
> [WARNING] 
> /Users/aervits/NetBeansProjects/OOZIE/oozie/client/src/main/java/org/apache/oozie/client/Job.java:116:
>  warning: no description for @param
> [WARNING] 
>

Failed: OOZIE-OOZIE-2969 PreCommit Build #274

2017-12-06 Thread Apache Jenkins Server

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

###
## LAST 100 LINES OF THE CONSOLE 
###
Started by user gezapeti
[EnvInject] - Loading node environment variables.
Building remotely on H17 (Hadoop xenial) in workspace 
/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 4a05898518af353a36465805099c947918bf7d50 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4a05898518af353a36465805099c947918bf7d50
Commit message: "OOZIE-2681 Fix javadoc to compile on JDK8 (dbist13, 
abhisekbafna, gezapeti)"
 > git rev-list 299370b44e2d7b22bfe622d19f65b02c5b18282f # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
No emails were triggered.
[PreCommit-OOZIE-Build] $ /bin/bash /tmp/jenkins3726923052704683668.sh
OOZIE-OOZIE-2969
rm: cannot remove 'distro/downloads/*': No such file or directory
rm: invalid option -- '.'
Try 'rm --help' for more information.

Testing JIRA OOZIE-OOZIE-2969

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  88650  88650 0  11520  0 --:--:-- --:--:-- --:--:-- 
11512100 390740 390740 0  45622  0 --:--:-- --:--:-- --:--:-- 
45593
OOZIE-OOZIE-2969 is not "Patch Available".  Exiting.

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 3706k0 101360 0   9468  0  0:06:40  0:00:01  0:06:39  
9468100 3706k  100 3706k0 0  2899k  0  0:00:01  0:00:01 --:--:-- 
17.4M
Adding comment to JIRA
Could not find issue with key: 'OOZIE-OOZIE-2969'

Remote error: com.atlassian.jira.rpc.exception.RemotePermissionException: This 
issue does not exist or you don't have permission to view it.

test-patch exit code: 1

Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-OOZIE-2969
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Updated] (OOZIE-3139) Oozie validates workflow incorrectly

2017-12-06 Thread Denes Bodo (JIRA)


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

Denes Bodo updated OOZIE-3139:
--
Attachment: OOZIE-3139.003.patch

003.patch is addressing Abhishek's ask.

> Oozie validates workflow incorrectly
> 
>
> Key: OOZIE-3139
> URL: https://issues.apache.org/jira/browse/OOZIE-3139
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.3.0
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
> Attachments: OOZIE-3139.001.patch, OOZIE-3139.002.patch, 
> OOZIE-3139.003.patch, exception.log, workflow.pdf
>
>
> We found that after OOZIE-1978 the attached workflow becomes invalid. Aa we 
> found out the following line brings the problem: 
> https://github.com/apache/oozie/commit/8e9b9042b3270dc5ff975c44a5c977fcc41250e4#diff-a38ae78886b7c3afb711d32cfb4dbbbdR267
>  . The parameter "okPath" changed from okPath to true.
> The following workflow is problematic:
> {noformat}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
> 
> 
> 
> ${jobTracker}
> ${nameNode}
> ${myscript}
> ${myscriptPath}
> 
> 
> 
> 
>  
>
> 
> Shell action failed, error 
> message[${wf:errorMessage(wf:lastErrorNode())}]
> 
> 
> 
> {noformat}



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

[jira] Subscription: Oozie Patch Available

[jira] Subscription: Oozie Patch Available

Re: Oozie 5.0.0-beta1

Re: Oozie 5.0.0-beta1

[jira] [Commented] (OOZIE-2973) Make sure Oozie works with Hadoop 3

Oozie 5.0.0-beta1

[jira] [Updated] (OOZIE-3105) testJMXInstrumentation from the org.apache.oozie.util.TestMetricsInstrumentation class is flaky

[jira] [Updated] (OOZIE-3094) fix for grammar mistake

[jira] [Updated] (OOZIE-2921) Document FS move action can copy files only, i.e. /parentdir/childdir/* /targetdir

[jira] [Updated] (OOZIE-2973) Make sure Oozie works with Hadoop 3

[jira] [Comment Edited] (OOZIE-3139) Oozie validates workflow incorrectly

[jira] [Updated] (OOZIE-3139) Oozie validates workflow incorrectly

[jira] [Commented] (OOZIE-3139) Oozie validates workflow incorrectly

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

Failed: OOZIE-2969 PreCommit Build #276

[jira] [Commented] (OOZIE-2969) Drop support for Java 1.7

[jira] [Comment Edited] (OOZIE-2969) Drop support for Java 1.7

[jira] [Resolved] (OOZIE-2905) fix for warning no description for @param

Failed: OOZIE-OOZIE-2969 PreCommit Build #274

[jira] [Updated] (OOZIE-3139) Oozie validates workflow incorrectly

20 matches

Site Navigation

Mail list logo

Footer information