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

Danny Cranmer commented on FLINK-28978:
---------------------------------------

* Merged commit 
[{{05bd634}}|https://github.com/apache/flink/commit/05bd63499358b589f2954b1822e68f43b5158cc1]
 into apache:release-1.14
 * Merged commit 
[{{a42e737}}|https://github.com/apache/flink/commit/a42e7373f79017ee4fffd1af5d61e25999b4038b]
 into apache:master

> Kinesis connector doesn't work for new AWS regions
> --------------------------------------------------
>
>                 Key: FLINK-28978
>                 URL: https://issues.apache.org/jira/browse/FLINK-28978
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kinesis
>    Affects Versions: 1.13.6, 1.14.5, 1.15.1
>            Reporter: Hong Liang Teoh
>            Assignee: Hong Liang Teoh
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0, 1.15.2, 1.14.6
>
>
> The current validation in the Kinesis connector checks that the AWS Region 
> string specified is present in the {{Regions}} enum attached in the {{{}AWS 
> SDK{}}}. This is not desirable because every time AWS launches a new region, 
> we will have to update the AWS SDK shaded into the connector. 
> We want to change it such that we validate the shape of the string, allowing 
> for future AWS Regions. 
>  
> Current list of regions:
> ap-south-1, eu-south-1, us-gov-east-1, ca-central-1, eu-central-1, us-west-1, 
> us-west-2, af-south-1, eu-north-1, eu-west-3, eu-west-2, eu-west-1, 
> ap-northeast-3, ap-northeast-2, ap-northeast-1, me-south-1, sa-east-1, 
> ap-east-1, cn-north-1, us-gov-west-1, ap-southeast-1, ap-southeast-2, 
> ap-southeast-3, us-iso-east-1, us-east-1, us-east-2, cn-northwest-1, 
> us-isob-east-1, aws-global, aws-cn-global, aws-us-gov-global, aws-iso-global, 
> aws-iso-b-global



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to