[jira] [Commented] (OOZIE-3207) Update ASF root pom version

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3207:
-

[~asalamon74] please go ahead

> Update ASF root pom version
> ---
>
> Key: OOZIE-3207
> URL: https://issues.apache.org/jira/browse/OOZIE-3207
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>    Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.2.0
>
>
> The Oozie root pom uses the ASF root pom as it's parent (as required by ASF 
> rules).  We're currently using version 17, which is from 2015.  The current 
> version is 19, from earlier this year (2018).  We should update this.  
> You can see more details about the ASF root pom, including diffs between each 
> version here:
> https://maven.apache.org/pom/asf/index.html
> This may require some testing or at least looking into because the ASF root 
> pom defines the versions of some things, especially maven plugins, and so 
> things may break or be incompatible.



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

Re: [jira] [Commented] (OOZIE-3294) Launcher exception: java.io.IOException

[Artem Ervits]

Ahmed, one thing I do to detect missing clients is run a workflow with
shell action such as
https://github.com/dbist/oozie-examples/blob/master/apps/shell/scripts/script.sh

Obviously it gets tricky when you have a lot of nodes but it's a something
so menial you can include it as part of each of your workflow.

On Thu, Jun 21, 2018, 3:35 AM Ahmed (JIRA)  wrote:

>
> [
> https://issues.apache.org/jira/browse/OOZIE-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16519209#comment-16519209
> ]
>
> Ahmed commented on OOZIE-3294:
> --
>
> [~andras.piros] Thanks for the quick response,
>
> Yes we are doing oozie shell actions. post your comment i evaluated all
> the servers with the spark-submit available, i see 1 node is not installed
> with the client(suspecting that node is causing intermittent issue
> sometimes if the oozie calls its action and YARN runs on that node & the
> failure Error is noticed.)
>
> How do i exactly identifiy node without the programme spark-submit is
> causing failure as the error logs says no such file. is there a way to find
> the exact failure cause on that specific node ?
>
> How do we fix this going forward? does installing the spark-client
> resolves this or we stop the nodemanager on this host and enable on other
> node?
>
>
>
> Regards
>
> -Ahmed
>
> > Launcher exception: java.io.IOException
> > ---
> >
> > Key: OOZIE-3294
> > URL: https://issues.apache.org/jira/browse/OOZIE-3294
> > Project: Oozie
> >  Issue Type: Bug
> >  Components: action
> >Affects Versions: 4.2.0
> >Reporter: Ahmed
> >Priority: Major
> >
> > Hi ,
> > There is an intermittent issue in oozie workflow, where the oozie action
> fails sometimes with file not found error for some actions of spark-submit
> or sqoop. (The issue is intermittent.)
> >
> > I am using hadoop - 2.7.3
> > oozie version-4.2.0
> >
> > "Launcher exception: java.io.IOException Cannot run program
> "./spark-submit" (in directory "/usr/hdp/current/spark2-client/bin"):
> error=2, No such file or directory"
> >
> >
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>

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

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3105:
-

[~pbacsko] I've ran the test multiple times with hadoop.version=2.7.6 and I 
cannot reproduce on the current master. We can close this as invalid, your call.

> 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: Peter Bacsko
>Priority: Major
> Fix For: 5.1.0
>
> 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
(v7.6.3#76005)

Re: Oozie 5.1.0 release and plans for the year

[Artem Ervits]

+1 on the plans, I won't get to the jiras I'm assigned to until next week.
Don't want to be a blocker.

On Tue, Jun 19, 2018, 4:48 AM Andras Piros  wrote:

> Good idea Gp!
>
> Thanks for volunteering as the release manager for 5.1.0. I can see *a few
> blockers
> <
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OOZIE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%205.1.0%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20%20%20priority%20DESC%2C%20updated%20DESC
> >*
> for 5.1.0 now, of which *OOZIE-3178
> * seems to be a real
> one.
>
> Regards,
>
> Andras
>
> On Tue, Jun 19, 2018 at 12:50 PM Gézapeti Cseh 
> wrote:
>
> > Hi everyone,
> >
> > Now, that Oozie-2339 is in (with other fixes as well), I think it would
> be
> > nice to release it as part of Oozie 5.1.0 so more people will try it out
> > before we jump in to do the coordinator/bunlde part as well.
> >
> > Also, we're planning to pick up on new action types with Andras and Peter
> > and probably will do a bunch of new releases as they are ready later this
> > year. The git action is the closest one, but there are others in the
> > pipeline like Maven and callback.
> >
> > Is anyone aware of issues in which we should wait for to start working on
> > 5.1.0?
> > If nobody else does, I can volunteer to be the release manager for it and
> > start the branching process in a week or so.
> >
> > thanks
> > gp
> >
>

[jira] [Commented] (OOZIE-1178) Workflow Application Master in YARN

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-1178:
-

[~andras.piros] with OYA this can be closed, no?

> Workflow Application Master in YARN
> ---
>
> Key: OOZIE-1178
> URL: https://issues.apache.org/jira/browse/OOZIE-1178
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Bo Wang
>Priority: Major
> Attachments: MAPREDUCE-4495-v1.1.patch, MAPREDUCE-4495-v1.patch, 
> MapReduceWorkflowAM.pdf, yapp_proposal.txt
>
>
> It is useful to have a workflow application master, which will be capable of 
> running a DAG of jobs. The workflow client submits a DAG request to the AM 
> and then the AM will manage the life cycle of this application in terms of 
> requesting the needed resources from the RM, and starting, monitoring and 
> retrying the application's individual tasks.
> Compared to running Oozie with the current MapReduce Application Master, 
> these are some of the advantages:
>  - Less number of consumed resources, since only one application master will 
> be spawned for the whole workflow.
>  - Reuse of resources, since the same resources can be used by multiple 
> consecutive jobs in the workflow (no need to request/wait for resources for 
> every individual job from the central RM).
>  - More optimization opportunities in terms of collective resource requests.
>  - Optimization opportunities in terms of rewriting and composing jobs in the 
> workflow (e.g. pushing down Mappers).
>  - This Application Master can be reused/extended by higher systems like Pig 
> and hive to provide an optimized way of running their workflows.



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

[jira] [Resolved] (OOZIE-2545) Output data exceeds its limit [2048]

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2545.
-
Resolution: Not A Problem

[~jingtao] please see response from [~satishsaley] to address the issue.

> Output data exceeds its limit [2048]
> 
>
> Key: OOZIE-2545
> URL: https://issues.apache.org/jira/browse/OOZIE-2545
> Project: Oozie
>  Issue Type: Bug
>Reporter: jingtao
>Priority: Major
>
> I am trying to run a simple oozie workflow executing a hive script. 
> This hive script just calls joining(tables is very large);
> Once the hive script execution ends I was expecting to see the workflow 
> status changing from RUNNING to SUCCESFUL, but this is not happening. 
> This is the content of the workflow log:
> 2016-05-31 15:52:34,591 WARN 
> org.apache.oozie.action.hadoop.HiveActionExecutor: SERVER[hadoop02] 
> USER[scapp] GROUP[-] TOKEN[] APP[wf-sqoop-hive-agreement] 
> JOB[001-160531143657136-oozie-oozi-W] 
> ACTION[001-160531143657136-oozie-oozi-W@hive-query-agreement] Launcher 
> exception: Output data exceeds its limit [2048]
> org.apache.oozie.action.hadoop.LauncherException: Output data exceeds its 
> limit [2048]
>   at 
> org.apache.oozie.action.hadoop.LauncherMapper.getLocalFileContentStr(LauncherMapper.java:415)
>   at 
> org.apache.oozie.action.hadoop.LauncherMapper.handleActionData(LauncherMapper.java:391)
>   at 
> org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:275)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:415)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
>   at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)



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

[jira] [Commented] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2211:
-

failing test is unrelated, passes locally.

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>    Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch, 
> OOZIE-2211.02.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2105:
-

[~rkanter] that's why I was wondering if this Jira made any sense at this 
point, I remember https://issues.apache.org/jira/browse/OOZIE-3097 where I used 
the mvn versions command to change all child modules. Maybe close this as won't 
fix?

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>    Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Assigned] (OOZIE-2352) Unportable shebang in shell scripts

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-2352:
---

Assignee: Artem Ervits

> Unportable shebang in shell scripts
> ---
>
> Key: OOZIE-2352
> URL: https://issues.apache.org/jira/browse/OOZIE-2352
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Dmitry Sivachenko
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2352-00.patch
>
>
> Some shell scripts in oozie distribution use unportable shebangs:
> #!/bin/bash
> bash shell interpreter may be installed in different locations (e.g 
> /usr/local/bin/bash on FreeBSD).
> The proposed solution is to use more portable
> #!/usr/bin/env bash
> instead.
> Affected files:
> client/src/main/bin/oozie
> distro/src/main/bin/addtowar.sh
> distro/src/main/bin/oozied.sh
> distro/src/main/bin/oozie-setup.sh
> distro/src/main/bin/oozie-sys.sh
> tools/src/main/bin/ooziedb.sh
> core/src/main/conf/oozie-env.sh



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

[jira] [Updated] (OOZIE-2352) Unportable shebang in shell scripts

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2352:

Attachment: OOZIE-2352-00.patch

> Unportable shebang in shell scripts
> ---
>
> Key: OOZIE-2352
> URL: https://issues.apache.org/jira/browse/OOZIE-2352
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Dmitry Sivachenko
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2352-00.patch
>
>
> Some shell scripts in oozie distribution use unportable shebangs:
> #!/bin/bash
> bash shell interpreter may be installed in different locations (e.g 
> /usr/local/bin/bash on FreeBSD).
> The proposed solution is to use more portable
> #!/usr/bin/env bash
> instead.
> Affected files:
> client/src/main/bin/oozie
> distro/src/main/bin/addtowar.sh
> distro/src/main/bin/oozied.sh
> distro/src/main/bin/oozie-setup.sh
> distro/src/main/bin/oozie-sys.sh
> tools/src/main/bin/ooziedb.sh
> core/src/main/conf/oozie-env.sh



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

[jira] [Comment Edited] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-2105 at 5/24/18 7:14 PM:
--

[~andras.piros] once I change the version to expression, we get warnings
{code:java}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-client:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-client:${project.parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/client/pom.xml, line 29, column 14
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-core:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml, line 29, column 14
[WARNING] The expression ${parent.version} is deprecated. Please use 
${project.parent.version} instead. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml{code}
I'm submitting a new patch with version removed, it will inherit version from 
parent. Btw, ${project.parent.version} expression also throws a warning.


was (Author: dbist13):
[~andras.piros] once I change the version to expression, we get warnings
{code:java}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-client:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-client:${project.parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/client/pom.xml, line 29, column 14
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-core:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml, line 29, column 14
[WARNING] The expression ${parent.version} is deprecated. Please use 
${project.parent.version} instead. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml{code}
I'm submitting a new patch with version removed, it will inherit version from 
parent.

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>    Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Updated] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2105:

Attachment: OOZIE-2105-03.patch

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>    Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-2105-03.patch, 
> OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2105:
-

[~andras.piros] once I change the version to expression, we get warnings
{code:java}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-client:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-client:${project.parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/client/pom.xml, line 29, column 14
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.oozie:oozie-core:jar:5.1.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml, line 29, column 14
[WARNING] The expression ${parent.version} is deprecated. Please use 
${project.parent.version} instead. @ 
org.apache.oozie:oozie-core:${parent.version}, 
/Users/aervits/NetBeansProjects/OOZIE/oozie/core/pom.xml{code}
I'm submitting a new patch with version removed, it will inherit version from 
parent.

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>    Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Attachment: OOZIE-2211.02.patch

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>    Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch, 
> OOZIE-2211.02.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Attachment: OOZIE-2211.01.patch

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>    Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch, OOZIE-2211.01.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Updated] (OOZIE-3256) refactor OozieCLI class

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3256:

Attachment: OOZIE-3256.00.patch

> refactor OozieCLI class
> ---
>
> Key: OOZIE-3256
> URL: https://issues.apache.org/jira/browse/OOZIE-3256
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 5.0.0
>    Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: OOZIE-3256.00.patch
>
>




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

[jira] [Created] (OOZIE-3256) refactor OozieCLI class

[Artem Ervits (JIRA)]

Artem Ervits created OOZIE-3256:
---

 Summary: refactor OozieCLI class
 Key: OOZIE-3256
 URL: https://issues.apache.org/jira/browse/OOZIE-3256
 Project: Oozie
  Issue Type: Improvement
Affects Versions: 5.0.0
Reporter: Artem Ervits
Assignee: Artem Ervits






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

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Attachment: OOZIE-2211-00.patch

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>    Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Updated] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2211:

Fix Version/s: 5.1.0

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>    Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Assigned] (OOZIE-2211) Remove OozieCLI#validateCommandV41

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-2211:
---

Assignee: Artem Ervits

> Remove OozieCLI#validateCommandV41
> --
>
> Key: OOZIE-2211
> URL: https://issues.apache.org/jira/browse/OOZIE-2211
> Project: Oozie
>  Issue Type: Task
>Reporter: Azrael Seoeun
>    Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 5.1.0
>
> Attachments: OOZIE-2211-00.patch
>
>
> XML validation API is move to server side (OOZIE-2159)
> OozieCLI#validateCommandV41 is for the backward compatibility.
> TestValidation is for the xml validation on client side.
> Those should be removed on next version. (might be 4.2.0 higher version)



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

[jira] [Resolved] (OOZIE-2002) Removed un-used property

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2002.
-
Resolution: Implemented

> Removed un-used property
> 
>
> Key: OOZIE-2002
> URL: https://issues.apache.org/jira/browse/OOZIE-2002
> Project: Oozie
>  Issue Type: Bug
>Reporter: Shwetha G S
>Priority: Trivial
>
> Looks like the following property is not used, but is available in 
> oozie-default and oozie-site
> {noformat}
>
> use.system.libpath.for.mapreduce.and.pig.jobs
> false
> 
> If set to true, submissions of MapReduce and Pig jobs will include
> automatically the system library path, thus not requiring users to
> specify where the Pig JAR files are. Instead, the ones from the 
> system
> library path are used.
> 
> 
> {noformat}



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

[jira] [Commented] (OOZIE-3255) Oozie cannot start with Hadoop 3.1.0

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3255:
-

[~andras.piros] I used
{code:java}
mv clean install -DskipTests -Dhadoop.version=3.1.0 -Puber
./bin/mkdistro.sh -DskipTests -Dhadoop.version=3.1.0 -Puber {code}

