[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-V6.patch > StatusTransitService has race condition >

[jira] [Commented] (OOZIE-1876) use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc

[ https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138528#comment-14138528 ] Shwetha G S commented on OOZIE-1876: thats failed as well. Started https://builds.apa

[jira] [Commented] (OOZIE-1977) Display patch analysis issues

[ https://issues.apache.org/jira/browse/OOZIE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138521#comment-14138521 ] Shwetha G S commented on OOZIE-1977: Because of jira formatting. The output in the jen

[jira] [Updated] (OOZIE-2012) coordinator with an invalid cron frequency throws NPE after validation

[ https://issues.apache.org/jira/browse/OOZIE-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bowen Zhang updated OOZIE-2012: --- Attachment: oozie-2012.patch > coordinator with an invalid cron frequency throws NPE after validation

[jira] [Created] (OOZIE-2012) coordinator with an invalid cron frequency throws NPE after validation

Bowen Zhang created OOZIE-2012: -- Summary: coordinator with an invalid cron frequency throws NPE after validation Key: OOZIE-2012 URL: https://issues.apache.org/jira/browse/OOZIE-2012 Project: Oozie

[jira] [Updated] (OOZIE-2011) In non-secure environment, oozie fails "with E0508: User [?] not authorized for WF job" when killing a job

[ https://issues.apache.org/jira/browse/OOZIE-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bowen Zhang updated OOZIE-2011: --- Attachment: oozie-2011.patch > In non-secure environment, oozie fails "with E0508: User [?] not author

[jira] [Updated] (OOZIE-2011) In non-secure environment, oozie fails "with E0508: User [?] not authorized for WF job" when killing a job

[ https://issues.apache.org/jira/browse/OOZIE-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bowen Zhang updated OOZIE-2011: --- Component/s: client > In non-secure environment, oozie fails "with E0508: User [?] not authorized > f

[jira] [Created] (OOZIE-2011) In non-secure environment, oozie fails "with E0508: User [?] not authorized for WF job" when killing a job

Bowen Zhang created OOZIE-2011: -- Summary: In non-secure environment, oozie fails "with E0508: User [?] not authorized for WF job" when killing a job Key: OOZIE-2011 URL: https://issues.apache.org/jira/browse/OOZIE-20

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

See -- [...truncated 10487 lines...] [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share

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

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

Re: issue after OOZIE-1807

OOZIE-1807 and OOZIE-1940 are not related for the use-case you have specified. As I explain earlier BundleJobChangeXCommand, will apply changes to bundle job and all coord jobs and will throw exception ( with list of coord jobs that are killed). Puru. On 9/17/14, 6:18 PM, "bowen zhang" wrote:

Re: issue after OOZIE-1807

Hi Bowen, BundleJobChangeXCommand command will get applied to bundle and coord jobs. It will aggregate message for all killed coord jobs and throw them as exception. It is similar to chmod command. JIRA has more details. Let me know if you need any other information. Puru. On 9/17/14, 6:05

Re: issue after OOZIE-1807

I am actually curious about what patch changes the behavior of bundle status that oozie-1940 needs to be committed to fix this. From: Mona Chitnis To: "dev@oozie.apache.org" ; bowen zhang Sent: Wednesday, September 17, 2014 6:11 PM Subject: Re: issue after

Re: issue after OOZIE-1807

Bowen, Regarding the other issue (if a bundle with two actions - one FAILED due to coordinator submission error, other KILLED), bundle is supposed to KILLED. I see this taken care of as part of OOZIE-1940 also(StatusTransitService) but it is not committed to Apache yet. Puru can help track down

[jira] [Commented] (OOZIE-1977) Display patch analysis issues

[ https://issues.apache.org/jira/browse/OOZIE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138329#comment-14138329 ] Robert Kanter commented on OOZIE-1977: -- This seems good, but the output of the latest

Re: issue after OOZIE-1807

Puru, Bowen just gave me a call regarding this issue. Can you answer his question? That'll be faster than me digging through the code.  Mona Chitnis Yahoo! On Wednesday, September 17, 2014 5:51 PM, bowen zhang wrote: Hi guys, Purshatom, I see you checked oozie-1807 into the trunk

issue after OOZIE-1807

Hi guys, Purshatom, I see you checked oozie-1807 into the trunk. So, I have a question, why does it need to throw an exception when someone wants to change a bundle job where one of its coord job is in KILLED state? Due to the change in BundleJobChangeXCommand, this is throwing exceptions when

[jira] [Updated] (OOZIE-1676) Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers

[ https://issues.apache.org/jira/browse/OOZIE-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-1676: - Fix Version/s: (was: 4.1.0) trunk Ok, I've changed the fix version to trunk

[jira] [Commented] (OOZIE-1917) Authentication secret should be random by default and needs to coordinate with HA

[ https://issues.apache.org/jira/browse/OOZIE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138276#comment-14138276 ] Rohini Palaniswamy commented on OOZIE-1917: --- That's right. Old hadoop-auth will

[jira] [Commented] (OOZIE-1917) Authentication secret should be random by default and needs to coordinate with HA

[ https://issues.apache.org/jira/browse/OOZIE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138274#comment-14138274 ] Robert Kanter commented on OOZIE-1917: -- Currently, regardless of the Hadoop version,

[jira] [Commented] (OOZIE-1676) Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers

[ https://issues.apache.org/jira/browse/OOZIE-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138266#comment-14138266 ] Rohini Palaniswamy commented on OOZIE-1676: --- bq. Or what if we marked v3 as "evo

[jira] [Commented] (OOZIE-1917) Authentication secret should be random by default and needs to coordinate with HA

[ https://issues.apache.org/jira/browse/OOZIE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138259#comment-14138259 ] Rohini Palaniswamy commented on OOZIE-1917: --- Sorry. I just realized that with th

[jira] [Commented] (OOZIE-1876) use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc

[ https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138256#comment-14138256 ] Robert Kanter commented on OOZIE-1876: -- Ok, that's fine then if it's listed elsewhere

[jira] [Commented] (OOZIE-1917) Authentication secret should be random by default and needs to coordinate with HA

[ https://issues.apache.org/jira/browse/OOZIE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138254#comment-14138254 ] Rohini Palaniswamy commented on OOZIE-1917: --- +1 > Authentication secret should

[jira] [Commented] (OOZIE-1853) Improve the Credentials documentation

[ https://issues.apache.org/jira/browse/OOZIE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138251#comment-14138251 ] Rohini Palaniswamy commented on OOZIE-1853: --- +1 > Improve the Credentials docum

[jira] [Commented] (OOZIE-1676) Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers

[ https://issues.apache.org/jira/browse/OOZIE-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138244#comment-14138244 ] Robert Kanter commented on OOZIE-1676: -- The problem with that is that the caller now

[jira] [Updated] (OOZIE-1917) Authentication secret should be random by default and needs to coordinate with HA

[ https://issues.apache.org/jira/browse/OOZIE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-1917: - Attachment: OOZIE-1917.patch The new patch removes the signature.secret property from oozie-site/d

[jira] [Updated] (OOZIE-1853) Improve the Credentials documentation

[ https://issues.apache.org/jira/browse/OOZIE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-1853: - Attachment: OOZIE-1853_amendment.patch Here's the amendment patch, for reference. > Improve the C

[jira] [Commented] (OOZIE-1853) Improve the Credentials documentation

[ https://issues.apache.org/jira/browse/OOZIE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138196#comment-14138196 ] Robert Kanter commented on OOZIE-1853: -- Sure. I'll just throw in an "amendment" patc

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

[ https://issues.apache.org/jira/browse/OOZIE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138190#comment-14138190 ] Rohini Palaniswamy commented on OOZIE-1940: --- +1. Pending jenkins > StatusTransi

Re: Review Request 24948: OOZIE-1940 StatusTransitService has race condition

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24948/#review53770 --- core/src/main/java/org/apache/oozie/CoordinatorJobBean.java

Re: Review Request 24948: OOZIE-1940 StatusTransitService has race condition

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24948/#review53768 --- Ship it! Ship It! - Rohini Palaniswamy On Sept. 17, 2014, 10:56

[jira] [Commented] (OOZIE-1676) Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers

[ https://issues.apache.org/jira/browse/OOZIE-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138181#comment-14138181 ] Rohini Palaniswamy commented on OOZIE-1676: --- Do we really need v3 for this one?

[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-V5.patch > StatusTransitService has race condition >

Re: Review Request 24948: OOZIE-1940 StatusTransitService has race condition

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24948/ --- (Updated Sept. 17, 2014, 10:56 p.m.) Review request for oozie. Bugs: OOZIE-19

[jira] [Assigned] (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 reassigned OOZIE-1940: - Assignee: Purshotam Shah > StatusTransitService has race condition >

[jira] [Commented] (OOZIE-1917) Authentication secret should be random by default and needs to coordinate with HA

[ https://issues.apache.org/jira/browse/OOZIE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138153#comment-14138153 ] Rohini Palaniswamy commented on OOZIE-1917: --- Actually can you remove the propert

[jira] [Commented] (OOZIE-1917) Authentication secret should be random by default and needs to coordinate with HA

[ https://issues.apache.org/jira/browse/OOZIE-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138145#comment-14138145 ] Rohini Palaniswamy commented on OOZIE-1917: --- +1 > Authentication secret should

[jira] [Commented] (OOZIE-1853) Improve the Credentials documentation

[ https://issues.apache.org/jira/browse/OOZIE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138138#comment-14138138 ] Rohini Palaniswamy commented on OOZIE-1853: --- This is great [~rkanter]. I was jus

[jira] [Updated] (OOZIE-1853) Improve the Credentials documentation

[ https://issues.apache.org/jira/browse/OOZIE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-1853: - Attachment: OOZIE-1853.patch I made your change and fixed the whitespace/tab issues. For referenc

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

See -- [...truncated 10120 lines...] [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO] s

[jira] [Commented] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

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

[jira] [Created] (OOZIE-2010) Sqoop + DB2 Connection Close Error

Ajit Koti created OOZIE-2010: Summary: Sqoop + DB2 Connection Close Error Key: OOZIE-2010 URL: https://issues.apache.org/jira/browse/OOZIE-2010 Project: Oozie Issue Type: Bug Components

[jira] [Commented] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137779#comment-14137779 ] Rohini Palaniswamy commented on OOZIE-1813: --- >From [~mchiang_4w...@yahoo.com]:

[jira] [Commented] (OOZIE-1992) Cannot create workflow parameter inside any action

[ https://issues.apache.org/jira/browse/OOZIE-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137774#comment-14137774 ] Bijoy Kumar Khandelwal commented on OOZIE-1992: --- Any body working on it? >

[jira] [Reopened] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Purshotam Shah reopened OOZIE-1813: --- > Add service to report/kill rogue bundles and coordinator jobs >

[jira] [Commented] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137767#comment-14137767 ] Purshotam Shah commented on OOZIE-1813: --- 2 days buffer, fails for catchup jobs. Atta

[jira] [Updated] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Purshotam Shah updated OOZIE-1813: -- Attachment: OOZIE-1813-Amendment-V1.patch > Add service to report/kill rogue bundles and coordin

Re: Review Request 24487: OOZIE-1913 Devise a way to turn off SLA alerts for bundle/coordinator flexibly

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24487/ --- (Updated Sept. 17, 2014, 6:59 p.m.) Review request for oozie. Changes ---

[jira] [Commented] (OOZIE-1795) Please create a DOAP file for your TLP

[ https://issues.apache.org/jira/browse/OOZIE-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137748#comment-14137748 ] Rohini Palaniswamy commented on OOZIE-1795: --- http://projects.apache.org/projects

[jira] [Created] (OOZIE-2009) Requeue CoordActionInputCheck in case of permission error

Ryota Egashira created OOZIE-2009: - Summary: Requeue CoordActionInputCheck in case of permission error Key: OOZIE-2009 URL: https://issues.apache.org/jira/browse/OOZIE-2009 Project: Oozie Iss

[jira] [Commented] (OOZIE-1853) Improve the Credentials documentation

[ https://issues.apache.org/jira/browse/OOZIE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137473#comment-14137473 ] Ryota Egashira commented on OOZIE-1853: --- +1, it becomes user-friendly doc. one min

Re: Review Request 25269: OOZIE-1985 support dropping hcat dataset in coord rerun with cleanup option

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25269/ --- (Updated Sept. 17, 2014, 3:48 p.m.) Review request for oozie. Changes ---

[jira] [Updated] (OOZIE-1876) use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc

[ https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated OOZIE-1876: --- Attachment: OOZIE-1876-v6.patch > use pom properties rather than specific version numbers in the pom f

[jira] [Updated] (OOZIE-1876) use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc

[ https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated OOZIE-1876: --- Attachment: (was: OOZIE-1876-v6.patch) > use pom properties rather than specific version numbers i

[jira] [Commented] (OOZIE-2008) When oozie war is not setup, oozie service fails to start

[ https://issues.apache.org/jira/browse/OOZIE-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137147#comment-14137147 ] Shwetha G S commented on OOZIE-2008: I think it was designed this way. To make it ea

[jira] [Commented] (OOZIE-1876) use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc

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

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

See -- [...truncated 3184 lines...] [INFO] Apache Oozie Hadoop Distcp 1.2.1.oozie-4.2.0-SNAPSHOT SUCCESS [ 0.020 s] [INFO] Apache Oozie Hadoop 1.2.1.oozie-4.2.0-SNAPSHOT Test SUCCESS [ 0.

[jira] [Commented] (OOZIE-1876) use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc

[ https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137139#comment-14137139 ] Shwetha G S commented on OOZIE-1876: Updated the patch with fix for hive2 Currently,

[jira] [Updated] (OOZIE-1876) use pom properties rather than specific version numbers in the pom files of hbaselibs, hcataloglibs, sharelib, etc

[ https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated OOZIE-1876: --- Attachment: OOZIE-1876-v6.patch > use pom properties rather than specific version numbers in the pom f

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

See -- [...truncated 10151 lines...] [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share

[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-tabpanel&focusedCommentId=14136975#comment-14136975 ] Hadoop QA commented on OOZIE-2001: -- Testing JIRA OOZIE-2001 Cleaning local git workspace

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

See Changes: [rkanter] OOZIE-1954 Add a way for the MapReduce action to be configured by Java code (rkanter) -- [...truncated 9333 lines...] [INFO] already added, skipping [INFO] sh

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14136955#comment-14136955 ] Hadoop QA commented on OOZIE-1391: -- Testing JIRA OOZIE-1391 Cleaning local git workspace

[jira] [Updated] (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:all-tabpanel ] Jaydeep Vishwakarma updated OOZIE-2001: --- Attachment: rerun-0.patch > Workflow re-runs doesn't update coord action status >

[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: suspend-1.patch > Sub wf suspend doesn't update parent wf > --

[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: (was: suspend-1.patch) > Sub wf suspend doesn't update parent wf > ---