subject:"\[jira\] \[Commented\] \(OOZIE\-1567\) Provide a wait tool in Oozie"

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-22 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-1567:
---

+1

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1959/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1520
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1956/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1957/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1953/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1952/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1951/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-1567:
---

+1, after fixing minor comments.

{quote}
--change  change a coordinator/bundle job
+-change  change a coordinator job
{quote}
Should be both coordinator and bundle.


{quote}
+/**
+ * Poll a job (Workflow Job ID, Coordinator Job ID, Coordinator Action ID, 
or Bundle Job ID) and return when it has reached a
+ * terminal state.
+ * (i.e. FAILED, KILLED, SUCCEEDED)
+ *
+ * @param id The Job ID
+ * @param timeout timeout in milliseconds (negative values indicate no 
timeout)
+ * @param interval polling interval in milliseconds (must be positive)
+ * @param verbose if true, the current status will be printed out at each 
poll; if false, no output
+ * @throws OozieClientException thrown if the job's status could not be 
retrieved
+ */
+public void poll
{quote}
timeout and interval are in minutes.


{quote}
--action  coordinator rerun/kill on action ids 
(requires -rerun/-kill); coordinator log retrieval on action ids (requires -log)
+-action  coordinator rerun on action ids 
(requires -rerun);
+  coordinator log retrieval on action ids 
(requires -log)
{quote}
Why (requires -rerun/-kill) is changed (requires -rerun). -kill also need 
-action.


> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1948/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-05 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

I've created OOZIE-1995 to look into making {{-poll}} work when (re)running 
jobs; I agree that it will be useful but it's going to be tricky I think.

For getting just the status column, I think I can just do that in this JIRA.  
As for the API, you can currently do 
{{/oozie/v2/job/000-140812153825178-oozie-oozi-W?show=info}} (or 
"definition", "log", etc)); so I can create 
{{/oozie/v2/job/000-140812153825178-oozie-oozi-W?show=status}} to fetch 
only the status column.

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-05 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1517
.Tests failed: 2
.Tests errors: 0

.The patch failed the following testcases:

.  
testActionKillCommandActionNumbers(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
.  
testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1911/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-05 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-1567:
---

{quote}
 I think we should leave both at minutes (the last patch from yesterday). 
 {quote}
[~rkanter]] Can you please put final patch? We went back and forth multiple 
times, so not sure which patch to review.
Regarding testing, you can use {{TestOozieCLI}} to test cli options. 

Can you also create two different JIRA,
1.
{quote}
We use getCoordJobInfo API to get job status ,which fetches every column from 
DB ( this can be fixed later, we can have a API just to report status). 
{quote}
We should avoid fetching unneeded columns.

