[ https://issues.apache.org/jira/browse/FALCON-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15684355#comment-15684355 ]
Ajay Yadava commented on FALCON-1406: ------------------------------------- [~sandeep.samudrala] I am still not in favor of this JIRA. My concern is not that you have made more changes than necessary, but rather it changes a fundamental assumption about the way falcon works and hence impacts a lot of current features and lot of features in future. This feature makes the code hard to reason for a lot of features. > 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)