date:20180403

[jira] Subscription: Oozie Patch Available

2018-04-03 Thread jira

Issue Subscription
Filter: Oozie Patch Available (104 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3199  Let system property restriction configurable
https://issues.apache.org/jira/browse/OOZIE-3199
OOZIE-3194  Oozie should set proper permissions to sharelib after upload
https://issues.apache.org/jira/browse/OOZIE-3194
OOZIE-3193  Applications are not killed when submitted via subworkflow
https://issues.apache.org/jira/browse/OOZIE-3193
OOZIE-3186  Oozie is unable to use configuration linked using jceks://file/...
https://issues.apache.org/jira/browse/OOZIE-3186
OOZIE-3185  Conflicting JARs org.apache.derby exist in Oozie
https://issues.apache.org/jira/browse/OOZIE-3185
OOZIE-3179  Adding a configurable config-default.xml location to a workflow
https://issues.apache.org/jira/browse/OOZIE-3179
OOZIE-3170  Oozie Diagnostic Bundle tool fails with NPE due to missing service 
class
https://issues.apache.org/jira/browse/OOZIE-3170
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3134  Potential inconsistency between the in-memory SLA map and the Oozie 
database
https://issues.apache.org/jira/browse/OOZIE-3134
OOZIE-3109  Escape log-streaming's HTML-specific characters
https://issues.apache.org/jira/browse/OOZIE-3109
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-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 o

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

2018-04-03 Thread Artem Ervits

created https://issues.apache.org/jira/browse/OOZIE-3210 and
https://issues.apache.org/jira/browse/OOZIE-3211 for some small issues
discovered.

On Tue, Apr 3, 2018 at 11:12 AM, Peter Bacsko  wrote:

> +1 from me:
>
> - compiled & run tests with Hadoop 2.6.0
> - compiled against Hadoop 2.7.2
> - checked RAT report & hash
>
> Peter
>
> On Tue, Apr 3, 2018 at 1:32 PM, Julia Kinga Marton 
> wrote:
>
> > Hi,
> >
> > +1 (non-binding)
> >
> > Here is what I did:
> > - verified sha512, signiture, rat report
> > - built against hadoop 2.6.0 and tested out in a pseudo-distributed mode
> > - run some examples
> > - clicked around UI and tried some CLI commands.
> >
> > I have opened a jira (OOZIE-3209
> > ), which is a very
> small
> > bug in the pyspark example workflow, not  in the Oozie itself.
> >
> >
> > Regards,
> > Kinga
> >
> >
> > On Sat, Mar 31, 2018 at 12:01 PM, Andras Piros <
> andras.pi...@cloudera.com>
> > wrote:
> >
> > > Hi there,
> > >
> > > extending the voting deadline for 5.0.0 RC0 as we didn't receive enough
> > > votes.
> > >
> > > New deadline for votes is Tuesday, April 3, 2018 at 12:00am PDT.
> > >
> > > Thanks,
> > >
> > > Andras Piros
> > >
> > > On Sat, Mar 31, 2018 at 4:11 AM, Robert Kanter 
> > wrote:
> > >
> > > > Did you set oozie.service.HadoopAccessorService.hadoop.
> configurations
> > > and
> > > > point it at your Hadoop configs?
> > > >
> > > > On Fri, Mar 30, 2018 at 4:12 AM, Artem Ervits  >
> > > > wrote:
> > > >
> > > > > I ran into a similar issue to Oozie-3208 except I did install
> > > sharelib. I
> > > > > can see it in hdfs and yet I get /user/share/lib does not exist.
> That
> > > > > message prevented me from running successful workflows except for
> > > no-op.
> > > > >
> > > > > On Thu, Mar 29, 2018, 5:52 PM Robert Kanter 
> > > wrote:
> > > > >
> > > > > > Here's what I did:
> > > > > > - Verified sha512
> > > > > > - Verified signature (gpg)
> > > > > > - Looked at rat report
> > > > > > - Looked at release log
> > > > > > - Built Oozie against Hadoop 2.7.2, using an empty local maven
> repo
> > > > > > - Ran a few of the examples, clicked around the UI, tried various
> > CLI
> > > > > > commands, looked at the REST output, launcher log output, etc
> > > > > >
> > > > > > +1 LGTM
> > > > > >
> > > > > > Non-blocker issues which I've filed JIRAs for
> > > > > > - OOZIE-3206 :
> > The
> > > > > > README.txt links to the 4.3.0 version of the quickstart page:
> > > > > > http://oozie.apache.org/docs/4.3.0/DG_QuickStart.html
> > > > > > - OOZIE-3207 :
> > > We're
> > > > > > using version 17 of the ASF root pom, and the latest is 19.
> > version
> > > 17
> > > > > is
> > > > > > from 2015!
> > > > > > - OOZIE-3208 :
> > If
> > > > the
> > > > > > sharelib isn't installed, you get a "It should never happen"
> error
> > > code
> > > > > > when submitting an action
> > > > > >
> > > > > > If a blocking issue is found, OOZIE-3206 and OOZIE-3208 would be
> > > > > > nice-to-have's in an RC1 (OOZIE-3207 is too risky).  Otherwise,
> we
> > > can
> > > > > save
> > > > > > them for Oozie 5.1.0.
> > > > > >
> > > > > >
> > > > > > thanks
> > > > > > - Robert
> > > > > >
> > > > > >
> > > > > > On Thu, Mar 29, 2018 at 11:00 AM, Attila Sasvari <
> > > > asasv...@cloudera.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks Andras for driving the release!
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Here is what I did:
> > > > > > > - Verified signature, hash
> > > > > > > - Created Oozie 5.0.0 distro using hadoop-2.6
> > > > > > > - On a pseudo Hadoop 2.6.0, I executed  SparkFileCopy (both in
> > > > > > > yarn-cluster, yarn-client mode),  custom-main-wf,
> > > > > datelist-java-main-wf,
> > > > > > > demo-wf, distcp-wf, hadoop-el-wf, java-main-wf, map-reduce-wf,
> > > > > no-op-wf,
> > > > > > > pig-wf, shell-wf, sqoop-freeform-wf, sqoop-wf, ssh-wf,
> > > streaming-wf,
> > > > > > > subwf-wf  - all the workflows have succeeded
> > > > > > > - Verified Web UI: version, getting logs and Job DAG
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Mar 28, 2018 at 4:30 PM, Artem Ervits <
> > > artemerv...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > additionally, I've ran the mvn verify and after some time it
> > > failed
> > > > > due
> > > > > > > to
> > > > > > > > timeout, still OK in my opinion.
> > > > > > > >
> > > > > > > > INFO] Results:
> > > > > > > > [INFO]
> > > > > > > > [INFO] Tests run: 738, Failures: 0, Errors: 0, Skipped: 0
> > > > > > > > [INFO]
> > > > > > > > [INFO]
> > > > > > > >
> > > > > > 
> > > > 
> > > > > > > > [INFO] Reactor Summary:
> > > > > > > > [INFO]
> > > > > > > > [INFO] Apache Oozie Main 5.0.0 
> > > > SUCCES

