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

Hudson commented on FLUME-1230:
-------------------------------

Integrated in flume-trunk #216 (See 
[https://builds.apache.org/job/flume-trunk/216/])
    FLUME-1230. Components can get initialized even when not active.

(Hari Shreedharan via Mike Percy) (Revision 1344126)

     Result = SUCCESS
mpercy : http://svn.apache.org/viewvc/?view=rev&rev=1344126
Files : 
* 
/incubator/flume/trunk/flume-ng-configuration/src/main/java/org/apache/flume/conf/FlumeConfiguration.java
* 
/incubator/flume/trunk/flume-ng-node/src/main/java/org/apache/flume/conf/properties/PropertiesFileConfigurationProvider.java

                
> Sink gets initialized even when not active
> ------------------------------------------
>
>                 Key: FLUME-1230
>                 URL: https://issues.apache.org/jira/browse/FLUME-1230
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Arvind Prabhakar
>            Assignee: Hari Shreedharan
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1230-refactor.diff, FLUME-1230.patch
>
>
> Flume configuration requires that components that are not declared in the 
> active lists (agent.sources, agent.sinks, agent.channels, and 
> agent.sinkgroups) be disabled by default. However, in some cases, sinks that 
> are not in the active list will get initialized and started. 
> Following configuration can reproduce this scenario:
> {noformat}
> agent.sources = s
> agent.channels = c
> #agent.sinks = k1 k2
> agent.sources.s.type = netcat
> agent.sources.s.port = 12121
> agent.sources.s.bind = localhost
> agent.sources.s.channels = c
> agent.channels.c.type = memory
> agent.sinks.k1.type = logger
> agent.sinks.k1.channel = c
> agent.sinks.k2.type = null
> agent.sinks.k2.channel = c
> {noformat}

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

        

Reply via email to