[
https://issues.apache.org/jira/browse/FLINK-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372492#comment-15372492
]
ASF GitHub Bot commented on FLINK-4197:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/2227
Hi @skidder, I like the add, I think serious users will definitely need
this.
One thing I'm concerned about is how `CONFIG_AWS_REGION` and
`CONFIG_AWS_ENDPOINT` should co-exist in the configuration properties,
especially when we validate the configuration with
`KinesisConfigUtil#validateConfiguration()`.
The Kinesis consumer requires the user to specify `CONFIG_AWS_REGION`.
I wonder if we need to check for conflicting `CONFIG_AWS_REGION` and
`CONFIG_AWS_ENDPOINT` values, i.e.region is set to "us-east-1", but endpoint is
set to "ap-northeast-1.amazonaws.com".
Also,
What do you think?
> 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
(v6.3.4#6332)