[jira] [Created] (OOZIE-3211) Warning: Deprecated property found in configuration in SparkConfigurationService is ambiguous

2018-04-03 Thread Artem Ervits (JIRA)

Artem Ervits created OOZIE-3211:
---

 Summary: Warning: Deprecated property found in configuration in 
SparkConfigurationService is ambiguous
 Key: OOZIE-3211
 URL: https://issues.apache.org/jira/browse/OOZIE-3211
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 5.0.0
 Environment: Apache Maven 3.5.3 
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
Maven home: /opt/maven/apache-maven-3.5.3
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.17.1.el7.x86_64", arch: "amd64", family: 
"unix"

Oozie 5.0 RC0 compiled from clean Maven repo

Hadoop 2.7.5 pseudo distributed
Reporter: Artem Ervits
 Fix For: 5.1.0


Getting
{code:java}
Deprecated property found in configuration: 
oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jarUse
 oozie.service.SparkConfigurationService.spark.configurations.blacklist 
instead{code}
even though property 
{code:java}
oozie.service.SparkConfigurationService.spark.configurations.blacklist{code}
is in oozie-site.xml. Looked at it with [~andras.piros] oozie-default.xml is 
part of core and is on the classpath. Need to handle 
[https://github.com/apache/oozie/blob/branch-5.0.0-beta1/core/src/main/java/org/apache/oozie/service/SparkConfigurationService.java#L74]
 condition better



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

[jira] [Created] (OOZIE-3210) revision information is empty

2018-04-03 Thread Artem Ervits (JIRA)

Artem Ervits created OOZIE-3210:
---

 Summary: revision information is empty
 Key: OOZIE-3210
 URL: https://issues.apache.org/jira/browse/OOZIE-3210
 Project: Oozie
  Issue Type: Bug
Affects Versions: 5.0.0
 Environment: {code:java}
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 
2018-02-24T19:49:05Z)
Maven home: /opt/maven/apache-maven-3.5.3
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.17.1.el7.x86_64", arch: "amd64", family: 
"unix"{code}
Reporter: Artem Ervits
 Fix For: 5.1.0


