falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-965) Open up life cycle stage implementation within Falcon for extension
Date Tue, 08 Dec 2015 20:08:11 GMT

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

Suresh Srinivas commented on FALCON-965:
----------------------------------------

[~ajayyadava], the design document for life cycle is sparse on details. Is there a more detailed
document that also includes the changes to falcon architecture etc.? Another concern I have
is backward compatibility and how existing processes are going to be migrated to the new proposal.

> Open up life cycle stage implementation within Falcon for extension
> -------------------------------------------------------------------
>
>                 Key: FALCON-965
>                 URL: https://issues.apache.org/jira/browse/FALCON-965
>             Project: Falcon
>          Issue Type: New Feature
>    Affects Versions: 0.7
>            Reporter: Srikanth Sundarrajan
>            Assignee: Ajay Yadava
>              Labels: recipes
>             Fix For: 0.8
>
>         Attachments: FALCON-965-v1.patch, FALCON-965-v2.patch, FALCON-965-v3.patch, FALCON-965-v4.patch,
FALCON-965.patch, FalconLifecycle-Designdoc.pdf, coord-lc.txt, xsd.patch
>
>
> As it stands Falcon supports replication, generation and eviction lifecycle stages and
plans to support more. This however assumes a certain way of implementing a life cycle function
and changes to these implementation aren't easy, as they are not open for easy extension.
This proposed feature is open this up in Falcon.
> Here is a proposal on how things can possibly be:
> * List of life cycles that Falcon supports would be well known and not extensible
> * Dependency between life cycles are coded up in the falcon server and not necessarily
extensible. (In short adding a new life cycle still requires changes in Falcon)
> * Each Lifecycle in falcon advertises an implementation interface and minimum configuration
interface (for ex. Eviction should expose a way to retrieve the configured time limit for
which data will be available for other life cycle stages to validate. There is no point in
having a process consume last 24 instances of a feed, when the retention will retain only
4 instances)
> * Similar to FALCON-634, life cycle implementation can be dropped in as long as the implementation
interface and configuraion interfaces are adhered to.



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

Mime
View raw message