Tzu-Li (Gordon) Tai created FLINK-4195:
------------------------------------------
Summary: Dedicated Configuration classes for Kinesis Consumer /
Producer
Key: FLINK-4195
URL: https://issues.apache.org/jira/browse/FLINK-4195
Project: Flink
Issue Type: Sub-task
Reporter: Tzu-Li (Gordon) Tai
While fixing FLINK-4170, I feel that configuration and default value setting &
validation is quite messy and unconsolidated for the current state of the code,
and will likely become worse as more configs grow for the Kinesis connector.
I propose to have a dedicated configuration class (instead of only Java
properties) along the lines of Flink's own {{Configuration}}, so that the usage
pattern is alike. There will be separate configuration classes for
{{FlinkKinesisConsumerConfig}} and {{FlinkKinesisProducerConfig}}.
[~uce] [~rmetzger] What do you think? This will break the interface, so if
we're to change this, I'd prefer to fix it along with FLINK-4170 for Flink 1.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)