flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abdullah Ozturk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3923) Unify configuration conventions of the Kinesis producer to the same as the consumer
Date Tue, 07 Jun 2016 08:49:21 GMT

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

Abdullah Ozturk commented on FLINK-3923:
----------------------------------------

I think it is really good idea. Except, I am not sure about overriding the default values
already set by KPL or KCL with our defaults if it has no definite purpose. But, how about
the state of the decision for whether using Amazon licensed libraries or not in Flink? According
to my last knowledge, enhancing these configurations were up to that decision. 

> 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)

Mime
View raw message