> Oozie cannot start with Hadoop 3.1.0
> 
>
> Key: OOZIE-3255
> URL: https://issues.apache.org/jira/browse/OOZIE-3255
> Project: Oozie
>  Issue Type: Bug
>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_171, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.171-8.b10.el7_5.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-862.2.3.el7.x86_64", arch: "amd64", 
> family: "unix"
>Reporter: Artem Ervits
>Priority: Major
>
> {code:java}
> bin/oozied.sh start{code}
> {code:java}
> Setting up oozie DB
> Validate DB Connection
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/util/ReflectionUtils
> at org.apache.oozie.service.Services.setServiceInternal(Services.java:377)
> at org.apache.oozie.service.Services.(Services.java:111)
> at org.apache.oozie.tools.OozieDBCLI.getJdbcConf(OozieDBCLI.java:169)
> at org.apache.oozie.tools.OozieDBCLI.createConnection(OozieDBCLI.java:918)
> at org.apache.oozie.tools.OozieDBCLI.validateConnection(OozieDBCLI.java:926)
> at org.apache.oozie.tools.OozieDBCLI.createDB(OozieDBCLI.java:188)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:131)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:79)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.hadoop.util.ReflectionUtils
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 8 more{code}
> {code:java}
> /opt/oozie/oozie-5.1.0-SNAPSHOT/bin/oozie-setup.sh sharelib create -fs 
> hdfs://hadoop.example.com:8020 -locallib ~/share/{code}
> {code:java}
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/hadoop/fs/Path
> at org.apache.oozie.tools.OozieSharelibCLI.run(OozieSharelibCLI.java:153)
> at org.apache.oozie.tools.OozieSharelibCLI.main(OozieSharelibCLI.java:67)
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.fs.Path
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 2 more{code}



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

[jira] [Updated] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2105:

Fix Version/s: 5.1.0

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>    Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Assigned] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-2105:
---

Assignee: Artem Ervits  (was: Mohammad Kamrul Islam)

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>    Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Updated] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2105:

Attachment: OOZIE-2105-02.patch

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>    Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-2105-02.patch, OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3178:
-

[~andras.piros] & [~gezapeti] please review the latest patch, I added a new 
function to look for javadoc errors.

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Comment Edited] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-3178 at 5/24/18 3:54 PM:
--

[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind.

 

also, addressing a minor issue in OOZIE-2363


was (Author: dbist13):
[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

 

also, addressing a minor issue in OOZIE-2363

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Updated] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3178:

Attachment: OOZIE-3178-02.patch

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>    Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch, 
> OOZIE-3178-02.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Comment Edited] (OOZIE-2301) JA017: Could not lookup launched hadoop Job ID

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-2301 at 5/24/18 2:46 PM:
--

[~mobinranjbar] I apologize, should've explained my motives. Apache Jira is not 
a place for individual issue resolution, this is clearly a message from Oozie 
with a valid Oozie error ID. A better place for questions like that would be on 
the Hue mailing list, Oozie mailing list, a vendor forum or StackOverflow where 
you clearly already have a question open:

[https://stackoverflow.com/questions/31379961/ja017-could-not-lookup-launched-hadoop-job-id]

Here's one possible solution for your problem: 
[https://community.hortonworks.com/content/supportkb/148594/errorja017-could-not-lookup-launched-hadoop-job-id.html]

Jira is for actual bugs, enhancements and new features to a project.


was (Author: dbist13):
[~mobinranjbar] I apologize, should've explained my motives. Apache Jira is not 
a place for individual issue resolution, this is clearly a message from Oozie 
with a valid Oozie error ID. A better place for questions like that would be on 
the Hue mailing list, Oozie mailing list, a vendor forum or StackOverflow where 
you clearly already have a question open:

[https://stackoverflow.com/questions/31379961/ja017-could-not-lookup-launched-hadoop-job-id]

Here's one possible solution for your problem: 
https://community.hortonworks.com/content/supportkb/148594/errorja017-could-not-lookup-launched-hadoop-job-id.html

 

> JA017: Could not lookup launched hadoop Job ID 
> ---
>
> Key: OOZIE-2301
> URL: https://issues.apache.org/jira/browse/OOZIE-2301
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mobin Ranjbar
>Priority: Major
>
> How can I solve this problem when I submit a mapreduce job in Oozie Editor in 
> Hue? :
> JA017: Could not lookup launched hadoop Job ID [job_local152843681_0009] 
> which was associated with action 
> [009-150711083342968-oozie-root-W@mapreduce-f660]. Failing this action!



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

[jira] [Updated] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3178:

Attachment: OOZIE-3178-01.patch

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>    Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Comment Edited] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-3178 at 5/24/18 1:59 PM:
--

[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

 

also, addressing a minor issue in OOZIE-2363


was (Author: dbist13):
[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch, OOZIE-3178-01.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Resolved] (OOZIE-2363) the redundant comma in CodecFactory.java

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2363.
-
Resolution: Fixed

since this is a minor fix, I will address it as part of another issue.

> the redundant comma in CodecFactory.java
> 
>
> Key: OOZIE-2363
> URL: https://issues.apache.org/jira/browse/OOZIE-2363
> Project: Oozie
>  Issue Type: Bug
>Reporter: sunmeng
>Priority: Major
>




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

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3178:
-

[~andras.piros] happy to do so, not sure which report pre hook is executed 
against as on my environment, I have to run mvn javadoc:javadoc goal then 
followed by mvn site and I'm getting
{code:java}
[INFO] < org.apache.oozie:oozie-tools >
[INFO] Building Apache Oozie Tools 5.1.0-SNAPSHOT [17/21]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-site-plugin:2.0-beta-6:site (default-site) @ oozie-tools ---
[INFO] Unable to load parent project from a relative path: 1 problem was 
encountered while building the effective model
[FATAL] Non-readable POM 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml: 
/Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml (No such file or 
directory) @
for project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml for 
project at /Users/aervits/NetBeansProjects/OOZIE/oozie/../pom.xml
[INFO] Parent project loaded from repository.{code}
can someone point me to the right report so I know how to modify the pre hook? 
Also, javadoc plugin 3.0 is out and I'm updating the patch with that in mind. 
Also, I think it's time to address mvn site plugin, the one we have is way old 
and uses a hacked version of Doxia. I once looked at it but this is over my 
head.

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3178-00.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Resolved] (OOZIE-2297) Oozie 4.2.0 does not build oozie-4.2.0-hadooplibs.tar.gz

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2297.
-
Resolution: Not A Problem

> Oozie 4.2.0 does not build oozie-4.2.0-hadooplibs.tar.gz
> 
>
> Key: OOZIE-2297
> URL: https://issues.apache.org/jira/browse/OOZIE-2297
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mobin Ranjbar
>Priority: Major
>
> After running "bin/mkdistro.sh -DskipTests -Dhadoopversion=2.6.0" I cannot 
> find oozie-4.2.0-hadooplibs.tar.gz in hadooplibs/target folder. Many others 
> have this problem too.



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

[jira] [Resolved] (OOZIE-2301) JA017: Could not lookup launched hadoop Job ID

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2301.
-
Resolution: Not A Problem

> JA017: Could not lookup launched hadoop Job ID 
> ---
>
> Key: OOZIE-2301
> URL: https://issues.apache.org/jira/browse/OOZIE-2301
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mobin Ranjbar
>Priority: Major
>
> How can I solve this problem when I submit a mapreduce job in Oozie Editor in 
> Hue? :
> JA017: Could not lookup launched hadoop Job ID [job_local152843681_0009] 
> which was associated with action 
> [009-150711083342968-oozie-root-W@mapreduce-f660]. Failing this action!



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

[jira] [Updated] (OOZIE-2336) Few testcases of TestStatusTransitService are failing

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2336:

Issue Type: Sub-task  (was: Bug)
Parent: OOZIE-3111

> Few testcases of TestStatusTransitService are failing
> -
>
> Key: OOZIE-2336
> URL: https://issues.apache.org/jira/browse/OOZIE-2336
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Purshotam Shah
>Priority: Major
>
> test-C@1] Released lock for [000-150817195742795-oozie-jenk-B] in 
> [bundle_status_transit]
> 19:57:43,472  INFO StatusTransitService$StatusTransitRunnable:520 - USER[-] 
> GROUP[-] TOKEN[] APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Released lock for 
> [org.apache.oozie.service.StatusTransitService]
> 19:57:43,474  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting up to [3,000] msec
> 19:57:43,474  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting up to [3,000] msec
> 19:57:44,477  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting up to [1,999] msec
> 19:57:46,478  INFO TestStatusTransitService:520 - USER[-] GROUP[-] TOKEN[] 
> APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Waiting timed out after 
> [1,000] msec
> {color:red}
> 19:57:46,480  INFO StatusTransitService$StatusTransitRunnable:520 - USER[-] 
> GROUP[-] TOKEN[] APP[-] JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] This StatusTransitService 
> instance will not run since there is already an instance running
> {color}
> 19:57:46,484  INFO Services:520 - USER[-] GROUP[-] TOKEN[] APP[-] 
> JOB[000-150817195742795-oozie-jenk-B] 
> ACTION[001-130521183438837-oozie-test-C@1] Shutdown



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

[jira] [Resolved] (OOZIE-2866) Oozie MiniOozie tests fail with Hadoop 2.7.1

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2866.
-
Resolution: Implemented

this issue no longer applies

> Oozie MiniOozie tests fail with Hadoop 2.7.1
> 
>
> Key: OOZIE-2866
> URL: https://issues.apache.org/jira/browse/OOZIE-2866
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Affects Versions: trunk
> Environment: $ uname -a
> Linux 9efcdb4d8880 3.19.0-37-generic #42-Ubuntu SMP Fri Nov 20 18:22:05 UTC 
> 2015 x86_64 x86_64 x86_64 GNU/Linux
> $ java -version
> openjdk version "1.8.0_111"
> OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>Reporter: Pravin Dsilva
>Priority: Major
>  Labels: test
> Attachments: org.apache.oozie.test.WorkflowTest-output.txt, 
> org.apache.oozie.test.WorkflowTest.txt
>
>
> Branch used: Master
> In the Oozie MiniOozie project, test org.apache.oozie.test.WorkflowTest fails
> {code}
>  mvn clean install  -Dhadoop.version=2.7.1 
> -Dtest=org.apache.oozie.test.WorkflowTest
> {code}
> {code}
> Running org.apache.oozie.test.WorkflowTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1,021.367 sec 
> <<< FAILURE!
> Results :
> Tests in error: 
>   testWorkflowRun(org.apache.oozie.test.WorkflowTest): Timed out waiting for 
> Mini HDFS Cluster to start
>   testWorkflowRunFromFile(org.apache.oozie.test.WorkflowTest): Timed out 
> waiting for Mini HDFS Cluster to start
> {code}
> Attached the logs for reference



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

[jira] [Resolved] (OOZIE-2381) Error: E0501

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2381.
-
Resolution: Not A Problem

> Error: E0501 
> -
>
> Key: OOZIE-2381
> URL: https://issues.apache.org/jira/browse/OOZIE-2381
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.1.0
> Environment: Ubuntu 14.04,Java 1.7,Hadoop 2.4.0,oozie 4.1.0
>Reporter: Veerendra Nath Jasthi
>Priority: Major
> Fix For: 4.1.0
>
>
> when i am trying to run this command,i am getting error like this:
> Error: E0501 : E0501: Could not perform authorization operation, Call From 
> ubuntu/127.0.1.1 to localhost:8020 failed on connection exception: 
> java.net.ConnectException: Connection refused; For more details see: 
> http://wiki.apache.org/hadoop/ConnectionRefused
> Could anyone help me out on this issue?



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

[jira] [Resolved] (OOZIE-2388) whether Oozie can do something to adapter ExjJs's License in webconsole?

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2388.
-
Resolution: Duplicate

duplicate of OOZIE-2683

> whether Oozie can do something to adapter ExjJs's License in webconsole?
> 
>
> Key: OOZIE-2388
> URL: https://issues.apache.org/jira/browse/OOZIE-2388
> Project: Oozie
>  Issue Type: Wish
>Reporter: teva
>Priority: Major
>
> when we use oozie to manager hadoop job in web, we have to follow with the 
> extjs framework's license in our product. Can oozie do somthing  to stop the 
> infect for using extjs's license?



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

[jira] [Resolved] (OOZIE-2417) Installation of oozie-4.2.0 with hadoop-2.7.1 in ubuntu14.10

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2417.
-

> Installation of oozie-4.2.0 with hadoop-2.7.1 in ubuntu14.10
> 
>
> Key: OOZIE-2417
> URL: https://issues.apache.org/jira/browse/OOZIE-2417
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 4.2.0
> Environment: Ubuntu
>Reporter: Prakash K
>Priority: Major
>
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Oozie Main . SUCCESS [3.052s]
> [INFO] Apache Oozie Hadoop Utils . SUCCESS [2.923s]
> [INFO] Apache Oozie Hadoop Distcp hadoop-1-4.2.0 . SUCCESS [0.200s]
> [INFO] Apache Oozie Hadoop Auth hadoop-1-4.2.0 ... SUCCESS [0.743s]
> [INFO] Apache Oozie Hadoop Libs .. SUCCESS [0.097s]
> [INFO] Apache Oozie Client ... SUCCESS [8:55.503s]
> [INFO] Apache Oozie Share Lib Oozie .. SUCCESS [5.255s]
> [INFO] Apache Oozie Share Lib HCatalog ... SUCCESS [4.685s]
> [INFO] Apache Oozie Share Lib Distcp . SUCCESS [1.151s]
> [INFO] Apache Oozie Core . SUCCESS [2:52.545s]
> [INFO] Apache Oozie Share Lib Streaming .. SUCCESS [8.308s]
> [INFO] Apache Oozie Share Lib Pig  SUCCESS [5.895s]
> [INFO] Apache Oozie Share Lib Hive ... SUCCESS [9.332s]
> [INFO] Apache Oozie Share Lib Hive 2 . SUCCESS [6.478s]
> [INFO] Apache Oozie Share Lib Sqoop .. SUCCESS [3.998s]
> [INFO] Apache Oozie Examples . SUCCESS [7.173s]
> [INFO] Apache Oozie Share Lib Spark .. SUCCESS [8.885s]
> [INFO] Apache Oozie Share Lib  SUCCESS [25.821s]
> [INFO] Apache Oozie Docs . FAILURE [14.284s]
> [INFO] Apache Oozie WebApp ... SKIPPED
> [INFO] Apache Oozie Tools  SKIPPED
> [INFO] Apache Oozie MiniOozie  SKIPPED
> [INFO] Apache Oozie Distro ... SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests . SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 13:47.847s
> [INFO] Finished at: Tue Dec 08 03:41:03 PST 2015
> [INFO] Final Memory: 300M/643M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site (default) on 
> project oozie-docs: The site descriptor cannot be resolved from the 
> repository: Could not transfer artifact org.apache:apache:xml:site_en:16 
> from/to Codehaus repository (http://repository.codehaus.org/): 
> repository.codehaus.org
> [ERROR] org.apache:apache:xml:16
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] central (http://repo1.maven.org/maven2, releases=true, 
> snapshots=false),
> [ERROR] Codehaus repository (http://repository.codehaus.org/, releases=true, 
> snapshots=false),
> [ERROR] apache.snapshots.repo 
> (https://repository.apache.org/content/groups/snapshots, releases=true, 
> snapshots=true),
> [ERROR] datanucleus (http://www.datanucleus.org/downloads/maven2, 
> releases=true, snapshots=false),
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true): Unknown host repository.codehaus.org
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :oozie-docs
> ERROR, Oozie distro creation failed



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

