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] [Commented] (FALCON-1406) Effective time in Entity updates.
Date Fri, 11 Nov 2016 05:11:58 GMT

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

sandeep samudrala commented on FALCON-1406:

 [~Praveen] : The way to look at is to see that all these features can benefit from this feature.
And also the changes to these services are confined to update the check time to the past time
if the effective time is in the past and remove any instances that are being monitored from
the effective time to the current time. The recipe has got noting to do with this feature,
the moment the entities are being submitted its to deal with the entities updates and got
nothing to do with recipe. 

This feature is being waited upon by a lot of users where the users keep creating new entities
each time when they would need to update the libs which would not work for older instances
and also there is no way for the user to specify a time where the user's updates would have
to be effective from , which results in doing a lot of manual work to handle for those overlapping
instances and worse might have to create a new entity and then acknowledge all the alerts
that get pushed.

I have added more comments in the comment above this comment. I hope they answer your comment.

> 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

View raw message