[
https://issues.apache.org/jira/browse/FLINK-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295051#comment-15295051
]
ASF GitHub Bot commented on FLINK-3923:
---------------------------------------
GitHub user aozturk opened a pull request:
https://github.com/apache/flink/pull/2016
[FLINK-3923] [connector-kinesis] Unify configuration conventions of t…
This pull request includes the changes as clearly described in the issue.
[FLINK-3923] Unify configuration conventions of the Kinesis producer to the
same as the consumer
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)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aozturk/flink FLINK-3923
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2016.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2016
----
commit b3f253a016fb3fdd9ecfd1f03ff9313d3f977e3f
Author: Abdullah Ozturk <oztu...@amazon.com>
Date: 2016-05-21T14:38:53Z
[FLINK-3923] [connector-kinesis] Unify configuration conventions of the
Kinesis producer to the same as the consumer
----
> 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
>
> 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)
