You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/01/23 12:22:13 UTC

[jira] [Commented] (OOZIE-674) resolveInstanceRange doesn't work for EL extensions

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

Hadoop QA commented on OOZIE-674:
---------------------------------

Testing JIRA OOZIE-674

Cleaning local svn workspace
                
> resolveInstanceRange doesn't work for EL extensions
> ---------------------------------------------------
>
>                 Key: OOZIE-674
>                 URL: https://issues.apache.org/jira/browse/OOZIE-674
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Shwetha G S
>              Labels: EL, extension
>         Attachments: OOZIE-674.patch, OOZIE-674-ver2.patch
>
>
> I have an EL extension today(0,0) which maps to start day of nominal time. This is used to specify startInstance, endInstance and instance in dataIn and dataOut of coordinator.
> In CoordCommandUtils.resolveInstanceRange(), getInstanceNumber has to return the instance number with respect to current. So, for coord-action-create-inst context, I have mapped today to current and hence getInstanceNumber returns the correct number. But later in resolveInstanceRange(), getFuncType is called with startInstance value which is today in this case and it maps to UNEXPECTED and throws up. getFuncType should be passed the evaluation of coord-action-create-inst context

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira