You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org> on 2012/03/06 23:07:59 UTC

[jira] [Commented] (FLUME-932) Making flume-ng components pluggage and name aware

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

Arvind Prabhakar commented on FLUME-932:
----------------------------------------

As the discussion has tapered off I am going to mark this issue resolved. If any further issue needs to be addressed as a result of this, please open new Jiras.
                
> Making flume-ng components pluggage and name aware
> --------------------------------------------------
>
>                 Key: FLUME-932
>                 URL: https://issues.apache.org/jira/browse/FLUME-932
>             Project: Flume
>          Issue Type: Improvement
>    Affects Versions: v1.0.0
>            Reporter: Arvind Prabhakar
>            Assignee: Arvind Prabhakar
>             Fix For: v1.1.0
>
>         Attachments: FLUME-932-1-svn.patch, FLUME-932-2-svn.patch
>
>
> Currently the components in flume-ng are hard wired to use the built in name. This implies that within one agent, there can be only one instance of a particular component. While the configuration supports having multiple components of the same time, the component interfaces themselves need to change.
> Also, need to support plugin components for user-provided implementations of source/sink/channels where necessary.

--
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