[ https://issues.apache.org/jira/browse/FLINK-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-4195: ---------------------------------- Labels: auto-deprioritized-major stale-minor (was: auto-deprioritized-major) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Dedicated Configuration classes for Kinesis Consumer / Producer > --------------------------------------------------------------- > > Key: FLINK-4195 > URL: https://issues.apache.org/jira/browse/FLINK-4195 > Project: Flink > Issue Type: Improvement > Components: Connectors / Common, Connectors / Kinesis > Affects Versions: 1.1.0 > Reporter: Tzu-Li (Gordon) Tai > Priority: Minor > Labels: auto-deprioritized-major, stale-minor > > 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 (v8.20.1#820001)