You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sergei Poganshev (JIRA)" <ji...@apache.org> on 2018/08/21 13:56:00 UTC
[jira] [Created] (FLINK-10190) Unable to use custom endpoint in
Kinesis producer
Sergei Poganshev created FLINK-10190:
----------------------------------------
Summary: Unable to use custom endpoint in Kinesis producer
Key: FLINK-10190
URL: https://issues.apache.org/jira/browse/FLINK-10190
Project: Flink
Issue Type: Bug
Components: Kinesis Connector
Affects Versions: 1.6.0
Reporter: Sergei Poganshev
There's a check in [KinesisConfigUtil|https://github.com/apache/flink/blob/7d034d4ef6986ba5ccda6f5e8c587b8fdd88be8e/flink-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/util/KinesisConfigUtil.java#L269] that validates the fact that either AWS_REGION or AWS_ENDPOINT is specified (not both), while Kinesis producer requires a region in any case (even with custom endpoint).
Also the error message for that validation outputs AWS_REGION twice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)