falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandeep samudrala (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1406) Effective time in Entity updates.
Date Tue, 18 Aug 2015 06:46:45 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

sandeep samudrala updated FALCON-1406:
--------------------------------------
    Description: 
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.




  was:
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. 




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



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

Mime
View raw message