You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Britt Cyr (JIRA)" <ji...@apache.org> on 2012/06/06 00:34:23 UTC
[jira] [Created] (OOZIE-860) start-instance and end-instance should
limit 1
Britt Cyr created OOZIE-860:
-------------------------------
Summary: start-instance and end-instance should limit 1
Key: OOZIE-860
URL: https://issues.apache.org/jira/browse/OOZIE-860
Project: Oozie
Issue Type: Improvement
Reporter: Britt Cyr
Priority: Minor
when coordinator.xml input instance has either
<start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
or
<end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
oozie creates the coordinator job but does not create actions.
it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-860) start-instance and end-instance
should limit 1
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403660#comment-13403660 ]
Virag Kothari commented on OOZIE-860:
-------------------------------------
looks good.. +1
Committed to trunk
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-860-v2.patch, OOZIE-860-v3.patch, OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-860) start-instance and end-instance should
limit 1
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-860:
----------------------------
Attachment: OOZIE-860-v3.patch
Made separate methods.
Added testing.
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-860-v2.patch, OOZIE-860-v3.patch, OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-860) start-instance and end-instance should
limit 1
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-860:
----------------------------
Attachment: (was: multipleStart-Instance.patch)
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-860) start-instance and end-instance should
limit 1
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-860:
----------------------------
Attachment: OOZIE-860-v2.patch
Created separate error messages for start-instance and end-instance
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-860-v2.patch, OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-860) start-instance and end-instance
should limit 1
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402029#comment-13402029 ]
Virag Kothari commented on OOZIE-860:
-------------------------------------
Two comments:
1) Can we have separate methods for checks of start-instance, end-instance nd instance?
2) Adding a test case would help
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-860-v2.patch, OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OOZIE-860) start-instance and end-instance
should limit 1
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari resolved OOZIE-860.
---------------------------------
Resolution: Fixed
Fix Version/s: trunk
Assignee: Britt Cyr
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-860-v2.patch, OOZIE-860-v3.patch, OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-860) start-instance and end-instance should
limit 1
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-860:
----------------------------
Attachment: multipleStart-Instance.patch
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: multipleStart-Instance.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-860) start-instance and end-instance
should limit 1
Posted by "Mona Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396169#comment-13396169 ]
Mona Chitnis commented on OOZIE-860:
------------------------------------
There can only be a single <start-instance> and a single <end-instance> tag to mark the synchronous dataset range. 'handleExpressionWithMultipleInstances' will not output the correct error message for this. Consider accounting for it in that method or writing separate error messages directly in your code block.
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-860) start-instance and end-instance should
limit 1
Posted by "Britt Cyr (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Britt Cyr updated OOZIE-860:
----------------------------
Attachment: OOZIE-860.patch
> start-instance and end-instance should limit 1
> -----------------------------------------------
>
> Key: OOZIE-860
> URL: https://issues.apache.org/jira/browse/OOZIE-860
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-860.patch
>
>
> when coordinator.xml input instance has either
> <start-instance>${coord:current(-10)},${coord:current(-11)}</start-instance>
> or
> <end-instance>${coord:current(0)},${coord:current(-1)}</end-instance>
> oozie creates the coordinator job but does not create actions.
> it would be nice to implement the check to error out at job submission
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira