[
https://issues.apache.org/jira/browse/FLINK-8944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476075#comment-16476075
]
ASF GitHub Bot commented on FLINK-8944:
---------------------------------------
Github user tweise commented on the issue:
https://github.com/apache/flink/pull/5992
Looks like we can either leave all the application facing constants as they
are (which might look a bit strange given they refer to old API and we are now
using the new), or we deprecate and duplicate :) If the latter, then I would
suggest to map from old/deprecated to new property keys in a single place and
issue deprecation warning.
> Use ListShards for shard discovery in the flink kinesis connector
> -----------------------------------------------------------------
>
> Key: FLINK-8944
> URL: https://issues.apache.org/jira/browse/FLINK-8944
> Project: Flink
> Issue Type: Improvement
> Reporter: Kailash Hassan Dayanand
> Priority: Minor
>
> Currently the DescribeStream AWS API used to get list of shards is has a
> restricted rate limits on AWS. (5 requests per sec per account). This is
> problematic when running multiple flink jobs all on same account since each
> subtasks calls the Describe Stream. Changing this to ListShards will provide
> more flexibility on rate limits as ListShards has a 100 requests per second
> per data stream limits.
> More details on the mailing list. https://goo.gl/mRXjKh
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
