[
https://issues.apache.org/jira/browse/FLUME-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191526#comment-13191526
]
Arvind Prabhakar commented on FLUME-932:
----------------------------------------
Eric, this primary objective of this change was to allow name support for
components. So an avro source can be named "myavrosrc" instead of being
required to call it "avro" only. It also enables us to have multiple avro
sources that are named differently within the same agent (myavrosrc1,
myavrosrc2) and be able to configure them differently. It is not an intent, but
a side-effect, that you cannot have two plugins of the same type that are named
the same.
bq. 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.
The enum here is a convenient idiom to have one place registration of
short-names to class-name mapping for various components. What was previously
being done in Application.loadPlugins() method is now externalized into these
enums. These enums are only there to enumerate the built-in components and do
not in anyway inhibit the use of drop-in components. The convenience they offer
is to allow the user to specify the type of a source as avro, instead of its
fully qualified class name.
> 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