[jira] [Resolved] (OOZIE-2189) Upgrade to hadoop 2.6 and TestJavaActionExecutor.testUpdateConfForTimeLineServiceEnabled failure in hadoop-2

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2189.
-
Resolution: Fixed

Oozie 5 bumped hadoop to 2.6

> Upgrade to hadoop 2.6 and 
> TestJavaActionExecutor.testUpdateConfForTimeLineServiceEnabled failure in 
> hadoop-2
> 
>
> Key: OOZIE-2189
> URL: https://issues.apache.org/jira/browse/OOZIE-2189
> Project: Oozie
>  Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Rohini Palaniswamy
>Priority: Major
>
>   Patch was done with hadoop 2.3.0 when yarn.timeline-service.enabled was not 
> set in yarn-default.xml. Now with hadoop-2.4.0 it fails, as that is set to 
> true in yarn-default.xml. It was set to false in hadoop-2.4.1 (YARN-1962).  
> So instead of going to hadoop-2.4.1, going directly to hadoop-2.6. 



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

[jira] [Commented] (OOZIE-2105) Make version of submodules configurable with parent version

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2105:
-

[~andras.piros] I think this behavior is already in place with Oozie 5?

> Make version of submodules configurable with parent version 
> 
>
> Key: OOZIE-2105
> URL: https://issues.apache.org/jira/browse/OOZIE-2105
> Project: Oozie
>  Issue Type: Bug
>Reporter: Mohammad Kamrul Islam
>Assignee: Mohammad Kamrul Islam
>Priority: Major
> Attachments: OOZIE-6252.1.patch
>
>
> Currently the versions of the Oozie sub-modules are hard-coded with parent 
> version. If someone changes the parent version, all sub-modules versions will 
> need to be explicitly updated. For example, in hadooplibs/hadoop-1/pom.xml we 
> use
> org.apache.oozie
>  oozie-hadoop
>  1.1.1.oozie-4.1.0
>  ...
> If you want to modify the Oozie version to 4.1.1 (say), you need to go to all 
> pom files and manually change replace 4.1.0 to 4.1.1.
> This JIRA is to use "parent.version" instead of hard-coding. For example, use 
> this :
> 1.1.1.oozie-${parent.version}
>  
> This will allow to change only the parent version in root pom.xml.
>  



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

[jira] [Updated] (OOZIE-1855) TestPriorityDelayQueue#testPoll failed intermittently in Jenkins

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-1855:

Issue Type: Sub-task  (was: Bug)
Parent: OOZIE-3111

> TestPriorityDelayQueue#testPoll failed intermittently in Jenkins
> 
>
> Key: OOZIE-1855
> URL: https://issues.apache.org/jira/browse/OOZIE-1855
> Project: Oozie
>  Issue Type: Sub-task
> Environment: Windows
>Reporter: Ostap
>Assignee: Ostap
>Priority: Major
> Attachments: BUG-18115.patch
>
>
> Test failed with the next error:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.oozie.util.TestPriorityDelayQueue.testPoll(TestPriorityDelayQueue.java:167)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:243)
>   at junit.framework.TestSuite.run(TestSuite.java:238)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>   at 
> org.apache.maven.surefire.junitcore.ClassDemarcatingRunner.run(ClassDemarcatingRunner.java:58)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:24)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>   at java.lang.Thread.run(Thread.java:722)
> {noformat}



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

[jira] [Commented] (OOZIE-2605) email action chinese disorderly code

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2605:
-

shouldn't this be directed to Hue dev list? [~andras.piros]

> email action chinese disorderly code
> 
>
> Key: OOZIE-2605
> URL: https://issues.apache.org/jira/browse/OOZIE-2605
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.1.0
> Environment: HUE 4.1.0
>Reporter: gewenhui
>Priority: Major
> Fix For: 4.1.0
>
>
> I use cloudera manager install the oozie and use HUE Operate oozie.
> Send Chinese mail ,it appears chinese disorderly code



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

[jira] [Resolved] (OOZIE-2040) Do not require Java v1.6 exact version for building Oozie. >= 1.6 rather.

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2040.
-
Resolution: Fixed

with Oozie 5.0, Java 8 is supported and Java 6 is dropped.

> Do not require Java v1.6 exact version for building Oozie. >= 1.6 rather.
> -
>
> Key: OOZIE-2040
> URL: https://issues.apache.org/jira/browse/OOZIE-2040
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
> Environment: All
>Reporter: Tony Reix
>Priority: Major
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> oozie pom.xml file says:
> 
> 1.6
> Requiring Java 1.6 (though Oozie compiles and runs perfectly with Java 1.7) 
> creates issues:
> - on machines where no Java 1.6 JVM is available (like on Ubuntu/PPC64LE)
> - when Oozie source code is automaticaly downloaded and compiled within a 
> product that does not require Java 1.6. When compiling Falcon, its pom.xml 
> and .sh files download Oozie source code and compiles it. No way to patch the 
> Oozie pom.xml "1.6" string by "1.7".
> So, it would help that Oozie requires a java version greater or equal to 1.6 .



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

[jira] [Updated] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3178:

Attachment: OOZIE-3178-00.patch

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Attachments: OOZIE-3178-00.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Assigned] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-3178:
---

Assignee: Artem Ervits  (was: Peter Cseh)

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Artem Ervits
>Priority: Blocker
> Attachments: OOZIE-3178-00.patch
>
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Updated] (OOZIE-2566) TestCoordActionInputCheckXCommand.testCoordActionInputCheckXCommandUniqueness() is flaky

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2566:

Issue Type: Sub-task  (was: Bug)
Parent: OOZIE-3111

> TestCoordActionInputCheckXCommand.testCoordActionInputCheckXCommandUniqueness()
>  is flaky
> 
>
> Key: OOZIE-2566
> URL: https://issues.apache.org/jira/browse/OOZIE-2566
> Project: Oozie
>  Issue Type: Sub-task
>  Components: core
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Major
>
> The testcase testCoordActionInputCheckXCommandUniqueness is unstable.
> We add three XCommands with the same actionId (entityKeys are different) into 
> the CallableQueueService. Only the first XCommand is expected to run.
> The reason why sometimes either the 2nd or 3rd XCommand executes is because 
> as soon as the first starts to run, its removed from the {{uniqueCallables}} 
> map immediately. If the first scheduled task runs quickly, then either the 
> 2nd or 3rd XCommand has the chance to get scheduled.
> Step by step:
> 1. Schedule first XCommand
> 2. XCommand is added to {{uniqueCallables}}
> 3. Schedule second XCommand
> 4. First XCommand starts to run in the thread pool and removes itself from 
> {{uniqueCallables}} (see {{CallableWrapper.run()}})
> 5. Second XCommand can successfully add itself to {{uniqueCallables}}
> 6. Second XCommand starts to run
> Please clarify whether this is the expected behavior of CallableQueueService.
> If not, then moving {{removeFromUniqueCallables()}} to the finally block 
> solves the problem.



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

[jira] [Commented] (OOZIE-2633) Some Oozie 4.2 maven artifacts missing from maven central

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2633:
-

doesn't sound like an issue? [~andras.piros]

> Some Oozie 4.2 maven artifacts missing from maven central
> -
>
> Key: OOZIE-2633
> URL: https://issues.apache.org/jira/browse/OOZIE-2633
> Project: Oozie
>  Issue Type: Wish
>  Components: bundle
>Affects Versions: 4.2.0
>Reporter: Tom Edwards
>Priority: Major
>  Labels: maven
>
> Some of the maven artifacts are missing for Oozie version 4.2, however they 
> exist for version 4.1.  The specific artifacts missing for 4.2 are:
>   - oozie-hadoop
>   - oozie-hadoop-dist
>   - oozie-hadoop-test
>   - oozie-hadoop-utils
> These artifacts are needed in order to perform certain integration with Oozie.



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

[jira] [Updated] (OOZIE-2883) OOZIE throw the error "Missing [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups] property"

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2883:

Fix Version/s: 5.1.0

> OOZIE throw the error "Missing 
> [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
>  property"
> --
>
> Key: OOZIE-2883
> URL: https://issues.apache.org/jira/browse/OOZIE-2883
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: yangfang
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2883.001.patch
>
>
> When I started oozie server without the configuration 
> "oozie.service.ProxyUserService.proxyuser.#USER#.groups", I got the error 
> "E0551: Missing 
> [oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
>  property" ,because I  don't have this configuration, but the exception tells 
> us 
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups",
>  
> "oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups"
>  does not exist at all. The correct configuration is 
> "oozie.service.ProxyUserService.proxyuser.mr.groups".



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

[jira] [Resolved] (OOZIE-2450) Oozie 4.2.0 Build Fails - oozie-docs

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2450.
-
Resolution: Cannot Reproduce

> Oozie 4.2.0 Build Fails  - oozie-docs
> -
>
> Key: OOZIE-2450
> URL: https://issues.apache.org/jira/browse/OOZIE-2450
> Project: Oozie
>  Issue Type: Task
>  Components: docs
>Affects Versions: 4.2.0
> Environment: Ubuntu 15.10
>Reporter: shri
>Priority: Major
>
> bin/mkdistro.sh -DskipTests -U -X
> While building the Oozie 4.2.0, getting the error at oozie-docs.
> The POM.xml has modified for Java Version 1.7
> Unable to find the way to resolve the same. Looks to be plugin version 
> problem ?
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site (default) on 
> project oozie-docs: Error parsing site descriptor: Unrecognised tag: 'html' 
> (position: START_TAG seen ...\n... @3:7) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site (default) on 
> project oozie-docs: Error parsing site descriptor
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing site 
> descriptor
>   at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.readDecorationModel(AbstractSiteRenderingMojo.java:279)
>   at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:238)
>   at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:245)
>   at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:245)
>   at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:527)
>   at 
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:466)
>   at 
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
>   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 20 more
> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: 
> Unrecognised tag: 'html' (position: START_TAG seen ... html>\n... @3:7) 
>   at 
> org.apache.maven.doxia.site.decoration.io.xpp3.DecorationXpp3Reader.parseDecorationModel(Decora

[jira] [Resolved] (OOZIE-2455) Installation of oozie-4.2.0 with hadoop-2.6.0 in ubuntu14.04

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-2455.
-
Resolution: Cannot Reproduce

> Installation of oozie-4.2.0 with hadoop-2.6.0 in ubuntu14.04
> 
>
> Key: OOZIE-2455
> URL: https://issues.apache.org/jira/browse/OOZIE-2455
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 4.2.0
> Environment: Ubuntu maven-3.2.3  jdk1.7.0_80
>Reporter: xiangtao
>Priority: Major
>
> Build Oozie whith  ./bin/mkdistro.sh -DskipTests 
> But i get error : 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Oozie Main .. SUCCESS [  3.427 
> s]
> [INFO] Apache Oozie Hadoop Utils .. SUCCESS [  2.553 
> s]
> [INFO] Apache Oozie Hadoop Distcp hadoop-1-4.2.0 .. SUCCESS [  0.157 
> s]
> [INFO] Apache Oozie Hadoop Auth hadoop-1-4.2.0  SUCCESS [  0.329 
> s]
> [INFO] Apache Oozie Hadoop Libs ... SUCCESS [  0.029 
> s]
> [INFO] Apache Oozie Client  SUCCESS [02:16 
> min]
> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [  3.518 
> s]
> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [  3.742 
> s]
> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [  0.912 
> s]
> [INFO] Apache Oozie Core .. SUCCESS [03:29 
> min]
> [INFO] Apache Oozie Share Lib Streaming ... SUCCESS [  4.883 
> s]
> [INFO] Apache Oozie Share Lib Pig . SUCCESS [  3.890 
> s]
> [INFO] Apache Oozie Share Lib Hive  SUCCESS [  8.251 
> s]
> [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [  6.320 
> s]
> [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [  2.293 
> s]
> [INFO] Apache Oozie Examples .. SUCCESS [  4.656 
> s]
> [INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 10.411 
> s]
> [INFO] Apache Oozie Share Lib . SUCCESS [ 13.630 
> s]
> [INFO] Apache Oozie Docs .. FAILURE [  0.892 
> s]
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 06:59 min
> [INFO] Finished at: 2016-02-17T15:17:26+08:00
> [INFO] Final Memory: 189M/755M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site (default) on 
> project oozie-docs: Error parsing site descriptor: Unrecognised tag: 'html' 
> (position: START_TAG seen ... @1:6) -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :oozie-docs
> ERROR, Oozie distro creation failed



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

[jira] [Updated] (OOZIE-2783) TestHive2ActionExecutor.testHive2Action is flaky

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2783:

Issue Type: Sub-task  (was: Bug)
Parent: OOZIE-3111

> TestHive2ActionExecutor.testHive2Action is flaky
> 
>
> Key: OOZIE-2783
> URL: https://issues.apache.org/jira/browse/OOZIE-2783
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Satish Subhashrao Saley
>Priority: Major
>
> {code}
> junit.framework.ComparisonFailure: expected:<[SUCCEED]ED> but 
> was:<[FAILED/KILL]ED>
>   at junit.framework.Assert.assertEquals(Assert.java:85)
>   at junit.framework.Assert.assertEquals(Assert.java:91)
>   at 
> org.apache.oozie.action.hadoop.TestHive2ActionExecutor.testHive2Action(TestHive2ActionExecutor.java:225)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> {code}
> Test case stack trace. It is unable to find default database
> {code}
> 22:12:20,119 ERROR RetryingHMSHandler:135 - 
> NoSuchObjectException(message:There is no database named default)
>   at 
> org.apache.hadoop.hive.metastore.ObjectStore.getMDatabase(ObjectStore.java:487)
>   at 
> org.apache.hadoop.hive.metastore.ObjectStore.getDatabase(ObjectStore.java:498)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at 
> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:108)
>   at com.sun.proxy.$Proxy95.getDatabase(Unknown Source)
>   at 
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.get_database(HiveMetaStore.java:796)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at 
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
>   at com.sun.proxy.$Proxy97.get_database(Unknown Source)
>   at 
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.getDatabase(HiveMetaStoreClient.java:949)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at 
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:89)
>   at com.sun.proxy.$Proxy98.getDatabase(Unknown Source)
>   at org.apache.hadoop.hive.ql.metadata.Hive.getDatabase(Hive.java:1165)
>   at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.getDatabase(BaseSemanticAnalyzer.java:1296)
>   at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.getDatabase(BaseSemanticAnalyzer.java:1291)
>   at 
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeCreateTable(SemanticAnalyzer.java:9944)
>   at 
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9180)
>   at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:327)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:422)
>   at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:322)
>   at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:975)
>   at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:968)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:99)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.run(SQLOperation.java:172)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:231)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:218)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccesso

[jira] [Commented] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3178:
-

