[jira] [Commented] (FLINK-18536) [Kinesis][EFO] Configuration deserialisation and validation

["Danny Cranmer (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-18536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154317#comment-17154317 ] 

Danny Cranmer commented on FLINK-18536:
---------------------------------------

Hey [~tzulitai], I have split out the configuration work as [~heywxl] would like to contribute this change. Can you please assign this Jira to [~heywxl]?

> [Kinesis][EFO] Configuration deserialisation and validation
> -----------------------------------------------------------
>
>                 Key: FLINK-18536
>                 URL: https://issues.apache.org/jira/browse/FLINK-18536
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Danny Cranmer
>            Priority: Major
>             Fix For: 1.12.0
>
>
> *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|https://cwiki.apache.org/confluence/display/FLINK/FLIP-128%3A+Enhanced+Fan+Out+for+AWS+Kinesis+Consumers] 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()}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)