2.
{quote}
As for allowing -poll to be used as an action and an argument like -dryrun, I 
don't think that will be as easy because when used as an action, it needs to 
take an argument (the job id) but as an argument it has no arguments. Even if 
we hack something to accept that, it's going to be confusing for the user. So 
I'm inclined to just keep it as an action.
{quote}
We should explore and see how can we do this? Running/rerunning and polling in 
same command will be useful for users.

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-04 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1896/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1891/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1511
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testCoordActionInputCheckXCommandUniqueness(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1890/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1511
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1889/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1511
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1887/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1469
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1888/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

I know I keep switching opinions on this, but Puru has a good point.  I think 
we should leave both at minutes ([the last patch from 
yesterday|https://issues.apache.org/jira/secure/attachment/12666112/OOZIE-1567.patch]).
  If the user really wants to poll at millisecond intervals, they can still 
write their own script/code to do so.

[~shwethags], unless you have a good reason for needing milliseconds?

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-1567:
---

{quote}
In CLI, you can take it in mins. For an automated application on top of oozie, 
waiting for mins doesn't work. The java API can take the argument in msecs.
{quote}

Why do you want to poll at msecs? Even getJobInfo API will take few sec to 
report status.   
In most of case Oozie Job will take at-least few minutes to complete.
As per my experience at Y!. If you expose API, people will start abusing it and 
calling server at every msecs will impact server performance and can even bring 
it down.

We use getCoordJobInfo API to get job status ,which fetches every column from 
DB ( this can be fixed later, we can have a API just to report status).

If users start using api like below, it might bring down DB and Oozie server.
public void pollJob(1864089-140715190315682-oozie-wrkf-C, -1, 5ms, true)

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-03 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

{quote}In CLI, you can take it in mins. For an automated application on top of 
oozie, waiting for mins doesn't work. The java API can take the argument in 
msecs.{quote}
That's a good compromise.  I'll do that.

As for allowing -poll to be used as an action and an argument like -dryrun, I 
don't think that will be as easy because when used as an action, it needs to 
take an argument (the job id) but as an argument it has no arguments.  Even if 
we hack something to accept that, it's going to be confusing for the user.  So 
I'm inclined to just keep it as an action.  

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Shwetha G S (JIRA)


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

Shwetha G S commented on OOZIE-1567:


{quote}
Can you please specify time in Min/Sec?
You have a good point here; I’ll make it in minutes.
{quote}
In CLI, you can take it in mins. For an automated application on top of oozie, 
waiting for mins doesn't work. The java API can take the argument in msecs.

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1511
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1827/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

Well, maybe it should be an argument and an action.  It's probably a pretty 
common desire to submit a job and poll it.  I'll look at OOZIE-1878 and do 
something similar; thanks.

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1835/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

I didn't see your comment about -dryrun.  Still, I think we should leave -poll 
as only a job action for now to keep things cleaner and only add it as an 
argument if users want it.  Unless you think we should do the same as -dryrun?

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1511
.Tests failed: 5
.Tests errors: 2

.The patch failed the following testcases:

.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1816/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1511
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testBundlePauseExtendMaterializesCoordinator(org.apache.oozie.command.bundle.TestBundleChangeXCommand)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1805/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1511
.Tests failed: 8
.Tests errors: 2

.The patch failed the following testcases:

.  
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
.  
testCoordChangeEndTime3(org.apache.oozie.command.coord.TestCoordChangeXCommand)
.  
testUnpauseBundleAndCoordinator(org.apache.oozie.service.TestPauseTransitService)
.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1798/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-1567:
---

That may not be easy. I did some workaround for -dryrun.
Now -dryrun is a command and -dryrun is also sub command (it is used with 
command -update).

 You can look at my patch @https://issues.apache.org/jira/browse/OOZIE-1878

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

{quote}Doesn't it make more sense for poll to be part of job command, after all 
it's a job operation.
oozie job -poll 
I also like your initial design of adding poll as part of -rerun/-submit.{quote}
I think that makes sense.  I'll see if I can get it to work with and without 
having to specify -rerun/-submit/-run/etc because I can envision cases where 
the user wants to submit the job and poll at the same time and cases where they 
don't.  

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1511
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1795/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1511
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1794/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-1567:
---

{quote}
I think this makes it a bit more consistent with other commands (most of them 
don't take a direct argument). I think it’s also clearer in how the help text 
works with it as a separate argument. Also, I don’t see a way to make the 
argument required if it’s not a separate argument.
{quote}
I didn't noticed that poll is as new command. 
Doesn't it make more sense for poll to be part of job command, after all it's a 
job operation.
oozie job -poll 

I also like your initial design of adding poll as part of -rerun/-submit.
Biggest use-case I see is that when user submit workflow/catchup mode coord or 
rerun coord action/Wf, he would like to wait till completion.
In this case he have to run one more command to poll job status. I guess we can 
do both.

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch, 
> OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1793/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-1567:
---

Few Comments

1.$ oozie poll -id 

Do we need to specify option -id, the command can be just "oozie poll "?

2. +public static final String QUIET_OPTION = "quiet";
In place of adding new option "quiet" can you using existing option "verbose".

If verbose is enable, it will print job status else no.

3.
{code} 
+Option timeout = new Option(TIMEOUT_OPTION, true, "timeout in 
milliseconds (default is 30 min, negative values indicate "
++ "no timeout)");
+Option interval = new Option(INTERVAL_OPTION, true, "polling interval 
in milliseconds (default is 5 min)");
{code}

Can you please specify time in Min/Sec? I don't think anybody will like to 
specify time in milliseconds ( we should even not support specifying time in 
milliseconds as it will increase load on server)


4. For coord "IGNORED" is also a terminal state.

{code}
public boolean isTerminalStatus() {
boolean isTerminal = false;
switch (getStatus()) {
case SUCCEEDED:
case FAILED:
case KILLED:
case DONEWITHERROR:
case IGNORED:
isTerminal = true;
break;
default:
isTerminal = false;
break;
}
return isTerminal;
}
 {code}
 
 5. We can also support polling of coord action, user can rerun a coord action 
and may want to poll it. This might be more useful in compare to polling on 
coord/bundle ( as coord/bundle may run for days).
 

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1511
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1788/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1789/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-09-01 Thread Shwetha G S (JIRA)


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

Shwetha G S commented on OOZIE-1567:


{noformat}
+Option timeout = new Option(TIMEOUT_OPTION, true, "timeout in seconds 
(default is -1 (no timeout))");
+Option interval = new Option(INTERVAL_OPTION, true, "polling interval 
in seconds (default is 60)");
{noformat}
we should give sane default for timeout, just in case the user forgets to stop 
if the job is stuck(this will unnecessarily put more load on oozie). Probably 
10 mins/1 hour. Depends on the kind of jobs that users typically launch. We use 
coord always. So, I don't know the typical workflow usecases
interval depends on workflow usecases again. Pick something thats useful for 
most

{noformat}
+public void pollJob(String id, int timeout, int interval, boolean quiet) 
throws OozieClientException {
{noformat}
Its better to expose time in milli secs as long

{noformat}
+System.out.println(jobInfo.getStatus());
{noformat}
This doesn't print '.'. Is it intentional?

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-29 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

Test failures unrelated.

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-28 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1510
.Tests failed: 2
.Tests errors: 0

.The patch failed the following testcases:

.  
testCoordStatusTransitServiceSuspendedWithError(org.apache.oozie.service.TestStatusTransitService)
.  
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1770/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1510
.Tests failed: 6
.Tests errors: 33

.The patch failed the following testcases:

.  testActionStart(org.apache.oozie.command.wf.TestActionStartXCommand)
.  
testActionReuseWfJobAppPath(org.apache.oozie.command.wf.TestActionStartXCommand)
.  
testActionWithEscapedStringAndCDATA(org.apache.oozie.command.wf.TestActionStartXCommand)
.  testRerun(org.apache.oozie.action.hadoop.TestRerun)
.  testRerunFork(org.apache.oozie.command.wf.TestReRunXCommand)
.  
testActionStartWithEscapeStrings(org.apache.oozie.command.coord.TestCoordActionStartXCommand)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1750/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1510
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1749/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1510
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1748/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-27 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1510
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1747/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-25 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-25 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1567:
--

{quote}Why would the poll require -run or -start. I thought the command is: 
oozie job -poll {quote}
I had originally envisioned that the user would do something like {{oozie job 
-config job.properties -run -poll}} which would start the job and do the 
polling.  In hindsight, I think it will be simpler if we make it a separate 
command like you suggest.  i.e. you'd submit the job and then do {{oozie poll 
}}.  A {{-timeout }} argument is also a good idea.  Maybe a 
{{-interval }} would also be useful.  These and any other arguments we 
want to add later, will be easier and clearer with poll being a separate 
command.

I'll post a new patch when I've refactored that.

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-22 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-22 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-08-03 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-06-09 Thread Shwetha G S (JIRA)


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

Shwetha G S commented on OOZIE-1567:


{noformat}
+-poll poll Oozie for job status instead of 
returning immediately;
+  requires -run or -start
Why would the poll require -run or -start. I thought the command is: oozie job 
-poll 
{noformat}

Also, a timeout will be useful for poll

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2014-04-08 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-1567:
--

Testing JIRA OOZIE-1567

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1409
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1157/

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Assignee: Robert Kanter
>Priority: Trivial
> Attachments: OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1567) Provide a wait tool in Oozie

2013-10-10 Thread Mona Chitnis (JIRA)


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

Mona Chitnis commented on OOZIE-1567:
-

Please look at the alternative of receiving Job notifications on status change. 
http://oozie.apache.org/docs/4.0.0/DG_JMSNotifications.html

> Provide a wait tool in Oozie
> 
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 4.0.0
>Reporter: Viji
>Priority: Trivial
>
> Currently, in situations where a program has to wait to check wether an oozie 
> workflow is successful or not, it is done by constantly pinging the oozie 
> workflow status (that is, manual scripts need to be written). It would be 
> good if Oozie provided a {{oozie wait -jobID }} or similar.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

53 matches

Mail list logo