[
https://issues.apache.org/jira/browse/FLUME-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Shreedharan updated FLUME-991:
-----------------------------------
Description: The idea is to make sure the validation of the configuration
file, with component specific validation takes place, so that configure() will
actually run in a valid configuration (was: Currently the configuration
provider implementation encompasses all the syntactic and structural validation
rules for loading the configuration. Externalizing this functionality to a
library will allow external tools to easily operate on flume configuration
files and be able to help parse and validate these files.)
Summary: Make flume configuration validation component specific at time
rather than at runtime (was: CLONE - Need a library that would allow external
tools to parse and validate flume properties file configuration)
> Make flume configuration validation component specific at time rather than at
> runtime
> -------------------------------------------------------------------------------------
>
> Key: FLUME-991
> URL: https://issues.apache.org/jira/browse/FLUME-991
> Project: Flume
> Issue Type: Task
> Affects Versions: v1.0.0
> Reporter: Hari Shreedharan
> Fix For: v1.1.0
>
>
> The idea is to make sure the validation of the configuration file, with
> component specific validation takes place, so that configure() will actually
> run in a valid configuration
--
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