as part of OOZIE-3207, it's suggested to run a test with 
{code:java}
-Papache-release{code}
 

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>Priority: Blocker
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



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

[jira] [Commented] (OOZIE-3207) Update ASF root pom version

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3207:
-

I tried to take a stab at it but ran into issues with OOZIE-3120 as the profile 
19 pulls maven-assembly-plugin and that requires descriptors that no longer 
satisfy empty.xml. If we solve OOZIE-3120, we can proceed here. 
maven-assembly-plugin: 
[org.apache.apache.resources:apache-source-release-assembly-descriptor:1.0.6|https://maven.apache.org/apache-resource-bundles/]
 is in the dependencies

> Update ASF root pom version
> ---
>
> Key: OOZIE-3207
> URL: https://issues.apache.org/jira/browse/OOZIE-3207
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Priority: Blocker
> Fix For: 5.1.0
>
>
> The Oozie root pom uses the ASF root pom as it's parent (as required by ASF 
> rules).  We're currently using version 17, which is from 2015.  The current 
> version is 19, from earlier this year (2018).  We should update this.  
> You can see more details about the ASF root pom, including diffs between each 
> version here:
> https://maven.apache.org/pom/asf/index.html
> This may require some testing or at least looking into because the ASF root 
> pom defines the versions of some things, especially maven plugins, and so 
> things may break or be incompatible.



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

[jira] [Assigned] (OOZIE-3207) Update ASF root pom version

[Artem Ervits (JIRA)]

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

Artem Ervits reassigned OOZIE-3207:
---

Assignee: Artem Ervits

> Update ASF root pom version
> ---
>
> Key: OOZIE-3207
> URL: https://issues.apache.org/jira/browse/OOZIE-3207
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>    Assignee: Artem Ervits
>Priority: Blocker
> Fix For: 5.1.0
>
>
> The Oozie root pom uses the ASF root pom as it's parent (as required by ASF 
> rules).  We're currently using version 17, which is from 2015.  The current 
> version is 19, from earlier this year (2018).  We should update this.  
> You can see more details about the ASF root pom, including diffs between each 
> version here:
> https://maven.apache.org/pom/asf/index.html
> This may require some testing or at least looking into because the ASF root 
> pom defines the versions of some things, especially maven plugins, and so 
> things may break or be incompatible.



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

[jira] [Commented] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3120:
-

getting [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default-cli) on 
project oozie-main: Error reading assemblies: No assembly descriptors found. -> 
[Help 1]
[ERROR]

> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>    Assignee: Artem Ervits
>Priority: Major
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on 
> project oozie-main: No formats specified in the execution parameters or the 
> assembly descriptor. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> ERROR, Oozie distro creation failed
> {noformat}



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

[jira] [Created] (OOZIE-3255) Oozie cannot start with Hadoop 3.1.0

[Artem Ervits (JIRA)]

Artem Ervits created OOZIE-3255:
---

 Summary: Oozie cannot start with Hadoop 3.1.0
 Key: OOZIE-3255
 URL: https://issues.apache.org/jira/browse/OOZIE-3255
 Project: Oozie
  Issue Type: Bug
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_171, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.171-8.b10.el7_5.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-862.2.3.el7.x86_64", arch: "amd64", family: 
"unix"
Reporter: Artem Ervits


{code:java}
bin/oozied.sh start{code}
{code:java}
Setting up oozie DB

Validate DB Connection
Exception in thread "main" java.lang.NoClassDefFoundError: 
org/apache/hadoop/util/ReflectionUtils
at org.apache.oozie.service.Services.setServiceInternal(Services.java:377)
at org.apache.oozie.service.Services.(Services.java:111)
at org.apache.oozie.tools.OozieDBCLI.getJdbcConf(OozieDBCLI.java:169)
at org.apache.oozie.tools.OozieDBCLI.createConnection(OozieDBCLI.java:918)
at org.apache.oozie.tools.OozieDBCLI.validateConnection(OozieDBCLI.java:926)
at org.apache.oozie.tools.OozieDBCLI.createDB(OozieDBCLI.java:188)
at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:131)
at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:79)
Caused by: java.lang.ClassNotFoundException: 
org.apache.hadoop.util.ReflectionUtils
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 8 more{code}
{code:java}
/opt/oozie/oozie-5.1.0-SNAPSHOT/bin/oozie-setup.sh sharelib create -fs 
hdfs://hadoop.example.com:8020 -locallib ~/share/{code}
{code:java}
Exception in thread "main" java.lang.NoClassDefFoundError: 
org/apache/hadoop/fs/Path
at org.apache.oozie.tools.OozieSharelibCLI.run(OozieSharelibCLI.java:153)
at org.apache.oozie.tools.OozieSharelibCLI.main(OozieSharelibCLI.java:67)
Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.fs.Path
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 2 more{code}



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

[jira] [Commented] (OOZIE-2562) Web application not getting started and Tomcat is shutting down with hadoop-2.7.2

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2562:
-

[~andras.piros] invalid?

> Web application not getting started and Tomcat is shutting down with 
> hadoop-2.7.2
> -
>
> Key: OOZIE-2562
> URL: https://issues.apache.org/jira/browse/OOZIE-2562
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.2.0
> Environment: Centos7
>Reporter: Prakash K
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: catalina.2016-06-09.log, catalina.out, oozie-error.log, 
> oozie-instrumentation.log, oozie-jpa.log, oozie-ops.log, oozie.log
>
>   Original Estimate: 53h
>  Remaining Estimate: 53h
>
> Jun 08, 2016 11:40:47 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal 
> performance in production environments was not found on the 
> java.library.path: 
> Jun 08, 2016 11:40:48 AM org.apache.coyote.http11.Http11Protocol init
> SEVERE: Error initializing endpoint
> java.net.BindException: Address already in use :11000
>   at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:549)
>   at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:182)
>   at 
> org.apache.catalina.connector.Connector.initialize(Connector.java:1123)
>   at 
> org.apache.catalina.core.StandardService.initialize(StandardService.java:703)
>   at 
> org.apache.catalina.core.StandardServer.initialize(StandardServer.java:843)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:538)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:562)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
>   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Caused by: java.net.BindException: Address already in use
>   at java.net.PlainSocketImpl.socketBind(Native Method)
>   at 
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
>   at java.net.ServerSocket.bind(ServerSocket.java:376)
>   at java.net.ServerSocket.(ServerSocket.java:237)
>   at java.net.ServerSocket.(ServerSocket.java:181)
>   at 
> org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
>   at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:538)
>   ... 12 more
> Jun 08, 2016 11:40:48 AM org.apache.catalina.core.StandardService initialize
> SEVERE: Failed to initialize connector [Connector[HTTP/1.1-11000]]
> LifecycleException:  Protocol handler initialization failed: 
> java.net.BindException: Address already in use :11000
>   at 
> org.apache.catalina.connector.Connector.initialize(Connector.java:1125)
>   at 
> org.apache.catalina.core.StandardService.initialize(StandardService.java:703)
>   at 
> org.apache.catalina.core.StandardServer.initialize(StandardServer.java:843)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:538)
>   at org.apache.catalina.startup.Catalina.load(Catalina.java:562)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
>   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Jun 08, 2016 11:40:48 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 594 ms
> Jun 08, 2016 11:40:48 AM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Jun 08, 2016 11:40:48 AM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.43
> Jun 08, 2016 11:40:48 AM org.apache.catalina.startup.HostConfig 
> deployDescriptor
> INFO: Deploying configuration descriptor oozie.xml
> Jun 08, 2016 11:40:52 AM org.apache.catalina.loader.WebappClassLoader 
> validateJarFile
> INFO:

[jira] [Commented] (OOZIE-1516) Usability issues submitting jobs

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-1516:
-

[~andras.piros] invalid?

> Usability issues submitting jobs
> 
>
> Key: OOZIE-1516
> URL: https://issues.apache.org/jira/browse/OOZIE-1516
> Project: Oozie
>  Issue Type: Improvement
>  Components: examples
> Environment: Cloudera CDH4 latest on Centos
>Reporter: Brad Cox
>Priority: Critical
>
> J Harsh suggested filing a usability issue concerning a problem he helped me 
> resolve via email. Problem seems to boil down to differences between 
> localhost and localhost.localdomain that I don't understand well enough to 
> explain here. I've enclosed the email thread as documentation.
> J Harsh...
> I believe we seem to be doing a strict hostname check in Apache Oozie
> and not a resolving check. Could you report an improvement on the
> Apache Oozie JIRA (https://issues.apache.org/jira/browse/OOZIE)
> upstream to perhaps improve this for usability?
> On Sun, Sep 1, 2013 at 2:41 AM, Brad Cox <bradj...@gmail.com> wrote:
> Copied examples to /user/cloudera/examples and changed nameNode to
> hdfs://localhost.localdomain in job.properties. Results look like a good
> sign.
> [cloudera@localhost Desktop]$ oozie job -oozie http://localhost:11000/oozie
> -config examples/apps/map-reduce/job.properties -run
> job: 000-130831130415538-oozie-oozi-W
> But in oozie console, got a job fail because jobTracker's not in whitelist
> so changed that to just localhost.localdomain by analogy.
> [cloudera@localhost Desktop]$ oozie job -oozie http://localhost:11000/oozie
> -config examples/apps/map-reduce/job.properties -run
> job: 001-130831130415538-oozie-oozi-W
> Console says that try succeeded. So thanks for the help!!
> All I'm missing is an understanding of why cloudera comes outOfBox with some
> services configured as localhost and others localhost.localdomain. I always
> thought they were equivalent. But these are huge differences; success vs
> fail.
> On Aug 31, 2013, at 4:58 PM, Brad Cox <bradj...@gmail.com> wrote:
> You mean use localhost.localdomain instead of localhost? Or should I define
> a unique name with hostname cmd, restart all, and use that instead?
> [cloudera@localhost Desktop]$ hostname
> localhost.localdomain
> On Aug 31, 2013, at 4:54 PM, Harsh J <ha...@cloudera.com> wrote:
> The whitelist message is close to the solution. Do not use 'localhost'
> in your job.properties, but replace it with whatever the command
> 'hostname' produces on your terminal, and I believe it should do the
> trick.
> On Sat, Aug 31, 2013 at 11:11 PM, Brad Cox <bradj...@gmail.com> wrote:
> That's what I tried in previous attempts. That causes this
> oozie job -oozie http://localhost:11000/oozie -config
> examples/apps/map-reduce/job.properties -run
> Error: HTTP error code: 500 : Internal Server Error
> /var/log/lochost.date.log contains
> Caused by: java.net.URISyntaxException: Relative path in absolute URI:
> localhost:8020/user/cloudera/examples/apps/map-reduce
>  at java.net.URI.checkPath(URI.java:1788)
> examples is where I put it as you said
> [cloudera@localhost Desktop]$ hdfs dfs -ls /
> Found 8 items
> drwxr-xr-x   - hdfs  supergroup  0 2013-08-30 15:28 /accumulo
> drwxr-xr-x   - oozie supergroup  0 2013-08-31 04:52 /examples
> drwxr-xr-x   - hbase hbase   0 2013-08-31 07:22 /hbase
> drwxr-xr-x   - hdfs  supergroup  0 2013-08-30 16:38 /share
> drwxr-xr-x   - solr  solr0 2013-07-17 00:03 /solr
> drwxrwxrwx   - hdfs  supergroup  0 2013-08-30 16:32 /tmp
> drwxr-xr-x   - hdfs  supergroup  0 2013-08-30 16:32 /user
> drwxr-xr-x   - hdfs  supergroup  0 2013-07-17 00:03 /var
> All this is after hacking nameNode=localhost:8020 (was hdfs://...) in
> job.properties based on the Running the Examples section of the Oozie docs.
> On reverting that change, the message changed to the problem I had before:
> oozie job -oozie http://localhost:11000/oozie -config
> examples/apps/map-reduce/job.properties -run
> Error: E0901 : E0901: Namenode [localhost:8020] not allowed, not in Oozies
> whitelist
> Based on that msg, I'd already changed
> oozie.service.HadoopAccessorService.nameNode.whitelist to localhost:8020 in
> /etc/oozie/conf/oozie-site.xml and just made a similar change to
> jobTracker.whitelist to localhost:8021. Best I've been able to do is switch
> mystifying messages.
> On Aug 31, 2013, at 12:22 PM, Harsh J <ha...@cloudera.co

[jira] [Commented] (OOZIE-1745) can't start oozie : java.lang.ClassNotFoundException : org.apache.hadoop.util.PlatformName

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-1745:
-

[~andras.piros] this is no longer valid

> can't start oozie : java.lang.ClassNotFoundException : 
> org.apache.hadoop.util.PlatformName
> --
>
> Key: OOZIE-1745
> URL: https://issues.apache.org/jira/browse/OOZIE-1745
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: trunk
> Environment: ubuntu 64 
>Reporter: lulu prat
>Priority: Critical
>
> i build oozie and do the tuto 
> :http://www.linuxpedia.fr/doku.php/expert/systeme_chiffre_luks_pam_cryptsetup
> but when i run : bin/oozied.sh run 
> i get the error:
> ERROR: Oozie could not be started
> REASON: java.lang.NoClassDefFoundError: org/apache/hadoop/util/PlatformName
> Stacktrace:
> -
> java.lang.NoClassDefFoundError: org/apache/hadoop/util/PlatformName
>   at 
> org.apache.hadoop.security.UserGroupInformation.getOSLoginModuleName(UserGroupInformation.java:337)
>   at 
> org.apache.hadoop.security.UserGroupInformation.(UserGroupInformation.java:382)
>   at 
> org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:132)
>   at 
> org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:98)
>   at 
> org.apache.oozie.service.Services.setServiceInternal(Services.java:368)
>   at org.apache.oozie.service.Services.setService(Services.java:354)
>   at org.apache.oozie.service.Services.loadServices(Services.java:287)
>   at org.apache.oozie.service.Services.init(Services.java:208)
>   at 
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:45)
>   at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
>   at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
>   at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
>   at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
>   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
>   at 
> org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
>   at 
> org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
>   at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
>   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
>   at 
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
>   at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
>   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
>   at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
>   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
>   at 
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
>   at 
> org.apache.catalina.core.StandardService.start(StandardService.java:525)
>   at 
> org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
>   at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:622)
>   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
>   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.hadoop.util.PlatformName
>   at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
>   at 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
>   ... 33 more



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

[jira] [Commented] (OOZIE-2217) Oozie-4.1.0 Installation failed during oozie-client install

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2217:
-

ping [~andras.piros] i think this is invalid at this point? Oozie compiles with 
Java 8.

