[
https://issues.apache.org/jira/browse/OOZIE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203297#comment-13203297
]
Shwetha G S commented on OOZIE-674:
-----------------------------------
Motivation for the EL extension:
This EL extension is used to specify startInstance and endInstance of input
dataset and instance of output dataset. If we use coord:current, when we change
the job schedule time, even input/output instances need to be changed and this
is a two step process which the user can miss very easily. Instead, if we use
today(0,0) which points to beginning time of scheduled day, instance need not
be changed with changes in job schedule time.
For example, if the input for a job is an hourly input for the whole of
previous day, and the job is scheduled at 2nd hour, input range is
coord:current(-3) to coord:current(-26). If we change job schedule time to 4th
hour for some reason, even input needs to be changed to coord:current(-5) to
coord:current(-28). Instead, if we use EL extensions, the instance range will
be yesterday(0,0) to today(-1,0). This doesn't need to be changed when we
update job schedule time.
We want to use oozie-3.1.3. Can you please review the patch and add it to the
release
> 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
