[ https://issues.apache.org/jira/browse/FLINK-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318272#comment-15318272 ]
Tzu-Li (Gordon) Tai commented on FLINK-3923: -------------------------------------------- The consumer isn't using the KCL at the moment, so default overriding wouldn't be a problem. As for KPL in the producer, I've heard from Robert that he's already talked with Amazon and came up with some conclusions. He's probably still a bit busy early this week, should update with the conclusions soon. > Unify configuration conventions of the Kinesis producer to the same as the > consumer > ----------------------------------------------------------------------------------- > > Key: FLINK-3923 > URL: https://issues.apache.org/jira/browse/FLINK-3923 > Project: Flink > Issue Type: Sub-task > Components: Kinesis Connector, Streaming Connectors > Affects Versions: 1.1.0 > Reporter: Robert Metzger > Assignee: Abdullah Ozturk > Fix For: 1.1.0 > > > Currently, the Kinesis consumer and producer are configured differently. > The producer expects a list of arguments for the access key, secret, region, > stream. The consumer is accepting properties (similar to the Kafka connector). > The objective of this issue is to change the producer so that it is also > using a properties-based configuration (including an input validation step) -- This message was sent by Atlassian JIRA (v6.3.4#6332)