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

Pallavi Rao commented on FALCON-664:
------------------------------------

Hmm.. to make it less ambiguous, we'll have to introduce another attribute in 
addition to start time. Lets say, in the initial process spec. user had this:
 <validity start="2014-01-15T00:00Z" end="2014-11-15T01:05Z"/>

Now, the user would like to update the time such that it starts at 2 am rather 
than 12 midnight for future instances, he/she will change the spec. during 
update to:
 <validity start="2014-01-15T00:00Z" startOffset=next(0,2,0) 
end="2014-11-15T01:05Z"/>
The syntax being next(days, hours, minutes). If no offset attribute is 
specified, it is assumed that the schedule remains unchanged, equivalent to 
next(0,0,0). startOffset need not be an attribute used for update. The offset 
can be applied during creation too.

During process/feed updates the start time update will be disallowed if the 
instance is already active. Meaning, if the original spec. had the start time 
in the past. If the original spec. had the start time in the future, we can 
allow for updates.



> 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)

Reply via email to