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 2019/12/02 13:28:00 UTC

[jira] [Assigned] (FLINK-10190) Unable to use custom endpoint in Kinesis producer

     [ https://issues.apache.org/jira/browse/FLINK-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Metzger reassigned FLINK-10190:
--------------------------------------

    Assignee: Scott Kidder

> 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: Connectors / Kinesis
>    Affects Versions: 1.6.0
>            Reporter: Sergei Poganshev
>            Assignee: Scott Kidder
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)