[
https://issues.apache.org/jira/browse/FLUME-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Shreedharan updated FLUME-1164:
------------------------------------
Affects Version/s: (was: v1.2.0)
v1.1.0
Note that this affects v1.1.0.
> Reconsider whether configure() should be called on the same component object
> after a reconfig event
> ---------------------------------------------------------------------------------------------------
>
> Key: FLUME-1164
> URL: https://issues.apache.org/jira/browse/FLUME-1164
> Project: Flume
> Issue Type: Bug
> Components: Configuration
> Affects Versions: v1.1.0
> Reporter: Will McQueen
> Fix For: v1.2.0
>
>
> After a reconfiguration event (config file is modified), the configure()
> method is called on the same component object (unless its name or type has
> changed in the config file). For example, changing the config file to add a
> new property or changing an existing property for source component instance
> r1 will cause the object's configure() method to be called again.
> We should consider whether this should be expected behavior, or if a reconfig
> event should result in instantiating new objects for all components specified
> in the config file.
> For reference, please see:
> FLUME-932
> FLUME-933
> FLUME-1036
> FLUME-1162
--
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