compiled from RC0
{code:java}
STARTUP MSG: Oozie BUILD_VERSION [5.0.0] compiled by [oozie] on 
[2018.04.02-19:55:20GMT]
STARTUP MSG: revision [unavailable]@[unavailable]{code}
 



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

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

2018-04-03 Thread Artem Ervits (JIRA)


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

Artem Ervits edited comment on OOZIE-3196 at 4/3/18 7:30 PM:
-

In order of priority:

1. Prevent UI access to private information

2. Prevent REST API access to private information

3. Prevent CLI access to private information

at the minimum this should be configurable at the oozie-site.xml level, when 
Oozie is restarted.

 


was (Author: dbist13):
In order of priority:

1. Prevent UI access to private information

2. Prevent REST API access to private information

3. Prevent CLI access to private information

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



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

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

2018-04-03 Thread Artem Ervits (JIRA)


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

Artem Ervits commented on OOZIE-3196:
-

In order of priority:

1. Prevent UI access to private information

2. Prevent REST API access to private information

3. Prevent CLI access to private information

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



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

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

2018-04-03 Thread Peter Bacsko

+1 from me:

- compiled & run tests with Hadoop 2.6.0
- compiled against Hadoop 2.7.2
- checked RAT report & hash

Peter

On Tue, Apr 3, 2018 at 1:32 PM, Julia Kinga Marton 
wrote:

