You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Scott Kidder (JIRA)" <ji...@apache.org> on 2016/07/12 02:32:10 UTC

[jira] [Created] (FLINK-4197) Allow Kinesis Endpoint to be Overridden via Config

Scott Kidder created FLINK-4197:
-----------------------------------

             Summary: 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
             Fix For: 1.0.4


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
(v6.3.4#6332)