You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/05/27 20:39:13 UTC
[jira] [Comment Edited] (FLINK-3923) Unify configuration
conventions of the Kinesis producer to the same as the consumer
[ https://issues.apache.org/jira/browse/FLINK-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304731#comment-15304731 ]
Robert Metzger edited comment on FLINK-3923 at 5/27/16 8:38 PM:
----------------------------------------------------------------
This has been resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/23d1cba7 and http://git-wip-us.apache.org/repos/asf/flink/commit/fc6dc487
was (Author: rmetzger):
This has been resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/23d1cba7
> 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)