> Hi,
>
> +1 (non-binding)
>
> Here is what I did:
> - verified sha512, signiture, rat report
> - built against hadoop 2.6.0 and tested out in a pseudo-distributed mode
> - run some examples
> - clicked around UI and tried some CLI commands.
>
> I have opened a jira (OOZIE-3209
> ), which is a very small
> bug in the pyspark example workflow, not  in the Oozie itself.
>
>
> Regards,
> Kinga
>
>
> On Sat, Mar 31, 2018 at 12:01 PM, Andras Piros 
> wrote:
>
> > Hi there,
> >
> > extending the voting deadline for 5.0.0 RC0 as we didn't receive enough
> > votes.
> >
> > New deadline for votes is Tuesday, April 3, 2018 at 12:00am PDT.
> >
> > Thanks,
> >
> > Andras Piros
> >
> > On Sat, Mar 31, 2018 at 4:11 AM, Robert Kanter 
> wrote:
> >
> > > Did you set oozie.service.HadoopAccessorService.hadoop.configurations
> > and
> > > point it at your Hadoop configs?
> > >
> > > On Fri, Mar 30, 2018 at 4:12 AM, Artem Ervits 
> > > wrote:
> > >
> > > > I ran into a similar issue to Oozie-3208 except I did install
> > sharelib. I
> > > > can see it in hdfs and yet I get /user/share/lib does not exist. That
> > > > message prevented me from running successful workflows except for
> > no-op.
> > > >
> > > > On Thu, Mar 29, 2018, 5:52 PM Robert Kanter 
> > wrote:
> > > >
> > > > > Here's what I did:
> > > > > - Verified sha512
> > > > > - Verified signature (gpg)
> > > > > - Looked at rat report
> > > > > - Looked at release log
> > > > > - Built Oozie against Hadoop 2.7.2, using an empty local maven repo
> > > > > - Ran a few of the examples, clicked around the UI, tried various
> CLI
> > > > > commands, looked at the REST output, launcher log output, etc
> > > > >
> > > > > +1 LGTM
> > > > >
> > > > > Non-blocker issues which I've filed JIRAs for
> > > > > - OOZIE-3206 :
> The
> > > > > README.txt links to the 4.3.0 version of the quickstart page:
> > > > > http://oozie.apache.org/docs/4.3.0/DG_QuickStart.html
> > > > > - OOZIE-3207 :
> > We're
> > > > > using version 17 of the ASF root pom, and the latest is 19.
> version
> > 17
> > > > is
> > > > > from 2015!
> > > > > - OOZIE-3208 :
> If
> > > the
> > > > > sharelib isn't installed, you get a "It should never happen" error
> > code
> > > > > when submitting an action
> > > > >
> > > > > If a blocking issue is found, OOZIE-3206 and OOZIE-3208 would be
> > > > > nice-to-have's in an RC1 (OOZIE-3207 is too risky).  Otherwise, we
> > can
> > > > save
> > > > > them for Oozie 5.1.0.
> > > > >
> > > > >
> > > > > thanks
> > > > > - Robert
> > > > >
> > > > >
> > > > > On Thu, Mar 29, 2018 at 11:00 AM, Attila Sasvari <
> > > asasv...@cloudera.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks Andras for driving the release!
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > Here is what I did:
> > > > > > - Verified signature, hash
> > > > > > - Created Oozie 5.0.0 distro using hadoop-2.6
> > > > > > - On a pseudo Hadoop 2.6.0, I executed  SparkFileCopy (both in
> > > > > > yarn-cluster, yarn-client mode),  custom-main-wf,
> > > > datelist-java-main-wf,
> > > > > > demo-wf, distcp-wf, hadoop-el-wf, java-main-wf, map-reduce-wf,
> > > > no-op-wf,
> > > > > > pig-wf, shell-wf, sqoop-freeform-wf, sqoop-wf, ssh-wf,
> > streaming-wf,
> > > > > > subwf-wf  - all the workflows have succeeded
> > > > > > - Verified Web UI: version, getting logs and Job DAG
> > > > > >
> > > > > >
> > > > > > On Wed, Mar 28, 2018 at 4:30 PM, Artem Ervits <
> > artemerv...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > additionally, I've ran the mvn verify and after some time it
> > failed
> > > > due
> > > > > > to
> > > > > > > timeout, still OK in my opinion.
> > > > > > >
> > > > > > > INFO] Results:
> > > > > > > [INFO]
> > > > > > > [INFO] Tests run: 738, Failures: 0, Errors: 0, Skipped: 0
> > > > > > > [INFO]
> > > > > > > [INFO]
> > > > > > >
> > > > > 
> > > 
> > > > > > > [INFO] Reactor Summary:
> > > > > > > [INFO]
> > > > > > > [INFO] Apache Oozie Main 5.0.0 
> > > SUCCESS [
> > > > > > > 3.859 s]
> > > > > > > [INFO] Apache Oozie Client 
> > > SUCCESS
> > > > [
> > > > > > > 34.826 s]
> > > > > > > [INFO] Apache Oozie Share Lib Oozie ...
> > > SUCCESS [
> > > > > > > 25.740 s]
> > > > > > > [INFO] Apache Oozie Share Lib HCatalog 
> > > SUCCESS [
> > > > > > > 11.842 s]
> > > > > > > [INFO] Apache Oozie Share Lib Distcp ..
> > > SUCCESS [
> > > > > > > 7.465 s]
> > > > > > > [INFO] Apache Oozie Core

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

2018-04-03 Thread Denes Bodo



> On March 27, 2018, 4:49 p.m., András Piros wrote:
> > Interesting idea!
> > 
> > However, in the existing approach within `ConfigurationService#loadConf()` 
> > following handling of system properties is implemented:
> > 
> > * `ConfigurationService#IGNORE_SYS_PROPS` defines the system properties 
> > that should never be overwritten, neither from config file nor from `-D` 
> > option
> > * `ConfigurationService#IGNORE_SYS_PROPS` contains both hard coded and 
> > additionally configured entries
> > * `ConfigurationService#CONF_SYS_PROPS` defines a fixed set of system 
> > properties. When the actual system property is present, and isn't contained 
> > in `ConfigurationService#IGNORE_SYS_PROPS`, a `Configuration` entry is 
> > inserted
> > * in addition to `ConfigurationService#CONF_SYS_PROPS`, all the already 
> > existing `Configuration` entries are checked for existence as a system 
> > property. If present and not contained in 
> > `ConfigurationService#IGNORE_SYS_PROPS`, the appropriare `Configuration` 
> > entry is updated
> > 
> > I'd suggest that the handling of the extra, admin-allowed system properties 
> > happens as the last step, and an extra filtering should also be taken for 
> > absence inside `ConfigurationService#IGNORE_SYS_PROPS`. The prefix should 
> > also be `oozie.`