> Oozie-4.1.0 Installation failed during oozie-client install
> ---
>
> Key: OOZIE-2217
> URL: https://issues.apache.org/jira/browse/OOZIE-2217
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 4.0.1
> Environment: CentOS 6 with Java-1.8 version
>Reporter: Vikram Janarthanan
>Priority: Critical
>  Labels: maven
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.7:javadoc (default) on 
> project oozie-client: An error has occurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:88:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:91:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:148:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:172:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:174:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:199:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:202:
>  error: self-closing element not allowed
> [ERROR] * 
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:265:
>  error: bad use of '>'
> [ERROR] * null -> KerberosAuthenticator
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:266:
>  error: bad use of '>'
> [ERROR] * SIMPLE -> PseudoAuthenticator
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:267:
>  error: bad use of '>'
> [ERROR] * KERBEROS -> KerberosAuthenticator
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:270:
>  error: exception not thrown: org.apache.oozie.client.OozieClientException
> [ERROR] * @throws OozieClientException
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java:270:
>  warning: no description for @throws
> [ERROR] * @throws OozieClientException
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:174:
>  warning: no @throws for java.io.IOException
> [ERROR] public String submitPig(Properties conf, String pigScriptFile, 
> String[] pigArgs) throws IOException, OozieClientException {
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:187:
>  warning: no @param for jobType
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String jobType)
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:187:
>  warning: no @throws for java.io.IOException
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String jobType)
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:202:
>  warning: no @param for jobType
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String[] params, String jobType)
> [ERROR] ^
> [ERROR] 
> /home/CSS/oozie-4.1.0/client/src/main/java/org/apache/oozie/client/XOozieClient.java:202:
>  warning: no @throws for java.io.IOException
> [ERROR] public String submitScriptLanguage(Properties conf, String 
> scriptFile, String[] args, String[] params, String jobType)
> [ERROR]

[jira] [Commented] (OOZIE-1874) ./oozied.sh: line 104: /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/bin/catalina.sh: No such file or directory

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-1874:
-

ping [~andras.piros] is this still relevant? prepare-war function goes away.

> ./oozied.sh: line 104: 
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/bin/catalina.sh: 
> No such file or directory
> 
>
> Key: OOZIE-1874
> URL: https://issues.apache.org/jira/browse/OOZIE-1874
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: ubuntu 12.04 LTS
>Reporter: ADARSHA HOTA
>Priority: Blocker
>
> At the time of installation process of Oozie-4.0.1 on Hadoop-2.3.0 , while 
> invoking "./oozied.sh prepare-war" command below error is coming.
> Setting OOZIE_HOME:  /usr/local/hadoop/oozie-4.0.1/distro/src/main
> Setting OOZIE_CONFIG:
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/conf
> Setting OOZIE_CONFIG_FILE:   oozie-site.xml
> Setting OOZIE_DATA:  
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/data
> Setting OOZIE_LOG:   
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/logs
> Setting OOZIE_LOG4J_FILE:oozie-log4j.properties
> Setting OOZIE_LOG4J_RELOAD:  10
> Setting OOZIE_HTTP_HOSTNAME: localhost
> Setting OOZIE_HTTP_PORT: 11000
> Setting OOZIE_ADMIN_PORT: 11001
> Setting OOZIE_HTTPS_PORT: 11443
> Setting OOZIE_BASE_URL:  http://localhost:11000/oozie
> Setting CATALINA_BASE:   
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server
> Setting OOZIE_HTTPS_KEYSTORE_FILE: /home/user/.keystore
> Setting OOZIE_HTTPS_KEYSTORE_PASS: password
> Setting CATALINA_OUT:
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/logs/catalina.out
> Setting CATALINA_PID:
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/temp/oozie.pid
> ./oozied.sh: line 104: 
> /usr/local/hadoop/oozie-4.0.1/distro/src/main/oozie-server/bin/catalina.sh: 
> No such file or directory



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

[jira] [Updated] (OOZIE-2364) Remove deprecated SLAEventBean and related code

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2364:

Fix Version/s: (was: trunk)
   5.1.0

> Remove deprecated SLAEventBean and related code
> ---
>
> Key: OOZIE-2364
> URL: https://issues.apache.org/jira/browse/OOZIE-2364
> Project: Oozie
>  Issue Type: Task
>Reporter: Rohini Palaniswamy
>Assignee: Satish Subhashrao Saley
>Priority: Major
>  Labels: newbie
> Fix For: 5.1.0
>
> Attachments: OOZIE-2364-1.patch, OOZIE-2364-2.patch, 
> OOZIE-2364-3.patch, OOZIE-2364-4.patch
>
>
>   With new SLAService feature which uses different tables, the old SLA_EVENTS 
> table is not used anymore. Need to remove all code related to it and drop 
> that table as well.



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

[jira] [Updated] (OOZIE-3185) Conflicting JARs org.apache.derby exist in Oozie

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3185:

Fix Version/s: 5.1.0

> Conflicting JARs org.apache.derby exist in Oozie
> 
>
> Key: OOZIE-3185
> URL: https://issues.apache.org/jira/browse/OOZIE-3185
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: PandaMonkey
>Assignee: PandaMonkey
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: 0001-Fix1.patch, oozie.txt
>
>
> Hi, by analyzing oozie-master\core\pom.xml, I found that there are two 
> versions of org.apache.derby:derby. Their introduced paths are:
> 1. 
> org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile
> 2. 
> org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile
> Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by 
> org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct 
> dependency. By further analyzing the source code, *we found they have too 
> many different features*.
> Also, I found that you have already gave derby a exclusion tag when 
> transitively introducing derby by hive-beeline to avoid dependency conflict.
> So it would be nice to keep the consistency of library version for the 
> project long-term health, maybe *update org.apache.derby:derby from 10.10.1.1 
> to 10.11.1.1, or exclude derby from hive-exec* is a good choice. Hope this 
> can help you. Thanks.



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

[jira] [Resolved] (OOZIE-3002) address findbugs errors in client lib

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-3002.
-
Resolution: Duplicate

duplicate of https://issues.apache.org/jira/browse/OOZIE-2955

> address findbugs errors in client lib
> -
>
> Key: OOZIE-3002
> URL: https://issues.apache.org/jira/browse/OOZIE-3002
> Project: Oozie
>  Issue Type: Bug
>  Components: client
>Affects Versions: 4.3.0
> Environment: Java 1.8.0.131
> Maven 3.5.0
> OSX 10.12.5
> commit 18694b616f419ed958230cedb2dc0431a9f9cb5d
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Attachments: OOZIE-3002-0.patch
>
>




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

[jira] [Commented] (OOZIE-2826) Falcon feed fails to aws s3; Oozie joda time version does not meet required jar version 2.2 or later

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2826:
-

joda-time is now being used in core so my original patch doesn't work, put joda 
back into main pom, sharelib/pig tests pass successfully. Couldn't run full 
suite successfully due to flaky tests.

> Falcon feed fails to aws s3; Oozie joda time version does not meet required 
> jar version 2.2 or later
> 
>
> Key: OOZIE-2826
> URL: https://issues.apache.org/jira/browse/OOZIE-2826
> Project: Oozie
>  Issue Type: Bug
>  Components: workflow
>Affects Versions: 4.3.0
>Reporter: Péter Gergő Barna
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-2826-03.patch, OOZIE-2826-1.patch, 
> OOZIE-2826-2.patch, OOZIE-2826.patch, oozie-joda.example-feed.xml, 
> oozie-joda.log.txt
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Symptom:
> 2016-11-04 17:34:50,283 WARN [main] 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler: Unable to parse 
> last modified date: Wed, 02 Nov 2016 23:05:38 GMT
> java.lang.IllegalStateException: Joda-time 2.2 or later version is 
> required, but found version: 2.1
>   at com.amazonaws.util.DateUtils.handleException(DateUtils.java:149)
>   at com.amazonaws.util.DateUtils.parseRFC822Date(DateUtils.java:195)
>   at 
> com.amazonaws.services.s3.internal.ServiceUtils.parseRfc822Date(ServiceUtils.java:78)
>   at 
> com.amazonaws.services.s3.internal.AbstractS3ResponseHandler.populateObjectMetadata(AbstractS3ResponseHandler.java:115)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:32)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:25)
>   at 
> com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:1072)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:746)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
>   at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1050)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1027)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getObjectMetadata(S3AFileSystem.java:850)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getFileStatus(S3AFileSystem.java:1403)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.innerMkdirs(S3AFileSystem.java:1343)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.mkdirs(S3AFileSystem.java:1308)
>   at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:1898)
>   at 
> org.apache.falcon.util.DistCPOptionsUtil.getDistCpOptions(DistCPOptionsUtil.java:90)
>   at 
> org.apache.falcon.replication.FeedReplicator.getDistCpOptions(FeedReplicator.java:229)
>   at 
> org.apache.falcon.replication.FeedReplicator.run(FeedReplicator.java:70)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>   at 
> org.apache.falcon.replication.FeedReplicator.main(FeedReplicator.java:64)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at org.apache.oozie.action.hadoop.JavaMain.run(JavaMain.java:56)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.JavaMain.main(JavaMain.java:35)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org

[jira] [Updated] (OOZIE-2826) Falcon feed fails to aws s3; Oozie joda time version does not meet required jar version 2.2 or later

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2826:

Attachment: OOZIE-2826-03.patch

> Falcon feed fails to aws s3; Oozie joda time version does not meet required 
> jar version 2.2 or later
> 
>
> Key: OOZIE-2826
> URL: https://issues.apache.org/jira/browse/OOZIE-2826
> Project: Oozie
>  Issue Type: Bug
>  Components: workflow
>Affects Versions: 4.3.0
>Reporter: Péter Gergő Barna
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-2826-03.patch, OOZIE-2826-1.patch, 
> OOZIE-2826-2.patch, OOZIE-2826.patch, oozie-joda.example-feed.xml, 
> oozie-joda.log.txt
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Symptom:
> 2016-11-04 17:34:50,283 WARN [main] 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler: Unable to parse 
> last modified date: Wed, 02 Nov 2016 23:05:38 GMT
> java.lang.IllegalStateException: Joda-time 2.2 or later version is 
> required, but found version: 2.1
>   at com.amazonaws.util.DateUtils.handleException(DateUtils.java:149)
>   at com.amazonaws.util.DateUtils.parseRFC822Date(DateUtils.java:195)
>   at 
> com.amazonaws.services.s3.internal.ServiceUtils.parseRfc822Date(ServiceUtils.java:78)
>   at 
> com.amazonaws.services.s3.internal.AbstractS3ResponseHandler.populateObjectMetadata(AbstractS3ResponseHandler.java:115)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:32)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:25)
>   at 
> com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:1072)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:746)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
>   at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1050)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1027)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getObjectMetadata(S3AFileSystem.java:850)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getFileStatus(S3AFileSystem.java:1403)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.innerMkdirs(S3AFileSystem.java:1343)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.mkdirs(S3AFileSystem.java:1308)
>   at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:1898)
>   at 
> org.apache.falcon.util.DistCPOptionsUtil.getDistCpOptions(DistCPOptionsUtil.java:90)
>   at 
> org.apache.falcon.replication.FeedReplicator.getDistCpOptions(FeedReplicator.java:229)
>   at 
> org.apache.falcon.replication.FeedReplicator.run(FeedReplicator.java:70)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>   at 
> org.apache.falcon.replication.FeedReplicator.main(FeedReplicator.java:64)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at org.apache.oozie.action.hadoop.JavaMain.run(JavaMain.java:56)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.JavaMain.main(JavaMain.java:35)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>

[jira] [Updated] (OOZIE-2826) Falcon feed fails to aws s3; Oozie joda time version does not meet required jar version 2.2 or later

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-2826:

Fix Version/s: 5.1.0

> Falcon feed fails to aws s3; Oozie joda time version does not meet required 
> jar version 2.2 or later
> 
>
> Key: OOZIE-2826
> URL: https://issues.apache.org/jira/browse/OOZIE-2826
> Project: Oozie
>  Issue Type: Bug
>  Components: workflow
>Affects Versions: 4.3.0
>Reporter: Péter Gergő Barna
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: OOZIE-2826-03.patch, OOZIE-2826-1.patch, 
> OOZIE-2826-2.patch, OOZIE-2826.patch, oozie-joda.example-feed.xml, 
> oozie-joda.log.txt
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Symptom:
> 2016-11-04 17:34:50,283 WARN [main] 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler: Unable to parse 
> last modified date: Wed, 02 Nov 2016 23:05:38 GMT
> java.lang.IllegalStateException: Joda-time 2.2 or later version is 
> required, but found version: 2.1
>   at com.amazonaws.util.DateUtils.handleException(DateUtils.java:149)
>   at com.amazonaws.util.DateUtils.parseRFC822Date(DateUtils.java:195)
>   at 
> com.amazonaws.services.s3.internal.ServiceUtils.parseRfc822Date(ServiceUtils.java:78)
>   at 
> com.amazonaws.services.s3.internal.AbstractS3ResponseHandler.populateObjectMetadata(AbstractS3ResponseHandler.java:115)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:32)
>   at 
> com.amazonaws.services.s3.internal.S3MetadataResponseHandler.handle(S3MetadataResponseHandler.java:25)
>   at 
> com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:1072)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:746)
>   at 
> com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
>   at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1050)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1027)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getObjectMetadata(S3AFileSystem.java:850)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.getFileStatus(S3AFileSystem.java:1403)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.innerMkdirs(S3AFileSystem.java:1343)
>   at 
> org.apache.hadoop.fs.s3a.S3AFileSystem.mkdirs(S3AFileSystem.java:1308)
>   at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:1898)
>   at 
> org.apache.falcon.util.DistCPOptionsUtil.getDistCpOptions(DistCPOptionsUtil.java:90)
>   at 
> org.apache.falcon.replication.FeedReplicator.getDistCpOptions(FeedReplicator.java:229)
>   at 
> org.apache.falcon.replication.FeedReplicator.run(FeedReplicator.java:70)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>   at 
> org.apache.falcon.replication.FeedReplicator.main(FeedReplicator.java:64)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at org.apache.oozie.action.hadoop.JavaMain.run(JavaMain.java:56)
>   at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:51)
>   at org.apache.oozie.action.hadoop.JavaMain.main(JavaMain.java:35)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:242)
>   at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
>   at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:453)
>   at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
>   at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168)
>   at java.security

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

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3094:

Labels: trivial  (was: )

> 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
>  Labels: trivial
> Fix For: 5.1.0
>
> 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
(v7.6.3#76005)

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

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3094:

Fix Version/s: 5.1.0

> 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
>  Labels: trivial
> Fix For: 5.1.0
>
> 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
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3221) rename DEFAULT_LAUNCHER_MAX_ATTEMPS

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3221:

Attachment: OOZIE-3221.00.patch

> rename DEFAULT_LAUNCHER_MAX_ATTEMPS
> ---
>
> Key: OOZIE-3221
> URL: https://issues.apache.org/jira/browse/OOZIE-3221
> Project: Oozie
>  Issue Type: Bug
>        Reporter: Artem Ervits
>    Assignee: Artem Ervits
>Priority: Trivial
> Attachments: OOZIE-3221.00.patch
>
>




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

[jira] [Created] (OOZIE-3221) rename DEFAULT_LAUNCHER_MAX_ATTEMPS

