incubator-flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "E. Sammer (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLUME-728) Flume NG refactoring
Date Wed, 05 Oct 2011 23:18:29 GMT

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

E. Sammer updated FLUME-728:
----------------------------

    Affects Version/s: NG
    
> Flume NG refactoring
> --------------------
>
>                 Key: FLUME-728
>                 URL: https://issues.apache.org/jira/browse/FLUME-728
>             Project: Flume
>          Issue Type: Epic
>          Components: Build, Docs, Master, Node, Shell, Sinks+Sources, Technical Debt,
Test, Web
>    Affects Versions: NG
>            Reporter: E. Sammer
>            Assignee: E. Sammer
>              Labels: NG
>
> To solve certain known issues and limitations, Flume requires a refactoring of some core
classes and systems. This bug is a parent issue to track the development of a "Flume NG" -
a poorly named, but necessary refactoring. Subtasks should be added to track individual systems
and components.
> The following known issues are specifically to be addressed:
> * Code complexity; Flume has evolved over the last few years and has a fair amount of
extraneous code.
> * Core component lifecycle standardization and control code (e.g. anything that can be
start()ed or stop()ed, sources, sinks).
> * (Static) Configuration access throughout the code base.
> * Drastic simplification of common data paths (e.g. durability as an element of the source
rather than a disconnected sink).
> * Heartbeat and master rearchitecture.
> * Renaming packages to org.apache.flume.
> This is a large and far reaching set of tasks. The intent is to perform this work in
a branch as to not disrupt immediate releases or short term forthcoming releases while still
allowing open development in the community.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message