[
https://issues.apache.org/jira/browse/FALCON-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268859#comment-14268859
]
Pallavi Rao commented on FALCON-664:
------------------------------------
How about this -
We introduce support for EL for start time too (it has been a pending ask
anyway). And for updates the only allowed value would be next(h,m). The values
of h and m can be used to offset the next start time of the bundle.
For example, If the job has been running at 1 pm everyday and the user wants to
move it to 12 noon. Here is how he would specify the start time: <validity
start="next(-1,0)" end="2030-01-01T00:00Z"/>. If the user wishes to keep the
job schedule unchanged he would just say : <validity start="next(0,0)"
end="2030-01-01T00:00Z"/>
Validations:
1. For updates, the only supported EL (at least for now), will be next(h,m)
2. If after applying the offset, the start time turns out to be before the
current time, we error out.
3. Have an upper bound on h + m (can't be greater than frequency) to avoid
scenarios where the next start happens to be a few days from today for a daily
job
> Enforce Validations on Update in Process/Feed Definition
> ---------------------------------------------------------
>
> Key: FALCON-664
> URL: https://issues.apache.org/jira/browse/FALCON-664
> Project: Falcon
> Issue Type: Improvement
> Reporter: Kisalay Ranjan
>
> Falcon should enforce Validation on update of the process/feed definition.
> This is specifically applicable for Start Times.
> Today falcon verbatim updates already configured and deployed start time with
> input start time.
> By doing this, a user can un-intentionally update the start time to recent
> time, and make all the past status of the process un-accessible through
> falcon.
> My understanding is that the start times are changed today to reflect the
> change in offset at which the process runs (10th minute of the hour for
> hourly jobs or 11th hour of the day for daily job).
> Falcon should just allow for the change in the offset and not the start time
> itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
