flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4197) Allow Kinesis Endpoint to be Overridden via Config
Date Tue, 12 Jul 2016 15:11:20 GMT

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

ASF GitHub Bot commented on FLINK-4197:

Github user tzulitai commented on a diff in the pull request:

    --- Diff: docs/apis/streaming/connectors/kinesis.md ---
    @@ -299,3 +299,41 @@ Otherwise, the returned stream name is used.
     Other optional configuration keys can be found in `KinesisConfigConstants`.
    +### Using non-AWS Kinesis Endpoints
    +It is sometimes desirable to have Flink operate as a consumer or producer against a non-AWS
Kinesis endpoint such as kinesalite; this is especially useful when performing functional
testing of a Flink application. The AWS endpoint that would normally be inferred by the AWS
region set in the Flink configuration must be overriden via a configuration property.
    +To override the AWS endpoint, set the `CONFIG_AWS_ENDPOINT` property in the Flink configuration,
in addition to the `CONFIG_AWS_REGION` required by Flink. Although the region is required,
it will not be used to determine the AWS endpoint URL.
    --- End diff --
    Previous content in the documentation always have the `KinesisConfigConstants.*` prefix
when mentioning config keys. Let's keep consistency with that.

> Allow Kinesis Endpoint to be Overridden via Config
> --------------------------------------------------
>                 Key: FLINK-4197
>                 URL: https://issues.apache.org/jira/browse/FLINK-4197
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kinesis Connector
>    Affects Versions: 1.0.3
>            Reporter: Scott Kidder
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 1.0.4
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> I perform local testing of my application stack with Flink configured as a consumer on
a Kinesis stream provided by Kinesalite, an implementation of Kinesis built on LevelDB. This
requires me to override the AWS endpoint to refer to my local Kinesalite server rather than
reference the real AWS endpoint. I'd like to add a configuration property to the Kinesis streaming
connector that allows the AWS endpoint to be specified explicitly.
> This should be a fairly small change and provide a lot of flexibility to people looking
to integrate Flink with Kinesis in a non-production setup.

This message was sent by Atlassian JIRA

View raw message