[
https://issues.apache.org/jira/browse/FLUME-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Nagy updated FLUME-1491:
------------------------------------
Attachment: FLUME-1491-2.patch
Prototype for ZooKeeper configuration provider. Summary of changes:
- Moved from flume-ng-node to flume-ng-core (SimpleNodeConfiguration,
ConfigurationProvider, NodeConfiguration, NodeConfigurationAware)
- Changed package of SimpleNodeConfiguration to org.apache.flume.node
- Created org.apache.flume.node.AbstractConfigurationProvider and moved most
getters/setters from AbstractFileConfigurationProvider and loadChannels,
loadSources and loadSinks from PropertiesFileConfigurationProvider
- Created flume-ng-configuration-zookeeper with ZooKeeperConfigurationProvider
(and unit test). It requires a system property called
'zookeeper.connectionstring' which is the connection string used to connect to
ZooKeeper
- Changed Application to load the custom config provider when the
'confprovider' is specified (with the classname)
> Dynamic configuration from Zookeeper watcher
> --------------------------------------------
>
> Key: FLUME-1491
> URL: https://issues.apache.org/jira/browse/FLUME-1491
> Project: Flume
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: v1.2.0
> Reporter: Denny Ye
> Assignee: Denny Ye
> Labels: Zookeeper
> Fix For: v1.3.0
>
> Attachments: FLUME-1491-2.patch
>
>
> Currently, Flume only support file-level dynamic configuration. Another
> frequent usage in practical environment, we would like to manage
> configuration with Zookeeper, and modify configuration from Web UI to stored
> file in Zookeeper.
> Flume should support this method with Zookeeper watcher.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
