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 04:43:59 GMT

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

sandeep samudrala commented on FALCON-1406:

Copying Summary of comments from @ajay.yadava from review board.

I haven't looked at the patch in detail, but I have noticed several things from earlier reviews.
1. It affects an unusually large number of functionalities.
2. It has taken a heroic effort over a considerable time to bring it up to this stage.
3. It adds lot of semantic burden on existing code base.
4. It will put an extra burden on the new features as they will have to support these scenarios
as well.

Given the ROI of this feature, all these are alarming signs. In my several years of supporting
a large deployment of Falcon, I have never exeperienced a strong need for this as there are
alternatives. IMO, it is a good to have but not a must have feature and given the ROI, I will
recommend dropping it. 

If you have different views on why this feature is a must have, I am happy to hear them.

> 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