[Artem Ervits (JIRA)]

Artem Ervits created OOZIE-3221:
---

 Summary: rename DEFAULT_LAUNCHER_MAX_ATTEMPS
 Key: OOZIE-3221
 URL: https://issues.apache.org/jira/browse/OOZIE-3221
 Project: Oozie
  Issue Type: Bug
Reporter: Artem Ervits
Assignee: Artem Ervits






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

[jira] [Created] (OOZIE-3220) oozie sharelib pig fails when compiled with hadoop 3

[Artem Ervits (JIRA)]

Artem Ervits created OOZIE-3220:
---

 Summary: oozie sharelib pig fails when compiled with hadoop 3
 Key: OOZIE-3220
 URL: https://issues.apache.org/jira/browse/OOZIE-3220
 Project: Oozie
  Issue Type: Bug
Affects Versions: 5.0.0
 Environment: Oozie 5.0 release
{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.21.1.el7.x86_64", arch: "amd64", family: 
"unix"{code}
Reporter: Artem Ervits
Assignee: Artem Ervits


{code:java}
mvn clean install -DskipTests -Dhadoop.version=3.1.0{code}
{code:java}
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java:[30,30]
 package org.apache.hadoop.conf does not exist
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java:[31,28]
 cannot find symbol
symbol: class Path
location: package org.apache.hadoop.fs
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/OoziePigStats.java:[142,37]
 cannot access org.apache.hadoop.io.Writable
class file for org.apache.hadoop.io.Writable not found
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java:[87,9]
 cannot find symbol
symbol: class Configuration
location: class org.apache.oozie.action.hadoop.PigMain
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java:[87,40]
 cannot find symbol
symbol: class Configuration
location: class org.apache.oozie.action.hadoop.PigMain
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java:[98,36]
 cannot find symbol
symbol: class Path
location: class org.apache.oozie.action.hadoop.PigMain
[INFO] 6 errors
[INFO] -
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Oozie Main 5.0.0  SUCCESS [ 5.637 s]
[INFO] Apache Oozie Client  SUCCESS [ 35.895 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 24.548 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [ 13.107 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 9.785 s]
[INFO] Apache Oozie Core .. SUCCESS [03:03 min]
[INFO] Apache Oozie Share Lib Streaming ... SUCCESS [ 14.031 s]
[INFO] Apache Oozie Share Lib Pig . FAILURE [ 18.706 s]
[INFO] Apache Oozie Share Lib Hive  SKIPPED
[INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
[INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
[INFO] Apache Oozie Examples .. SKIPPED
[INFO] Apache Oozie Share Lib Spark ... SKIPPED
[INFO] Apache Oozie Share Lib . SKIPPED
[INFO] Apache Oozie Docs .. SKIPPED
[INFO] Apache Oozie WebApp  SKIPPED
[INFO] Apache Oozie Tools . SKIPPED
[INFO] Apache Oozie MiniOozie . SKIPPED
[INFO] Apache Oozie Server  SKIPPED
[INFO] Apache Oozie Distro  SKIPPED
[INFO] Apache Oozie ZooKeeper Security Tests 5.0.0  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 05:07 min
[INFO] Finished at: 2018-04-13T16:03:09Z
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) 
on project oozie-sharelib-pig: Compilation failure: Compilation failure:
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java:[30,30]
 package org.apache.hadoop.conf does not exist
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/PigMain.java:[31,28]
 cannot find symbol
[ERROR] symbol: class Path
[ERROR] location: package org.apache.hadoop.fs
[ERROR] 
/tmp/oozie-5.0.0/sharelib/pig/src/main/java/org/apache/oozie/action/hadoop/OoziePigStats.java:[142,37]
 cannot access org.apache.hadoop.io.Writable
[ERROR] class file for

[jira] [Updated] (OOZIE-3219) oozie core fails when compiled with hadoop 3.x

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3219:

Attachment: OOZIE-3219.00.patch

> oozie core fails when compiled with hadoop 3.x
> --
>
> Key: OOZIE-3219
> URL: https://issues.apache.org/jira/browse/OOZIE-3219
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>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.21.1.el7.x86_64", arch: "amd64", 
> family: "unix"{code}
> latest 5.0 release bits
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-3219.00.patch
>
>
> command failure on the following, same happens with 3.0.0. Issue does not 
> appear with < 3.0
> {code:java}
> mvn clean install -DskipTests -Dhadoop.version=3.1.0{code}
> {code:java}
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR] 
> /tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[24,37]
>  package org.apache.directory.api.util does not exist
> [ERROR] 
> /tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[352,41]
>  cannot find symbol
> symbol: variable Strings
> location: class 
> org.apache.oozie.util.db.FailingConnectionWrapper.OozieDmlStatementPredicate
> [INFO] 2 errors
> [INFO] -
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main 5.0.0  SUCCESS [ 3.768 s]
> [INFO] Apache Oozie Client  SUCCESS [ 30.924 
> s]
> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 20.904 
> s]
> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [ 9.150 s]
> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 7.938 s]
> [INFO] Apache Oozie Core .. FAILURE [ 13.929 
> s]
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests 5.0.0  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 01:28 min
> [INFO] Finished at: 2018-04-13T14:03:17Z
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile 
> (default-compile) on project oozie-core: Compilation failure: Compilation 
> failure:
> [ERROR] 
> /tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[24,37]
>  package org.apache.directory.api.util does not exist
> [ERROR] 
> /tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[352,41]
>  cannot find symbol
> [ERROR] symbol: variable Strings
> [ERROR] location: class 
> org.apache.oozie.util.db.FailingConnectionWrapper.OozieDmlStatementPredicate
> [ERROR] 

[jira] [Created] (OOZIE-3219) oozie core fails when compiled with hadoop 3.x

[Artem Ervits (JIRA)]

Artem Ervits created OOZIE-3219:
---

 Summary: oozie core fails when compiled with hadoop 3.x
 Key: OOZIE-3219
 URL: https://issues.apache.org/jira/browse/OOZIE-3219
 Project: Oozie
  Issue Type: Bug
  Components: core
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.21.1.el7.x86_64", arch: "amd64", family: 
"unix"{code}
latest 5.0 release bits
Reporter: Artem Ervits
Assignee: Artem Ervits
 Fix For: 5.1.0


command failure on the following, same happens with 3.0.0. Issue does not 
appear with < 3.0
{code:java}
mvn clean install -DskipTests -Dhadoop.version=3.1.0{code}
{code:java}
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[24,37]
 package org.apache.directory.api.util does not exist
[ERROR] 
/tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[352,41]
 cannot find symbol
