[jira] [Created] (OOZIE-2022) TestConnection check in Argus Admin portal fails in Kerberos environment for all the repositories

Ramesh Mani created OOZIE-2022: -- Summary: TestConnection check in Argus Admin portal fails in Kerberos environment for all the repositories Key: OOZIE-2022 URL: https://issues.apache.org/jira/browse/OOZIE-2022

[jira] [Resolved] (OOZIE-2022) TestConnection check in Argus Admin portal fails in Kerberos environment for all the repositories

[ https://issues.apache.org/jira/browse/OOZIE-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani resolved OOZIE-2022. Resolution: Fixed Wrongly created this issue in Oozie project. So need to be canceled

Re: Java 7

+1 Mona Chitnis On Tuesday, September 23, 2014 6:21 PM, Rohini Palaniswamy rohini.adi...@gmail.com wrote: +1 to drop support for Java 6 from Oozie trunk. I am just closing a vote on that for Pig now.  From Hadoop 2.7, hadoop is planning to publish maven artifacts in jdk1.7. So it

[jira] [Commented] (OOZIE-2017) On startup, StatusTransitService can transition Coordinators that were in PREPSUSPENDED to RUNNING

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

Jenkins build is back to normal : oozie-trunk-precommit-build #2008

See https://builds.apache.org/job/oozie-trunk-precommit-build/2008/changes

[jira] [Updated] (OOZIE-1940) StatusTransitService has race condition

[ https://issues.apache.org/jira/browse/OOZIE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Purshotam Shah updated OOZIE-1940: -- Attachment: OOZIE-1940-V8.patch StatusTransitService has race condition

[jira] [Commented] (OOZIE-1940) StatusTransitService has race condition

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

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

See https://builds.apache.org/job/oozie-trunk-precommit-build/2009/ -- [...truncated 10148 lines...] [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share

Re: Problem with coord:current?

Oh, I see now. Wow, some of these things can get quite tricky and subtle. I'm glad we didn't have such a scary flaw here :) thanks - Robert On Tue, Sep 23, 2014 at 10:11 PM, Shwetha GS shwetha...@inmobi.com wrote: The ds initial instance is 2013-01-01T00:01Z(Note 1st minute of hour). So,

[jira] [Commented] (OOZIE-2001) Workflow re-runs doesn't update coord action status

[ https://issues.apache.org/jira/browse/OOZIE-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152802#comment-14152802 ] Shwetha G S commented on OOZIE-2001: [~puru]/[~rohini], any idea why the condition

Build failed in Jenkins: oozie-trunk-find-patches-available #75918

See https://builds.apache.org/job/oozie-trunk-find-patches-available/75918/ -- Started by timer Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace https://builds.apache.org/job/oozie-trunk-find-patches-available/ws/ git rev-parse

Jenkins build is back to normal : oozie-trunk-find-patches-available #75919

See https://builds.apache.org/job/oozie-trunk-find-patches-available/75919/

[jira] [Updated] (OOZIE-1391) Sub wf suspend doesn't update parent wf

[ https://issues.apache.org/jira/browse/OOZIE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeep Vishwakarma updated OOZIE-1391: --- Attachment: OOZIE-1391-1.patch changes done as according to review feedback. Sub wf