falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-238) Support updates at specific time
Date Mon, 06 Jan 2014 06:59:51 GMT

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

Shwetha G S updated FALCON-238:
-------------------------------

    Description: 
Currently, feed/process update sets end time of coordinator to now and then creates new coord
with start time as now. When updating a process's workflow/lib, its useful to stage an update
with specific timestamp so that all instances before the timestamp use the old lib and instances
after the timestamp use new lib. This is useful to roll-out any application changes

This can be implemented by taking additional timestamp argument in update and honour that
whenever possible. For cases where this can't be honoured, return the update timestamp always
so that user is aware of when the new lib is used



  was:
Currently, feed/process update sets end time of coordinator to now and then creates new coord
with start time as now. When updating a process's workflow/lib, its useful to stage an update
with specific timestamp so that all instances before the timestamp use the old lib and instances
after the timestamp use new lib. This is useful to roll-out any application changes

This can be implemented by taking additional timestamp argument in update and honour that
whenever possible. For cases where this can't be honoured, return the update timestamp always
so that user is ware of when the new lib is used




> Support updates at specific time
> --------------------------------
>
>                 Key: FALCON-238
>                 URL: https://issues.apache.org/jira/browse/FALCON-238
>             Project: Falcon
>          Issue Type: New Feature
>            Reporter: Shwetha G S
>            Assignee: Shwetha G S
>             Fix For: 0.5
>
>         Attachments: FALCON-238.patch
>
>
> Currently, feed/process update sets end time of coordinator to now and then creates new
coord with start time as now. When updating a process's workflow/lib, its useful to stage
an update with specific timestamp so that all instances before the timestamp use the old lib
and instances after the timestamp use new lib. This is useful to roll-out any application
changes
> This can be implemented by taking additional timestamp argument in update and honour
that whenever possible. For cases where this can't be honoured, return the update timestamp
always so that user is aware of when the new lib is used



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message