symbol: variable Strings
location: class 
org.apache.oozie.util.db.FailingConnectionWrapper.OozieDmlStatementPredicate
[INFO] 2 errors
[INFO] -
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Oozie Main 5.0.0  SUCCESS [ 3.768 s]
[INFO] Apache Oozie Client  SUCCESS [ 30.924 s]
[INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 20.904 s]
[INFO] Apache Oozie Share Lib HCatalog  SUCCESS [ 9.150 s]
[INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 7.938 s]
[INFO] Apache Oozie Core .. FAILURE [ 13.929 s]
[INFO] Apache Oozie Share Lib Streaming ... SKIPPED
[INFO] Apache Oozie Share Lib Pig . SKIPPED
[INFO] Apache Oozie Share Lib Hive  SKIPPED
[INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
[INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
[INFO] Apache Oozie Examples .. SKIPPED
[INFO] Apache Oozie Share Lib Spark ... SKIPPED
[INFO] Apache Oozie Share Lib . SKIPPED
[INFO] Apache Oozie Docs .. SKIPPED
[INFO] Apache Oozie WebApp  SKIPPED
[INFO] Apache Oozie Tools . SKIPPED
[INFO] Apache Oozie MiniOozie . SKIPPED
[INFO] Apache Oozie Server  SKIPPED
[INFO] Apache Oozie Distro  SKIPPED
[INFO] Apache Oozie ZooKeeper Security Tests 5.0.0  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:28 min
[INFO] Finished at: 2018-04-13T14:03:17Z
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) 
on project oozie-core: Compilation failure: Compilation failure:
[ERROR] 
/tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[24,37]
 package org.apache.directory.api.util does not exist
[ERROR] 
/tmp/oozie-5.0.0/core/src/main/java/org/apache/oozie/util/db/FailingConnectionWrapper.java:[352,41]
 cannot find symbol
[ERROR] symbol: variable Strings
[ERROR] location: class 
org.apache.oozie.util.db.FailingConnectionWrapper.OozieDmlStatementPredicate
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn  -rf :oozie-core{code}



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

Re: [ANNOUNCE] Apache Oozie 5.0.0 released

[Artem Ervits]

replying to dev list only

looks like binary release was not published. Is there a plan to release one
soon?

On Mon, Apr 9, 2018 at 1:26 PM, Robert Kanter  wrote:

> Yay!  This is a great milestone for Oozie!  Thanks everyone who worked on
> it.
>
> On Mon, Apr 9, 2018 at 8:01 AM, Andras Piros  wrote:
>
> > Hello Oozie community,
> >
> >
> > Apache Oozie is a workflow scheduler system to manage Apache Hadoop jobs.
> >
> >
> > The Apache Oozie team is pleased to announce the release of Oozie 5.0.0.
> >
> > Oozie 5.0.0 includes new features, bug fixes and minor improvements.
> >
> >
> > The details of the release and download location can be found at
> > http://oozie.apache.org.
> >
> >
> >
> > The full release notes can be found at the download location, but some
> > highlights of this release include:
> >
> >
> > - moved launcher from MapReduce AM to YARN AM,
> > - switched from Tomcat to embedded Jetty,
> > - updated third party libraries,
> > - completely rewritten workflow graph generator,
> > - JDK 8 support,
> > - deprecated Instrumentation in favor of Metrics,
> > - added indexes to speed up DB queries,
> > - fixed CVE-2017-15712
> >
> > Thanks to all developers, QA's, users, and committers for making this
> > release happen.
> >
> > Regards,
> >
> > Andras
> >
>

[jira] [Resolved] (OOZIE-3212) fix findbugs issues in oozie sharelib

[Artem Ervits (JIRA)]

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

Artem Ervits resolved OOZIE-3212.
-
Resolution: Duplicate

duplicate of https://issues.apache.org/jira/browse/OOZIE-2952

> fix findbugs issues in oozie sharelib 
> --
>
> Key: OOZIE-3212
> URL: https://issues.apache.org/jira/browse/OOZIE-3212
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>    Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Fix For: 5.1.0
>
>
> {code:java}
> [INFO] BugInstance size is 39
> [INFO] Error size is 0
> [INFO] Total bugs: 39
> [INFO] Unwritten public or protected field: 
> org.apache.oozie.action.hadoop.ActionStats.currentActionType 
> [org.apache.oozie.action.hadoop.ActionStats] At ActionStats.java:[line 37] 
> UWF_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD
> [INFO] Unchecked/unconfirmed cast from Throwable to 
> org.apache.oozie.action.hadoop.LauncherMainException of return value in 
> org.apache.oozie.action.hadoop.LauncherAM.runActionMain(ErrorHolder) 
> [org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 427] 
> BC_UNCONFIRMED_CAST_OF_RETURN_VALUE
> [INFO] java/io/File.(Ljava/lang/String;)V reads a file whose location 
> might be specified by user input [org.apache.oozie.action.hadoop.LauncherAM, 
> org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 522]At 
> LauncherAM.java:[line 514] PATH_TRAVERSAL_IN
> [INFO] Redundant nullcheck of id, which is known to be non-null in 
> org.apache.oozie.action.hadoop.LauncherAM.setRecoveryId() 
> [org.apache.oozie.action.hadoop.LauncherAM] Redundant null check at 
> LauncherAM.java:[line 481] RCN_REDUNDANT_NULLCHECK_OF_NONNULL_VALUE
> [INFO] Exception is caught when Exception is not thrown in 
> org.apache.oozie.action.hadoop.LauncherAM.executePrepare(ErrorHolder) 
> [org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 379] 
> REC_CATCH_EXCEPTION
> [INFO] Exception is caught when Exception is not thrown in 
> org.apache.oozie.action.hadoop.LauncherAM.run() 
> [org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 251] 
> REC_CATCH_EXCEPTION
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherAMUtils.getLocalFileContentStr(File, 
> String, int): new java.io.FileReader(File) 
> [org.apache.oozie.action.hadoop.LauncherAMUtils] At 
> LauncherAMUtils.java:[line 64] DM_DEFAULT_ENCODING
> [INFO] 
> org.apache.oozie.action.hadoop.LauncherAMUtils.getLocalFileContentStr(File, 
> String, int) may fail to clean up java.io.Reader on checked exception 
> [org.apache.oozie.action.hadoop.LauncherAMUtils, 
> org.apache.oozie.action.hadoop.LauncherAMUtils, 
> org.apache.oozie.action.hadoop.LauncherAMUtils, 
> org.apache.oozie.action.hadoop.LauncherAMUtils] Obligation to clean up 
> resource created at LauncherAMUtils.java:[line 64] is not dischargedPath 
> continues at LauncherAMUtils.java:[line 65]Path continues at 
> LauncherAMUtils.java:[line 67]Path continues at LauncherAMUtils.java:[line 
> 68] OBL_UNSATISFIED_OBLIGATION_EXCEPTION_EDGE
> [INFO] 
> org.apache.oozie.action.hadoop.LauncherAMUtils.getLocalFileContentStr(File, 
> String, int) may fail to close stream on exception 
> [org.apache.oozie.action.hadoop.LauncherAMUtils] At 
> LauncherAMUtils.java:[line 64] OS_OPEN_STREAM_EXCEPTION_PATH
> [INFO] Use of non-localized String.toUpperCase() or String.toLowerCase() in 
> org.apache.oozie.action.hadoop.LauncherMain.printArgs(String, String[]) 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 423] 
> DM_CONVERT_CASE
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMain.getHadoopJobIds(String, 
> Pattern[]): new java.io.FileReader(String) 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 144] 
> DM_DEFAULT_ENCODING
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMain.propagateToHadoopConf(): new 
> java.io.FileWriter(String) [org.apache.oozie.action.hadoop.LauncherMain] At 
> LauncherMain.java:[line 454] DM_DEFAULT_ENCODING
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMain.propagateToHadoopConf(): new 
> java.io.OutputStreamWriter(OutputStream) 
> [org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 458] 
> DM_DEFAULT_ENCODING
> [INFO] Found reliance on default encoding in 
> org.apache.oozie.action.hadoop.LauncherMain.writeExternalChildIDs(String, 
> Pat

[jira] [Created] (OOZIE-3212) fix findbugs issues in oozie sharelib

[Artem Ervits (JIRA)]

Artem Ervits created OOZIE-3212:
---

 Summary: fix findbugs issues in oozie sharelib 
 Key: OOZIE-3212
 URL: https://issues.apache.org/jira/browse/OOZIE-3212
 Project: Oozie
  Issue Type: Bug
Affects Versions: 5.0.0
Reporter: Artem Ervits
Assignee: Artem Ervits
 Fix For: 5.1.0


{code:java}
[INFO] BugInstance size is 39
[INFO] Error size is 0
[INFO] Total bugs: 39
[INFO] Unwritten public or protected field: 
org.apache.oozie.action.hadoop.ActionStats.currentActionType 
[org.apache.oozie.action.hadoop.ActionStats] At ActionStats.java:[line 37] 
UWF_UNWRITTEN_PUBLIC_OR_PROTECTED_FIELD
[INFO] Unchecked/unconfirmed cast from Throwable to 
org.apache.oozie.action.hadoop.LauncherMainException of return value in 
org.apache.oozie.action.hadoop.LauncherAM.runActionMain(ErrorHolder) 
[org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 427] 
BC_UNCONFIRMED_CAST_OF_RETURN_VALUE
[INFO] java/io/File.(Ljava/lang/String;)V reads a file whose location 
might be specified by user input [org.apache.oozie.action.hadoop.LauncherAM, 
org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 522]At 
LauncherAM.java:[line 514] PATH_TRAVERSAL_IN
[INFO] Redundant nullcheck of id, which is known to be non-null in 
org.apache.oozie.action.hadoop.LauncherAM.setRecoveryId() 
[org.apache.oozie.action.hadoop.LauncherAM] Redundant null check at 
LauncherAM.java:[line 481] RCN_REDUNDANT_NULLCHECK_OF_NONNULL_VALUE
[INFO] Exception is caught when Exception is not thrown in 
org.apache.oozie.action.hadoop.LauncherAM.executePrepare(ErrorHolder) 
[org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 379] 
REC_CATCH_EXCEPTION
[INFO] Exception is caught when Exception is not thrown in 
org.apache.oozie.action.hadoop.LauncherAM.run() 
[org.apache.oozie.action.hadoop.LauncherAM] At LauncherAM.java:[line 251] 
REC_CATCH_EXCEPTION
[INFO] Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherAMUtils.getLocalFileContentStr(File, 
String, int): new java.io.FileReader(File) 
[org.apache.oozie.action.hadoop.LauncherAMUtils] At LauncherAMUtils.java:[line 
64] DM_DEFAULT_ENCODING
[INFO] 
org.apache.oozie.action.hadoop.LauncherAMUtils.getLocalFileContentStr(File, 
String, int) may fail to clean up java.io.Reader on checked exception 
[org.apache.oozie.action.hadoop.LauncherAMUtils, 
org.apache.oozie.action.hadoop.LauncherAMUtils, 
org.apache.oozie.action.hadoop.LauncherAMUtils, 
org.apache.oozie.action.hadoop.LauncherAMUtils] Obligation to clean up resource 
created at LauncherAMUtils.java:[line 64] is not dischargedPath continues at 
LauncherAMUtils.java:[line 65]Path continues at LauncherAMUtils.java:[line 
67]Path continues at LauncherAMUtils.java:[line 68] 
OBL_UNSATISFIED_OBLIGATION_EXCEPTION_EDGE
[INFO] 
org.apache.oozie.action.hadoop.LauncherAMUtils.getLocalFileContentStr(File, 
String, int) may fail to close stream on exception 
[org.apache.oozie.action.hadoop.LauncherAMUtils] At LauncherAMUtils.java:[line 
64] OS_OPEN_STREAM_EXCEPTION_PATH
[INFO] Use of non-localized String.toUpperCase() or String.toLowerCase() in 
org.apache.oozie.action.hadoop.LauncherMain.printArgs(String, String[]) 
[org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 423] 
DM_CONVERT_CASE
[INFO] Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMain.getHadoopJobIds(String, Pattern[]): 
new java.io.FileReader(String) [org.apache.oozie.action.hadoop.LauncherMain] At 
LauncherMain.java:[line 144] DM_DEFAULT_ENCODING
[INFO] Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMain.propagateToHadoopConf(): new 
java.io.FileWriter(String) [org.apache.oozie.action.hadoop.LauncherMain] At 
LauncherMain.java:[line 454] DM_DEFAULT_ENCODING
[INFO] Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMain.propagateToHadoopConf(): new 
java.io.OutputStreamWriter(OutputStream) 
[org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 458] 
DM_DEFAULT_ENCODING
[INFO] Found reliance on default encoding in 
org.apache.oozie.action.hadoop.LauncherMain.writeExternalChildIDs(String, 
Pattern[], String): String.getBytes() 
[org.apache.oozie.action.hadoop.LauncherMain] At LauncherMain.java:[line 180] 
DM_DEFAULT_ENCODING
[INFO] org.apache.oozie.action.hadoop.LauncherMain.HADOOP_SITE_FILES should be 
both final and package protected [org.apache.oozie.action.hadoop.LauncherMain] 
At LauncherMain.java:[line 80] MS_FINAL_PKGPROTECT
[INFO] java/io/File.(Ljava/lang/String;)V reads a file whose location 
might be specified by user input [org.apache.oozie.action.hadoop.LauncherMain] 
At LauncherMain.java:[line 473] PATH_TRAVERSAL_IN
[INFO] java/io/File.(Ljava/lang/String;)V reads a file whose location 
might be specified by user input [org.apache.oozie.action.hadoop.LauncherMain

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

[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 <pbac...@cloudera.com> 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 <kmar...@cloudera.com>
> 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
> > <https://issues.apache.org/jira/browse/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 <rkan...@apache.org>
> > 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 <artemerv...@gmail.com
> >
> > > > 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 <rkan...@apache.org>
> > > 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 <https://issues.apache.org/jira/browse/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 <https://issues.apache.org/jira/browse/OOZIE-3207>:
> > > We're
> > > > > > using version 17 of the ASF root pom, and the latest is 19.
> > version
> > > 17
> > > > > is
> > > > > > from 2015!
> > > > > > - OOZIE-3208 <https://issues.apache.org/jira/browse/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

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

[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

[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

[Artem Ervits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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

[Artem Ervits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[Artem Ervits]

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 <rkan...@apache.org> 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 <https://issues.apache.org/jira/browse/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 <https://issues.apache.org/jira/browse/OOZIE-3207>: We're
> using version 17 of the ASF root pom, and the latest is 19.  version 17 is
> from 2015!
> - OOZIE-3208 <https://issues.apache.org/jira/browse/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
> > > [INFO] Apache Oozie Examples .. SKIPPED
> > > [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> > > [INFO] Apache Oozie Share Lib . SKIPPED
> > > [INFO] Apache Oozie Docs .. SKIPPED
> > > [INFO] Apache Oozie WebApp  SKIPPED
> > > [INFO] Apache Oozie Tools . SKIPPED
> > > [INFO] Apache Oozie MiniOozie . SKIPPED
> > > [INFO] Apache Oozie Server  SKIPPED
> > > [INFO] Apache Oozie Distro  SKIPPED
> > > [INFO] Apache Oozie ZooKeeper Security Tests 5.0.0  SKIPPED
> > > [INFO]
> > >
> 
> > > [INFO] BUILD FAILURE
> > > [INFO]
> > >

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

[Artem Ervits]

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
[INFO] Apache Oozie Examples .. SKIPPED
[INFO] Apache Oozie Share Lib Spark ... SKIPPED
[INFO] Apache Oozie Share Lib . SKIPPED
[INFO] Apache Oozie Docs .. SKIPPED
[INFO] Apache Oozie WebApp  SKIPPED
[INFO] Apache Oozie Tools . SKIPPED
[INFO] Apache Oozie MiniOozie . SKIPPED
[INFO] Apache Oozie Server  SKIPPED
[INFO] Apache Oozie Distro  SKIPPED
[INFO] Apache Oozie ZooKeeper Security Tests 5.0.0  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 01:32 h
[INFO] Finished at: 2018-03-28T14:21:30Z
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test)
on project oozie-core: There was a timeout or other error in the fork ->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :oozie-core

On Wed, Mar 28, 2018 at 8:50 AM, Artem Ervits <artemerv...@gmail.com> wrote:

> +1 non-binding
>
> signatures and checksum: OK
> build with Hadoop 2.7.5: OK
> install on a single-node pseudo-distributed cluster: OK
> ran no-op workflow: OK
>
> the directions to install sharelib on 5.0 are unclear and I'm not able to
> execute other workflows due to share lib problems. (not a blocker in my
> opinion).
>
> Thank you
>
> On Tue, Mar 27, 2018 at 8:39 AM, Andras Piros <and...@apache.org> wrote:
>
>> Hi there,
>>
>> I have created a build for Oozie 5.0.0, release candidate 0.
>>
>> This release introduces major changes:
>> - moved launcher from MapReduce AM to YARN AM,
>> - switched from Tomcat to embedded Jetty,
>> - updated third party libraries,
>> - completely rewritten workflow graph generator,
>> - JDK 8 support,
>> - deprecated Instrumentation in favor of Metrics,
>> - added indexes to speed up DB queries,
>> - fixed CVE-2017-15712
>>
>> Keys to verify the signature of the release artifact are available at
>>
>>  http://www.apache.org/dist/oozie/KEYS
>>
>> Please download, test, and try it out:
>>
>> http://people.apache.org/~andras/oozie-5.0.0-rc0/
>>
>> The release candidate, sha512 signature, gpg signature, and rat report can
>> all be found
>> at the above address.
>>
>> The vote is open until Saturday, March 31, 2018 at 12:00am PDT.
>>
>> Thanks,
>>
>> Andras Piros
>>
>
>

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

[Artem Ervits]

+1 non-binding

signatures and checksum: OK
build with Hadoop 2.7.5: OK
install on a single-node pseudo-distributed cluster: OK
ran no-op workflow: OK

the directions to install sharelib on 5.0 are unclear and I'm not able to
execute other workflows due to share lib problems. (not a blocker in my
opinion).

Thank you

On Tue, Mar 27, 2018 at 8:39 AM, Andras Piros  wrote:

> Hi there,
>
> I have created a build for Oozie 5.0.0, release candidate 0.
>
> This release introduces major changes:
> - moved launcher from MapReduce AM to YARN AM,
> - switched from Tomcat to embedded Jetty,
> - updated third party libraries,
> - completely rewritten workflow graph generator,
> - JDK 8 support,
> - deprecated Instrumentation in favor of Metrics,
> - added indexes to speed up DB queries,
> - fixed CVE-2017-15712
>
> Keys to verify the signature of the release artifact are available at
>
>  http://www.apache.org/dist/oozie/KEYS
>
> Please download, test, and try it out:
>
> http://people.apache.org/~andras/oozie-5.0.0-rc0/
>
> The release candidate, sha512 signature, gpg signature, and rat report can
> all be found
> at the above address.
>
> The vote is open until Saturday, March 31, 2018 at 12:00am PDT.
>
> Thanks,
>
> Andras Piros
>

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

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3196:
-

I heard from another client who's only concerned with who submitted the job and 
when etc,  as underlining actions are already governed by their respective 
authorization mechanisms, in their case Ranger.

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

[DISCUSS] Wondering why 5.0 beta not using fluido skin

[Artem Ervits]

If you look at
https://oozie.apache.org/docs/5.0.0-beta1/DG_SparkActionExtension.html

I'd have the old look and feel, I know there was a Jira to switch to Fluido
skin that made things pop, see difference on main page

https://oozie.apache.org/

Even worse it works with 4.3.0 but now with 5.0, does this Jira need to be
applied to Branch 5.x and master?

https://issues.apache.org/jira/plugins/servlet/mobile#issue/OOZIE-3163

[jira] [Commented] (OOZIE-2339) Provide an API for writing jobs based on the XSD schemas

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-2339:
-

how about "workflow as code"?

> Provide an API for writing jobs based on the XSD schemas
> 
>
> Key: OOZIE-2339
> URL: https://issues.apache.org/jira/browse/OOZIE-2339
> Project: Oozie
>  Issue Type: New Feature
>  Components: client
>Affects Versions: 4.3.0
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.1.0
>
> Attachments: OOZIE-2339.001.patch, OOZIE-2339.002.patch, 
> OOZIE-2339.003.patch, OOZIE-2339.004.patch, OOZIE-2339.005.patch, 
> OOZIE-2339.006.patch, OOZIE-2339.008.patch, OOZIE-2339.010.patch, 
> OOZIE-2339.011.patch
>
>
> Users often complain about the XML they have to write for Oozie jobs.  It 
> would be nice if they could write them in something like Java, but we don't 
> want to have to maintain a separate Java API for this.  I was looking around 
> and saw that JAXB might be the right thing here.  From what I can tell, it 
> lets you create Java classes from XSD schemas.  So, we should be able to 
> auto-generate a Java API for writing Oozie jobs, without having to really 
> maintain it.
> We should investigate if this is feasible and, if so, implement it.
> Some useful looking links:
> * [JAXB 
> overview|https://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding]
> * [JAXB description|https://jaxb.java.net/2.2.11/docs/ch03.html]
> * [Maven JAXB plugin|https://java.net/projects/maven-jaxb2-plugin/pages/Home]
> * [Apache Falcon|https://falcon.apache.org]
> Key features:
> * must have:
> ** inside an {{oozie-jobs-api}} artifact
> ** able to create workflow / coordinator / bundle definitions programmatically
> ** synchronizing each and every XSD change on rebuild
> ** can write {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and 
> {{jobs.properties}} artifacts of every XSD version
> ** cloneability of workflow etc. {{Object}} s
> ** perform cross checks, e.g. that the workflow graph is a DAG
> ** only latest XSD versions should be supported as must have
> * nice to have:
> ** XSD version(s) can be provided. When not provided, latest ones are 
> considered as valid
> ** implement a [*fluent API*|https://en.wikipedia.org/wiki/Fluent_interface]
> ** have a Python / Jython REPL to make it easy to experiment
> ** create documentation about usage
> ** can read {{workflow.xml}}, {{coordinator.xml}}, {{bundle.xml}}, and 
> {{jobs.properties}} artifacts of every XSD version
> ** can convert between XSD versions
> ** support XSD change on the fly (within REPL)
> ** support HDFS reads / writes
> ** support dry run on an Oozie server to perform checks



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

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

[Artem Ervits (JIRA)]

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

Artem Ervits edited comment on OOZIE-3196 at 3/20/18 4:32 PM:
--

this is a wonderful idea, at the minimum, implementation should be internal to 
Oozie not (Sentry, Ranger) specific. There should be a property file with Oozie 
authorizations and provide an interface for external projects to tap into.

Do we want this for per workflow, per coordinator, per bundle, per action?

feedback I got from customers is that they want jobs to be more private, 
prevent user from seeing a workflow, see job.properties (passwords), job logs, 
etc.


was (Author: dbist13):
this is a wonderful idea, at the minimum, implementation should be internal to 
Oozie not (Sentry, Ranger) specific. There should be a property file with Oozie 
authorizations and provide an interface for external projects to tap into.

Do we want this for per workflow, per coordinator, per bundle, per action?

feedback I got from customers is that they want jobs to be more private, 
prevent user from seeing a workflow, see job.properties (passwords).

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

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3196:
-

this is a wonderful idea, at the minimum, implementation should be internal to 
Oozie not (Sentry, Ranger) specific. There should be a property file with Oozie 
authorizations and provide an interface for external projects to tap into.

Do we want this for per workflow, per coordinator, per bundle, per action?

feedback I got from customers is that they want jobs to be more private, 
prevent user from seeing a workflow, see job.properties (passwords).

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

DWS abstract

[Artem Ervits]

Oozie team,

Clay from Bloomberg and I will be speaking at Dataworks Summit Berlin in
April and I'd like to highlight all of the cool things going into 5.0
release as part of the talk. I have a list in mind but would like to get
your take on this and point out anything I've missed?

New doc skin
New schemas
New launcher
DSL for WF
Futures?

Have we established goals for 6.x and later releases? What's the future
like for Oozie?

Thank you

Re: [VOTE][RESULT] Oozie 4.3.1(candidate 4)

[Artem Ervits]

it's late but seems I'm hitting the following jira on 4.3.1
https://issues.apache.org/jira/browse/OOZIE-1213, I see the fix in master
but in 4.3 branch clover.version is missing.

https://github.com/apache/oozie/blob/branch-4.3/pom.xml#L1687-#L1700



On Tue, Feb 13, 2018 at 7:57 AM, Gézapeti  wrote:

> Hi,
>
> Oozie 4.3.1 RC4 has passed the vote.
>
> The vote tally is:
> +1 --> 3 votes from Oozie PMC members (binding), 1 vote from
> Contributors (non-binding)
> -1 --> 0
> 0 --> 0
>
>
> On Tue, Feb 6, 2018 at 1:42 PM, Gézapeti Cseh  wrote:
> > Hi,
> >
> > I have created a build for Oozie 4.3.1, candidate 4.
> >
> > It includes all the changes in rc3 plus OOZIE-2888 to fix sharelib
> > creation with Hadoop 2.7.5. and possibly other newer versions.
> >
> > Keys to verify the signature of the release artifact are available at
> >   http://www.apache.org/dist/oozie/KEYS
> >
> > Please download, test, and try it out:
> >
> > http://people.apache.org/~gezapeti/oozie-4.3.1-rc4/
> >
> > The release, md5 signature, gpg signature, and rat report can be found at
> > the above address.
> >
> > Vote closes on 02/12/2018 11:59 PM CET.
>

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

[Artem Ervits]

Attila, AFAIK, these properties are in my core-site.xml except for last
one, mapreduce.framework.name is in mapred-site.xml. I'll have to double
check on the proxyuser.root.hosts as I believe my service runs with user
oozie not root and get back to you.

On Tue, Feb 6, 2018 at 3:49 PM, Attila Sasvari <asasv...@cloudera.com>
wrote:

> +1 (binding)
>
> - Verified MD5 hash, signature, rat_report, release log are OK
> - Built Oozie against Hadoop 2.7.5 (did not build against other Hadoop
> versions this time)
> - Installed Oozie sharelib
> - Some example workflows I submitted to a 1-node Hadoop 2.7.5 (running in
> pseudo distributed mode for tests) succeeded: ( aggregator bundle
> coord-input-logic cron cron-schedule custom-main datelist-java-main demo
> distcp hadoop-el hcatalog java-main map-reduce no-op pig shell sla sqoop
> sqoop-freeform ssh streaming subwf )
> - Verified basic functionality of the Web UI (version, Job DAG, Job logs)
>
>
> Artem, have you specified conf/hadoop-conf/core-site.xml with all the
> details Oozie needs to communicate with a Hadoop cluster?
>
> In my local environment, I use a pseudo Hadoop 2.7.5. My
> conf/hadoop-conf/core-site.xml is as follows:
> 
> 
> 
> 
> 
>   
> fs.defaultFS
> hdfs://localhost:9000
>   
>   
> hadoop.proxyuser.root.hosts
> *
>   
>   
> hadoop.proxyuser.root.groups
> *
>   
> 
> mapreduce.framework.name
> yarn
> 
> 
>
>
> On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits <artemerv...@gmail.com>
> wrote:
>
> > jdk: 1.8.0_161
> > hadoop: 2.7.5
> > md5: OK
> > curl http://localhost:11000/oozie/v1/admin/status
> > {"systemMode":"NORMAL"}
> >
> > curl http://localhost:11000/oozie/v2/admin/status
> > {"systemMode":"NORMAL"}
> >
> >
> > I also got in oozie-ops.log
> >
> >   STARTUP MSG: Oozie BUILD_VERSION [4.3.1] compiled by [oozie] on
> > [2018.02.06-16:30:43GMT]
> >   STARTUP MSG:   revision [unavailable]@[unavailable]
> >
> > so perhaps we may want to add but not critical OOZIE-2004, OOZIE-3083,
> > OOZIE-3152.
> >
> >  submitted a job and got but that is most likely my environment.
> Otherwise
> > +1
> >
> > 2018-02-06 18:09:37,635  WARN ActionStartXCommand:523 - SERVER[
> > hadoop.example.com] USER[vagrant] GROUP[-] TOKEN[] APP[python-wf]
> > JOB[000-180206180622504-oozie-oozi-W]
> > ACTION[000-180206180622504-oozie-oozi-W@python-node] Error starting
> > action [python-node]. ErrorType [ERROR], ErrorCode
> > [UnsupportedOperationException], Message [UnsupportedOperationException:
> > Accessing local file system is not allowed]
> > org.apache.oozie.action.ActionExecutorException:
> > UnsupportedOperationException: Accessing local file system is not allowed
> > at
> > org.apache.oozie.action.ActionExecutor.convertException(Acti
> > onExecutor.java:446)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.submitLaun
> > cher(JavaActionExecutor.java:1204)
> > at
> > org.apache.oozie.action.hadoop.JavaActionExecutor.start(Java
> > ActionExecutor.java:1386)
> > at
> > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > onStartXCommand.java:234)
> > at
> > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > onStartXCommand.java:65)
> > at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> > at
> > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > ble.call(CallableQueueService.java:332)
> > at
> > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > ble.call(CallableQueueService.java:261)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > at
> > org.apache.oozie.service.CallableQueueService$CallableWrappe
> > r.run(CallableQueueService.java:179)
> > at
> > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> > Executor.java:1149)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> > lExecutor.java:624)
> > at java.lang.Thread.run(Thread.java:748)
> > Caused by: java.lang.UnsupportedOperationException: Accessing local file
> > system is not allowed
> > at
> > org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalF
> > ileSystem.java:48)
> > at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSys
> > tem.java:47)
> > at org.apache.hadoop.fs.FileSystem.createFileSystem(
> FileSystem.java:2667)
> > at org.a

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

[Artem Ervits]

jdk: 1.8.0_161
hadoop: 2.7.5
md5: OK
curl http://localhost:11000/oozie/v1/admin/status
{"systemMode":"NORMAL"}

curl http://localhost:11000/oozie/v2/admin/status
{"systemMode":"NORMAL"}


I also got in oozie-ops.log

  STARTUP MSG: Oozie BUILD_VERSION [4.3.1] compiled by [oozie] on
[2018.02.06-16:30:43GMT]
  STARTUP MSG:   revision [unavailable]@[unavailable]

so perhaps we may want to add but not critical OOZIE-2004, OOZIE-3083,
OOZIE-3152.

 submitted a job and got but that is most likely my environment. Otherwise
+1

2018-02-06 18:09:37,635  WARN ActionStartXCommand:523 - SERVER[
hadoop.example.com] USER[vagrant] GROUP[-] TOKEN[] APP[python-wf]
JOB[000-180206180622504-oozie-oozi-W]
ACTION[000-180206180622504-oozie-oozi-W@python-node] Error starting
action [python-node]. ErrorType [ERROR], ErrorCode
[UnsupportedOperationException], Message [UnsupportedOperationException:
Accessing local file system is not allowed]
org.apache.oozie.action.ActionExecutorException:
UnsupportedOperationException: Accessing local file system is not allowed
at
org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:446)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1204)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1386)
at
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
at
org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
at org.apache.oozie.command.XCommand.call(XCommand.java:287)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:332)
at
org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:261)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:179)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.UnsupportedOperationException: Accessing local file
system is not allowed
at
org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2667)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:93)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2701)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2683)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:372)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:171)
at
org.apache.oozie.service.ShareLibService.updateShareLib(ShareLibService.java:554)
at
org.apache.oozie.service.ShareLibService.getShareLibJars(ShareLibService.java:366)
at
org.apache.oozie.service.ShareLibService.getSystemLibJars(ShareLibService.java:432)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.addSystemShareLibForAction(JavaActionExecutor.java:756)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.addAllShareLibs(JavaActionExecutor.java:853)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.setLibFilesArchives(JavaActionExecutor.java:844)
at
org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1095)
... 11 more
2018-02-06 18:09:37,661  WARN ActionStartXCommand:523 - SERVER[
hadoop.example.com] USER[vagrant] GROUP[-] TOKEN[] APP[python-wf]
JOB[000-180206180622504-oozie-oozi-W]
ACTION[000-180206180622504-oozie-oozi-W@python-node] Setting Action
Status to [DONE]



