[jira] Subscription: Oozie Patch Available

Issue Subscription Filter: Oozie Patch Available (44 issues) Subscriber: ooziedaily Key Summary OOZIE-2065 Oozie returns incorrect total action for coord dryrun https://issues.apache.org/jira/browse/OOZIE-2065 OOZIE-2060 Incorrect documentation of Java action config XML file

[jira] [Commented] (OOZIE-1983) Add spark action executor

[ https://issues.apache.org/jira/browse/OOZIE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215710#comment-14215710 ] pavan kumar kolamuri commented on OOZIE-1983: - [~rkanter] Can you please revi

Re: VOTE Release Oozie 4.1.0 (candidate 1)

+1 - downloaded release artifacts - built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a few of the examples. - built with Hadoop 2.3.0 (though ran against Hadoop some 2.7.0-SNAPSHOT) and ran a few of the examples. There's something wrong with my Hadoop 2 setup, but as far as I cou

Re: VOTE Release Oozie 4.1.0 (candidate 1)

Sorry Bowen for the delay.I'm looking into this , I never tried that. Regards,Mohammad On Monday, November 17, 2014 9:58 AM, bowen zhang wrote: Hi Mohammad,I think the KEY issue is the reason Mona has problem signing the page since I cannot commit my key to the repo. Can you resolve

Re: VOTE Release Oozie 4.1.0 (candidate 1)

Hi Mohammad,I think the KEY issue is the reason Mona has problem signing the page since I cannot commit my key to the repo. Can you resolve this ASAP?Thanks,Bowen From: Mona Chitnis To: "dev@oozie.apache.org" ; bowen zhang Sent: Monday, November 17, 2014 9:15 AM Subject: Re: VOTE Re

Re: VOTE Release Oozie 4.1.0 (candidate 1)

Downloaded the tarball, built and installed Oozie (-DskipTests) and ran an example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that. Was unable to verify the md5 and gpg signatures. I dont find the key used for signing the page in the list of public keys on the KEYS page. Please let me k

Re: VOTE Release Oozie 4.1.0 (candidate 1)

+1 On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang < bowenzhang...@yahoo.com.invalid> wrote: > Hi, > > I have created a build for Oozie 4.1.0, candidate 1. > > Keys to verify the signature of the release artifact are available at > > http://www.apache.org/dist/oozie/KEYS > > Please download, test,

[jira] [Created] (OOZIE-2067) Shell Actions should set HADOOP_USER_NAME on unsecured clusters

James Grant created OOZIE-2067: -- Summary: Shell Actions should set HADOOP_USER_NAME on unsecured clusters Key: OOZIE-2067 URL: https://issues.apache.org/jira/browse/OOZIE-2067 Project: Oozie Is

[jira] [Updated] (OOZIE-2066) oozie.launcher.mapreduce.task.classpath.user.precedence is not respected

[ https://issues.apache.org/jira/browse/OOZIE-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Robertson updated OOZIE-2066: - Description: When using MR2, the user classpath precedence is not read from the job configuration

[jira] [Updated] (OOZIE-2066) oozie.launcher.mapreduce.task.classpath.user.precedence is not respected

[ https://issues.apache.org/jira/browse/OOZIE-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Robertson updated OOZIE-2066: - Attachment: test-wf.zip In the example attached, a simple Java action uses a Guava method that req

[jira] [Updated] (OOZIE-2066) oozie.launcher.mapreduce.task.classpath.user.precedence is not respected

[ https://issues.apache.org/jira/browse/OOZIE-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Robertson updated OOZIE-2066: - Description: When using MR2, the user classpath is not read from the job configuration. When subm

[jira] [Created] (OOZIE-2066) oozie.launcher.mapreduce.task.classpath.user.precedence is not respected

Tim Robertson created OOZIE-2066: Summary: oozie.launcher.mapreduce.task.classpath.user.precedence is not respected Key: OOZIE-2066 URL: https://issues.apache.org/jira/browse/OOZIE-2066 Project: Oozie

[jira] [Commented] (OOZIE-2029) Workflow re-run with RERUN_FAIL_NODES=true should re-run only the failed nodes of the sub-workflow

[ https://issues.apache.org/jira/browse/OOZIE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214663#comment-14214663 ] Jaydeep Vishwakarma commented on OOZIE-2029: Test cases are already failing in

Build failed in Jenkins: oozie-trunk-precommit-build #2095

See Changes: [purushah] OOZIE-2064 coord job with frequency coord:endOfMonths doesn't materialize -- [...truncated 10880 lines...] [INFO] --- maven-surefire-plugin:2.12.2:test (defau

[jira] [Commented] (OOZIE-2029) Workflow re-run with RERUN_FAIL_NODES=true should re-run only the failed nodes of the sub-workflow

[ https://issues.apache.org/jira/browse/OOZIE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214551#comment-14214551 ] Hadoop QA commented on OOZIE-2029: -- Testing JIRA OOZIE-2029 Cleaning local git workspace

[jira] [Updated] (OOZIE-2029) Workflow re-run with RERUN_FAIL_NODES=true should re-run only the failed nodes of the sub-workflow

[ https://issues.apache.org/jira/browse/OOZIE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeep Vishwakarma updated OOZIE-2029: --- Attachment: OOZIE-2029-v0.patch > Workflow re-run with RERUN_FAIL_NODES=true should re