[jira] [Commented] (FALCON-1406) Effective time in Entity updates.

["Peeyush Bishnoi (JIRA)" <ji...@apache.org>]

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

Peeyush Bishnoi commented on FALCON-1406:
-----------------------------------------

[~sandeep.samudrala] I have done initial review of the patch and put up my comments. Can you also please put some statements about this in Falcon Architecture doc to make the user aware, what is effective time and how it works.

> Effective time in Entity updates.
> ---------------------------------
>
>                 Key: FALCON-1406
>                 URL: https://issues.apache.org/jira/browse/FALCON-1406
>             Project: Falcon
>          Issue Type: New Feature
>            Reporter: sandeep samudrala
>            Assignee: sandeep samudrala
>              Labels: syncup
>         Attachments: FALCON-1406-initial.patch, effective_time_in_entity_updates.pdf
>
>
> Effective time with entity updates needs to be provided even with past time too. There was effective time capability provided in the past which gives the functionality to set an effective time for an entity with only current or future time(now + delay), which could not solve all the issues. 
> Following are few scenarios which would require effective time to be available with time back in past.
> a) New code being deployed for an incompatible input data set which would leave instances with old code and new data.
> b) Bad code being pushed for which, the entity should be able to go back in time to replay(rerun) with new code.
> c) Orchestration level changes(good/bad) would need functionality to go back in time to start with.
> For reference: Linking all the Jiras that have been worked upon around effective time .
> https://issues.apache.org/jira/browse/FALCON-374
> https://issues.apache.org/jira/browse/FALCON-297



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)