Thank you for your explanation. I see that there is another way to solve my 
problem; simply define property in site.xml with the same name as wanted system 
property.
I am glad that this list fits into Oozie's spirit. However, do you mean that 
"The prefix should also be oozie" should be understood as the property names in 
the list should be started with oozie?

Sorry for the late reaction, I didn't get notification about your review. :\


- Denes


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


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

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-3209:
-

Failing tests are unrelated. Committed to {{master}}.

> XML schema error when submitting pyspark example
> 
>
> Key: OOZIE-3209
> URL: https://issues.apache.org/jira/browse/OOZIE-3209
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-3209-001.patch
>
>
> The following exception is thrown when the pyspark example is submitted:
> {code:java}
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'resource-manager'. One of 
> '{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
> The xmlns version should be changed to 1.0 in order to accept the 
> resource-manager element as well. 
> [https://github.com/apache/oozie/blob/master/examples/src/main/apps/3/workflow.xml#L24|https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]
>  



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

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3209:
--


Testing JIRA OOZIE-3209

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 [webapp].
. {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:red}-1 TESTS{color}
.Tests run: 2107
.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}


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

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



> XML schema error when submitting pyspark example
> 
>
> Key: OOZIE-3209
> URL: https://issues.apache.org/jira/browse/OOZIE-3209
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Minor
> Attachments: OOZIE-3209-001.patch
>
>
> The following exception is thrown when the pyspark example is submitted:
> {code:java}
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'resource-manager'. One of 
> '{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
> The xmlns version should be changed to 1.0 in order to accept the 
> resource-manager element as well. 
> [https://github.com/apache/oozie/blob/master/examples/src/main/apps/3/workflow.xml#L24|https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]
>  



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

Failed: OOZIE-3209 PreCommit Build #476

2018-04-03 Thread Apache Jenkins Server

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

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.71 MB...]
[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 2177 bytes
[TRACE] Full summary file size is 1314 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-3209

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 [webapp].
 +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: 2107
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)


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

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

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0{"self":"https://issues.apache.org/jira/rest/api/2/issue/13149711/comment/16423991","id":"16423991","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&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3209\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 
introduce any tabs

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-3209:
-

Thanks for the contribution [~kmarton]! +1 (pending Jenkins)

> XML schema error when submitting pyspark example
> 
>
> Key: OOZIE-3209
> URL: https://issues.apache.org/jira/browse/OOZIE-3209
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Minor
> Attachments: OOZIE-3209-001.patch
>
>
> The following exception is thrown when the pyspark example is submitted:
> {code:java}
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'resource-manager'. One of 
> '{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
> The xmlns version should be changed to 1.0 in order to accept the 
> resource-manager element as well. 
> [https://github.com/apache/oozie/blob/master/examples/src/main/apps/3/workflow.xml#L24|https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]
>  



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

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

2018-04-03 Thread Julia Kinga Marton

Hi,

+1 (non-binding)

Here is what I did:
- verified sha512, signiture, rat report
- built against hadoop 2.6.0 and tested out in a pseudo-distributed mode
- run some examples
- clicked around UI and tried some CLI commands.

I have opened a jira (OOZIE-3209
), which is a very small
bug in the pyspark example workflow, not  in the Oozie itself.


Regards,
Kinga


On Sat, Mar 31, 2018 at 12:01 PM, Andras Piros 
wrote:

> Hi there,
>
> extending the voting deadline for 5.0.0 RC0 as we didn't receive enough
> votes.
>
> New deadline for votes is Tuesday, April 3, 2018 at 12:00am PDT.
>
> Thanks,
>
> Andras Piros
>
> On Sat, Mar 31, 2018 at 4:11 AM, Robert Kanter  wrote:
>
> > Did you set oozie.service.HadoopAccessorService.hadoop.configurations
> and
> > point it at your Hadoop configs?
> >
> > On Fri, Mar 30, 2018 at 4:12 AM, Artem Ervits 
> > wrote:
> >
> > > I ran into a similar issue to Oozie-3208 except I did install
> sharelib. I
> > > can see it in hdfs and yet I get /user/share/lib does not exist. That
> > > message prevented me from running successful workflows except for
> no-op.
> > >
> > > On Thu, Mar 29, 2018, 5:52 PM Robert Kanter 
> wrote:
> > >
> > > > Here's what I did:
> > > > - Verified sha512
> > > > - Verified signature (gpg)
> > > > - Looked at rat report
> > > > - Looked at release log
> > > > - Built Oozie against Hadoop 2.7.2, using an empty local maven repo
> > > > - Ran a few of the examples, clicked around the UI, tried various CLI
> > > > commands, looked at the REST output, launcher log output, etc
> > > >
> > > > +1 LGTM
> > > >
> > > > Non-blocker issues which I've filed JIRAs for
> > > > - OOZIE-3206 : The
> > > > README.txt links to the 4.3.0 version of the quickstart page:
> > > > http://oozie.apache.org/docs/4.3.0/DG_QuickStart.html
> > > > - OOZIE-3207 :
> We're
> > > > using version 17 of the ASF root pom, and the latest is 19.  version
> 17
> > > is
> > > > from 2015!
> > > > - OOZIE-3208 : If
> > the
> > > > sharelib isn't installed, you get a "It should never happen" error
> code
> > > > when submitting an action
> > > >
> > > > If a blocking issue is found, OOZIE-3206 and OOZIE-3208 would be
> > > > nice-to-have's in an RC1 (OOZIE-3207 is too risky).  Otherwise, we
> can
> > > save
> > > > them for Oozie 5.1.0.
> > > >
> > > >
> > > > thanks
> > > > - Robert
> > > >
> > > >
> > > > On Thu, Mar 29, 2018 at 11:00 AM, Attila Sasvari <
> > asasv...@cloudera.com>
> > > > wrote:
> > > >
> > > > > Thanks Andras for driving the release!
> > > > >
> > > > > +1
> > > > >
> > > > > Here is what I did:
> > > > > - Verified signature, hash
> > > > > - Created Oozie 5.0.0 distro using hadoop-2.6
> > > > > - On a pseudo Hadoop 2.6.0, I executed  SparkFileCopy (both in
> > > > > yarn-cluster, yarn-client mode),  custom-main-wf,
> > > datelist-java-main-wf,
> > > > > demo-wf, distcp-wf, hadoop-el-wf, java-main-wf, map-reduce-wf,
> > > no-op-wf,
> > > > > pig-wf, shell-wf, sqoop-freeform-wf, sqoop-wf, ssh-wf,
> streaming-wf,
> > > > > subwf-wf  - all the workflows have succeeded
> > > > > - Verified Web UI: version, getting logs and Job DAG
> > > > >
> > > > >
> > > > > On Wed, Mar 28, 2018 at 4:30 PM, Artem Ervits <
> artemerv...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > additionally, I've ran the mvn verify and after some time it
> failed
> > > due
> > > > > to
> > > > > > timeout, still OK in my opinion.
> > > > > >
> > > > > > INFO] Results:
> > > > > > [INFO]
> > > > > > [INFO] Tests run: 738, Failures: 0, Errors: 0, Skipped: 0
> > > > > > [INFO]
> > > > > > [INFO]
> > > > > >
> > > > 
> > 
> > > > > > [INFO] Reactor Summary:
> > > > > > [INFO]
> > > > > > [INFO] Apache Oozie Main 5.0.0 
> > SUCCESS [
> > > > > > 3.859 s]
> > > > > > [INFO] Apache Oozie Client 
> > SUCCESS
> > > [
> > > > > > 34.826 s]
> > > > > > [INFO] Apache Oozie Share Lib Oozie ...
> > SUCCESS [
> > > > > > 25.740 s]
> > > > > > [INFO] Apache Oozie Share Lib HCatalog 
> > SUCCESS [
> > > > > > 11.842 s]
> > > > > > [INFO] Apache Oozie Share Lib Distcp ..
> > SUCCESS [
> > > > > > 7.465 s]
> > > > > > [INFO] Apache Oozie Core ..
> > FAILURE
> > > [
> > > > > > 01:30 h]
> > > > > > [INFO] Apache Oozie Share Lib Streaming ...
> SKIPPED
> > > > > > [INFO] Apache Oozie Share Lib Pig .
> SKIPPED
> > > > > > [INFO] Apache Oozie Share Lib Hive 
> SKIPPED
> > > > > > [INFO] Apache Oozie Share Lib Hive 2 ..
> SKIPPED
> > > > > > [INFO] Apache Oozie Share Lib Sqoop ...
> SKIPPED
> > > >

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3209:
--

PreCommit-OOZIE-Build started


> XML schema error when submitting pyspark example
> 
>
> Key: OOZIE-3209
> URL: https://issues.apache.org/jira/browse/OOZIE-3209
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Minor
> Attachments: OOZIE-3209-001.patch
>
>
> The following exception is thrown when the pyspark example is submitted:
> {code:java}
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'resource-manager'. One of 
> '{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
> The xmlns version should be changed to 1.0 in order to accept the 
> resource-manager element as well. 
> [https://github.com/apache/oozie/blob/master/examples/src/main/apps/3/workflow.xml#L24|https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]
>  



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

[jira] [Updated] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton updated OOZIE-3209:
--
Attachment: OOZIE-3209-001.patch

> XML schema error when submitting pyspark example
> 
>
> Key: OOZIE-3209
> URL: https://issues.apache.org/jira/browse/OOZIE-3209
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Minor
> Attachments: OOZIE-3209-001.patch
>
>
> The following exception is thrown when the pyspark example is submitted:
> {code:java}
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'resource-manager'. One of 
> '{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
> The xmlns version should be changed to 1.0 in order to accept the 
> resource-manager element as well. 
> [https://github.com/apache/oozie/blob/master/examples/src/main/apps/3/workflow.xml#L24|https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]
>  



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

[jira] [Updated] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton updated OOZIE-3209:
--
Description: 
The following exception is thrown when the pyspark example is submitted:
{code:java}
Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid content 
was found starting with element 'resource-manager'. One of 
'{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
The xmlns version should be changed to 1.0 in order to accept the 
resource-manager element as well. 

[https://github.com/apache/oozie/blob/master/examples/src/main/apps/3/workflow.xml#L24|https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]

 

  was:
The following exception is thrown when the pyspark example is submitted:
{code:java}
Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid content 
was found starting with element 'resource-manager'. One of 
'{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
The xmlns version should be changed to 1.0 in order to accept the 
resource-manager element as well. 

[https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]

 


> XML schema error when submitting pyspark example
> 
>
> Key: OOZIE-3209
> URL: https://issues.apache.org/jira/browse/OOZIE-3209
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Minor
>
> The following exception is thrown when the pyspark example is submitted:
> {code:java}
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'resource-manager'. One of 
> '{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
> The xmlns version should be changed to 1.0 in order to accept the 
> resource-manager element as well. 
> [https://github.com/apache/oozie/blob/master/examples/src/main/apps/3/workflow.xml#L24|https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]
>  



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

[jira] [Updated] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton updated OOZIE-3209:
--
Description: 
The following exception is thrown when the pyspark example is submitted:
{code:java}
Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid content 
was found starting with element 'resource-manager'. One of 
'{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
The xmlns version should be changed to 1.0 in order to accept the 
resource-manager element as well. 

[https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]

 

  was:
The following exception is thrown when the pyspark example is submitted:
{code:java}
Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid content 
was found starting with element 'resource-manager'. One of 
'{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
The xmns version should be changed to 1.0 in order to accept the 
resource-manager element as well. 

[https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]

 


> XML schema error when submitting pyspark example
> 
>
> Key: OOZIE-3209
> URL: https://issues.apache.org/jira/browse/OOZIE-3209
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: trunk
>Reporter: Julia Kinga Marton
>Assignee: Julia Kinga Marton
>Priority: Minor
>
> The following exception is thrown when the pyspark example is submitted:
> {code:java}
> Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'resource-manager'. One of 
> '{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
> The xmlns version should be changed to 1.0 in order to accept the 
> resource-manager element as well. 
> [https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]
>  



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

[jira] [Commented] (OOZIE-3208) "It should never happen" error code when running an action when Sharelib doesn't exist

2018-04-03 Thread Peter Bacsko (JIRA)


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

Peter Bacsko commented on OOZIE-3208:
-

I've seen this error message at different places, IMO it should be removed 
altogether and change it to a more meaningful one.

> "It should never happen" error code when running an action when Sharelib 
> doesn't exist
> --
>
> Key: OOZIE-3208
> URL: https://issues.apache.org/jira/browse/OOZIE-3208
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Priority: Critical
> Fix For: 5.1.0
>
>
> If you forget to install the sharelib and you try to run a workflow, the 
> action will fail (as expected), but the error code will be "It should never 
> happen".  That's not a good error code :D
> {noformat}
> 2018-03-29 14:35:02,361  WARN ActionStartXCommand:523 - 
> SERVER[rkanter-MBP.local] USER[rkanter] GROUP[-] TOKEN[] APP[map-reduce-wf] 
> JOB[000-180329142919509-oozie-rkan-W] 
> ACTION[000-180329142919509-oozie-rkan-W@mr-node] Error starting action 
> [mr-node]. ErrorType [FAILED], ErrorCode [It should never happen], Message 
> [File /user/rkanter/share/lib does not exist]
> org.apache.oozie.action.ActionExecutorException: File /user/rkanter/share/lib 
> does not exist
> at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.addSystemShareLibForAction(JavaActionExecutor.java:646)
> at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.addAllShareLibs(JavaActionExecutor.java:760)
> at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setLibFilesArchives(JavaActionExecutor.java:746)
> at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:984)
> at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1512)
> at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:243)
> at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:68)
> at org.apache.oozie.command.XCommand.call(XCommand.java:290)
> at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:334)
> at 
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:263)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:181)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> {noformat}
> Error starting action [mr-node]. ErrorType [FAILED], ErrorCode [It should 
> never happen]
> {noformat}



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

