You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2012/06/18 21:17:42 UTC

[jira] [Commented] (OOZIE-860) start-instance and end-instance should limit 1

    [ 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