Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Tue, 23 Feb 2016 12:49:18 +0000 (UTC)
From: "sandeep samudrala (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12856828.1439879703000.121339.1456231758121@Atlassian.JIRA>
In-Reply-To: <JIRA.12856828.1439879703000@Atlassian.JIRA>
References: <JIRA.12856828.1439879703000@Atlassian.JIRA>
 <JIRA.12856828.1439879703110@arcas>
Subject: [jira] [Commented] (FALCON-1406) Effective time in Entity updates.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sandeep samudrala commented on FALCON-1406:
-------------------------------------------

[~peeyushb]: Thanks for reviewing. I will update the twikis and documentation accordingly for the same. Once it looks in a good shape, I will raise a pull Request for final review.

> 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
>              Labels: syncup
>         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)