[
https://issues.apache.org/jira/browse/FLUME-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432057#comment-13432057
]
Hari Shreedharan commented on FLUME-1452:
-----------------------------------------
Denny - This is built into the architecture. The source need not know about the
sink at all. The channel is a buffer to store the events. It is entirely
possible to connect a sink to that channel later to retrieve the events from
that. I don't think there is anything wrong with the current set up. We can
have channels with either a source or a sink or both, but every channel must
have at least one - the idea being that you either buffer event in the channel
or drain events from it or do both.
> Source should not submit event to Sink which it doesnot connect to any Sink
> ---------------------------------------------------------------------------
>
> Key: FLUME-1452
> URL: https://issues.apache.org/jira/browse/FLUME-1452
> Project: Flume
> Issue Type: Bug
> Components: Configuration
> Affects Versions: v1.2.0
> Reporter: Denny Ye
> Assignee: Denny Ye
> Labels: Sink
> Fix For: v1.3.0
>
>
> If there has Channel (mc) and it does not connect to any Sink, Source
> shouldn't submit event to it.
> Configuration example:
> {quote}
> #Channels that Source connect to
> agent.sources.scribesource.channels = mc
> #No specified Sink connect to this Channel
> {quote}
> Otherwise, event in this Channel is increasing and no consumer, it's
> misunderstanding.
--
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