[jira] [Created] (OOZIE-3209) XML schema error when submitting pyspark example

2018-04-03 Thread Julia Kinga Marton (JIRA)

Julia Kinga Marton created OOZIE-3209:
-

 Summary: XML schema error when submitting pyspark example
 Key: OOZIE-3209
 URL: https://issues.apache.org/jira/browse/OOZIE-3209
 Project: Oozie
  Issue Type: Bug
  Components: examples
Affects Versions: trunk
Reporter: Julia Kinga Marton
Assignee: Julia Kinga Marton


The following exception is thrown when the pyspark example is submitted:
{code:java}
Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid content 
was found starting with element 'resource-manager'. One of 
'{"uri:oozie:spark-action:0.1":job-tracker}' is expected.{code}
The xmns version should be changed to 1.0 in order to accept the 
resource-manager element as well. 

[https://github.com/apache/oozie/blob/master/examples/src/main/apps/pyspark/workflow.xml#L24]

 



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

[jira] [Updated] (OOZIE-2937) Remove redundant groupId from the child POMs

2018-04-03 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-2937:

Summary: Remove redundant groupId from the child POMs  (was: Remove 
redundant groupId from the child pom's)

> Remove redundant groupId from the child POMs
> 
>
> Key: OOZIE-2937
> URL: https://issues.apache.org/jira/browse/OOZIE-2937
> Project: Oozie
>  Issue Type: Task
>  Components: build
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Trivial
> Attachments: OOZIE-2937-1.patch, OOZIE-2937-2.patch
>
>
> Currently all child pom's define the *groupId* again. That's not necessary, 
> because it is already defined in the parent pom. Remove the redundant 
> declarations of the *groupId*.



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

[jira] Subscription: Oozie Patch Available

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

[jira] [Created] (OOZIE-3211) Warning: Deprecated property found in configuration in SparkConfigurationService is ambiguous

[jira] [Created] (OOZIE-3210) revision information is empty

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

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

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

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

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

Failed: OOZIE-3209 PreCommit Build #476

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

Re: [VOTE] Release Oozie 5.0.0 (candidate 0)

[jira] [Commented] (OOZIE-3209) XML schema error when submitting pyspark example

[jira] [Updated] (OOZIE-3209) XML schema error when submitting pyspark example

[jira] [Updated] (OOZIE-3209) XML schema error when submitting pyspark example

[jira] [Updated] (OOZIE-3209) XML schema error when submitting pyspark example

[jira] [Commented] (OOZIE-3208) "It should never happen" error code when running an action when Sharelib doesn't exist

[jira] [Created] (OOZIE-3209) XML schema error when submitting pyspark example

[jira] [Updated] (OOZIE-2937) Remove redundant groupId from the child POMs

20 matches

Site Navigation

Mail list logo

Footer information