[FLUME-1051] Configuration System

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Incomplete
• Affects Version/s: 1.0.0
• Assignee: Unassigned
• Reporter: Hari Shreedharan
• Created: 27/Mar/12 06:00
• Updated: 30/Oct/14 03:58
• Resolved: 29/Oct/14 19:43

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

Issue Links

• is a clone of: FLUME-991 Make flume configuration validation component specific at time rather than at runtime

Sub-Tasks

• Core configuration component: Resolved
• Basic SourceConfiguration: Resolved
• Basic ChannelConfiguration: Resolved
• Basic SinkConfiguration: Resolved
• AvroSource configuration: Closed
• AvroSink configuration: Closed
• Exec source configuration: Closed
• failover sink configuration: Closed
• Hdfs sink configuration: Closed
• jdbc channel configuration: Closed
• Memory Channel configuration: Closed
• Miscellanous changes related to imports and minor changes related to config changes: Closed
• Channel selector configuration: Closed
• netcat source configuration: Resolved
• PseudoTxnMemoryChannel configuration: Closed
• RollingFileSink configuration: Closed
• syslog source configuration: Closed
• FileChannel configuration: Closed