[FLUME-3336] Add support for configuring with YAML

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.9.0
• Component/s: Configuration
• Assignee: Ralph Goers
• Reporter: Ralph Goers
• Created: 24/May/19 04:48
• Updated: 08/Oct/22 06:42
• Resolved: 08/Oct/22 06:42

Description

As part of FLUME-3335 the configuration classes need to be split so that more configuration options are supported and polling is separated from parsing the configuration. As a consequence of this split it is straightforward to add support for JSON configurations. The only hitch is that the property syntax has some peculiarities that don't map to YAML very well and since properties are so ingrained into the Flume configuration mechanism the YAML basically has to be translated to the same Map structure as the properties:

1. JSON doesn't allow a property to be a parent of other nodes and also have a value.
2. It doesn't make sense to have sources, channels, and sinks elements that name the various entities in the configuration since they are being directly declared in the YAML,

However, the JSON syntax will be much easier to follow then the existing property syntax.