On Tue, Feb 6, 2018 at 7:42 AM, Gézapeti Cseh  wrote:

> Hi,
>
> I have created a build for Oozie 4.3.1, candidate 4.
>
> It includes all the changes in rc3 plus OOZIE-2888 to fix sharelib
> creation with Hadoop 2.7.5. and possibly other newer versions.
>
> Keys to verify the signature of the release artifact are available at
>   http://www.apache.org/dist/oozie/KEYS
>
> Please download, test, and try it out:
>
> http://people.apache.org/~gezapeti/oozie-4.3.1-rc4/
>
> The release, md5 signature, gpg signature, and rat report can be found at
> the above address.
>
> Vote closes on 02/12/2018 11:59 PM CET.
>

[jira] [Commented] (OOZIE-3120) maven-assembly-plugin fails when bumped from 2.2.1

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3120:
-

[~gezapeti] hope I could get some insights from you, I started looking at this 
and this involves a lot of surgery. I see we have an empty.xml descriptor in 
the parent pom which is not sufficient for assembly plugin to work in versions 
> 2.2.1. I got it to work somewhat with example here 
[https://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-source-inclusion-simple.html]
 but it failed on sharelib. I think this will involve a lot of conversation. 
Could use your advice.

> maven-assembly-plugin fails when bumped from 2.2.1
> --
>
> Key: OOZIE-3120
> URL: https://issues.apache.org/jira/browse/OOZIE-3120
> Project: Oozie
>  Issue Type: Task
>Affects Versions: 4.3.0
>Reporter: Artem Ervits
>    Assignee: Artem Ervits
>Priority: Major
>
> maven-assembly plugin 3.1.0 is available, version 2.2.1 is old, with upgrade 
> to even 2.2.2 build fails with
> {noformat}
> [INFO] --- maven-assembly-plugin:3.1.0:single (default-cli) @ oozie-main ---
> [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Oozie Main .. FAILURE [  0.972 
> s]
> [INFO] Apache Oozie Client  SKIPPED
> [INFO] Apache Oozie Share Lib Oozie ... SKIPPED
> [INFO] Apache Oozie Share Lib HCatalog  SKIPPED
> [INFO] Apache Oozie Share Lib Distcp .. SKIPPED
> [INFO] Apache Oozie Core .. SKIPPED
> [INFO] Apache Oozie Share Lib Streaming ... SKIPPED
> [INFO] Apache Oozie Share Lib Pig . SKIPPED
> [INFO] Apache Oozie Share Lib Hive  SKIPPED
> [INFO] Apache Oozie Share Lib Hive 2 .. SKIPPED
> [INFO] Apache Oozie Share Lib Sqoop ... SKIPPED
> [INFO] Apache Oozie Examples .. SKIPPED
> [INFO] Apache Oozie Share Lib Spark ... SKIPPED
> [INFO] Apache Oozie Share Lib . SKIPPED
> [INFO] Apache Oozie Docs .. SKIPPED
> [INFO] Apache Oozie WebApp  SKIPPED
> [INFO] Apache Oozie Tools . SKIPPED
> [INFO] Apache Oozie MiniOozie . SKIPPED
> [INFO] Apache Oozie Server  SKIPPED
> [INFO] Apache Oozie Distro  SKIPPED
> [INFO] Apache Oozie ZooKeeper Security Tests .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.872 s
> [INFO] Finished at: 2017-11-10T13:38:17-05:00
> [INFO] Final Memory: 31M/437M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (default-cli) on 
> project oozie-main: No formats specified in the execution parameters or the 
> assembly descriptor. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> ERROR, Oozie distro creation failed
> {noformat}



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

[jira] [Commented] (OOZIE-3121) bump all maven plugins to latest versions

[Artem Ervits (JIRA)]

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

Artem Ervits commented on OOZIE-3121:
-

[~gezapeti] rebased the patch and added newer versions to a couple of artifacts.

> bump all maven plugins to latest versions
> -
>
> Key: OOZIE-3121
> URL: https://issues.apache.org/jira/browse/OOZIE-3121
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>    Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3121-02.patch, OOZIE-3121.patch
>
>
> bump all maven plugins to latest



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

[jira] [Updated] (OOZIE-3121) bump all maven plugins to latest versions

[Artem Ervits (JIRA)]

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

Artem Ervits updated OOZIE-3121:

Attachment: OOZIE-3121-02.patch

> bump all maven plugins to latest versions
> -
>
> Key: OOZIE-3121
> URL: https://issues.apache.org/jira/browse/OOZIE-3121
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: 4.3.0
>    Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3121-02.patch, OOZIE-3121.patch
>
>
> bump all maven plugins to latest



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

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

[Artem Ervits]

That was my pet peeve for a long time, it'd be a welcome change to replace
jobTracker nomenclature.

On Jan 31, 2018 4:05 PM, "Robert Kanter (JIRA)"  wrote:

>
> [ https://issues.apache.org/jira/browse/OOZIE-2814?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel=16347605#comment-16347605 ]
>
> Robert Kanter commented on OOZIE-2814:
> --
>
> I think we should also update {{}} to {{}}
> to encourage users to start using it.
>
> > OYA: Update example workflows to newest schemas
> > ---
> >
> > Key: OOZIE-2814
> > URL: https://issues.apache.org/jira/browse/OOZIE-2814
> > Project: Oozie
> >  Issue Type: Sub-task
> >Affects Versions: 5.0.0
> >Reporter: Robert Kanter
> >Assignee: Attila Sasvari
> >Priority: Blocker
> > Attachments: OOZIE-2814-00.patch
> >
> >
> > OOZIE-2687 will add in a whole set of newer schemas that are more
> Yarn-centric.  Most, if not all, examples currently use pretty old versions
> of the schemas.  We should take this opportunity to update the examples to
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> > It may make sense to keep the older schemas too, to show that older
> workflows still work.  We have some examples where we have two workflow XML
> files that do the same thing in different ways.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>