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 Wed, 13 Jul 2016 17:08:20 GMT

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

ASF GitHub Bot commented on FLINK-4197:

Github user asfgit closed the pull request at:


> 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