[
https://issues.apache.org/jira/browse/OOZIE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199611#comment-13199611
]
[email protected] commented on OOZIE-674:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3752/
-----------------------------------------------------------
(Updated 2012-02-03 09:33:10.266513)
Review request for oozie.
Summary (updated)
-------
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 addresses bug OOZIE-674.
https://issues.apache.org/jira/browse/OOZIE-674
Diffs
-----
Diff: https://reviews.apache.org/r/3752/diff
Testing
-------
UT - TestCoordActionMaterializeCommand
Tested with coord:current instance range and EL extension
Thanks,
shwethags
> 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
> Labels: EL, extension
> Attachments: OOZIE-674.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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
