[
https://issues.apache.org/jira/browse/FLUME-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186733#comment-13186733
]
E. Sammer commented on FLUME-932:
---------------------------------
I know this was committed already and I missed it, but I'm not so sure are
ideal here.
This seems to deal with the case that one can't have two plugin definitions for
the same name. I'm not sure how this matters though. For instance, the name
"memory" only allows one to *create* new instances of MemoryChannel that are
unrelated; there's nothing else shared here.
The other issue is that we now use enums to create instances of various
components. This means that those creating new components are going to be
tempted to add items to the enum. This is pretty gross. I have a really, really
strong preference for reverting this. If this is because there's a desire to
have spring-like functionality, let's just use spring.
> 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
> Reporter: Arvind Prabhakar
> Assignee: Arvind Prabhakar
> 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
