[
https://issues.apache.org/jira/browse/FALCON-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272599#comment-14272599
]
Srikanth Sundarrajan commented on FALCON-664:
---------------------------------------------
Nothing in the config seems to suggest that it is running at 1pm. With this
approach schedule will be dependent on the actual time when schedule/update is
performed. Can this be improved further to remove the ambiguity and
non-deterministic nature of the schedule?
{quote}
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"/>
{quote}
> 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)
