[
https://issues.apache.org/jira/browse/FLINK-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger resolved FLINK-4197.
-----------------------------------
Resolution: Fixed
Assignee: Scott Kidder
Fix Version/s: (was: 1.0.4)
1.1.0
Resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/bc3a96f5
Thank you for the contribution [~skidder].
> 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
> Assignee: Scott Kidder
> Priority: Minor
> Labels: easyfix
> Fix For: 1.1.0
>
> 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
(v6.3.4#6332)
