[FLINK-18536] [Kinesis][EFO] Configuration deserialisation and validation

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.0
• Component/s: Connectors / Kinesis
• Labels: pull-request-available
• Assignee: roland
• Reporter: Danny Cranmer
• Created: 09/Jul/20 08:18
• Updated: 12/Oct/20 01:50
• Resolved: 04/Sep/20 06:55

Description

Background
EFO record consumption has configuration properties that are available to the connector via a properties map. The connector must deserialise (where applicable) these properties and validate they are correct.

Scope

• See FLIP for possible configuration options
• Validate the configuration, see KinesisConfigUtil::validateConsumerConfiguration for existing validation routines
• Provide a deserialisation mechanism to allow other EFO components to access properties without having to parse from string:
  • Suggest we create a new config class, FanOutProperties that accepts a Properties map and provides convenience methods, for example getConsumerName()

Issue Links

• links to: GitHub Pull Request #12920
• links to: GitHub Pull Request #13015