falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1406) Effective time in Entity updates.
Date Thu, 24 Nov 2016 02:49:58 GMT

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

Srikanth Sundarrajan commented on FALCON-1406:
----------------------------------------------

Further to notes from the discussion, here are my suggestions on how we proceed with this

* First things first, ensure that design document is updated to reflect the complete approach,
detailing all the affected sub systems and how they are being handled
* Track all open issues with independent jiras
* Create a branch to track this given the nature of the change (The reasons for suggesting
a branch is that work can get in continuously instead of one very large chunk and possibly
test automation can also commence. Large incoming patches are always difficult to review.
Also if in a branch, it can be kept upto date as other changes get in)
* Merge the branch once we are satisfactorily ready

I would echo what [~ajayyadava] had to say about the mammoth effort by [~sandeep.samudrala]
thus far on the work. Thanks

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

Mime
View raw message