nuno-c-afonso opened a new pull request #17966:
URL: https://github.com/apache/flink/pull/17966
<!--
## Contribution Checklist
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes. You can set up Azure Pipelines CI to do that following [this
guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
-->
## What is the purpose of the change
- The `flink-connector-kinesis` connector contains AWS utilities that could
be re-used across other connectors that interact with other AWS services
- This changes moves such utilities to a common connector
(`flink-connector-aws-common`) that can be used directly by other connectors
## Brief change log
- Added `flink-connector-aws-common`, which is a new module that contains
AWS utilities extracted from `flink-connector-kinesis`
## Verifying this change
This change added tests and can be verified as follows:
- Tests for AWS utilities that were part of `flink-connector-kinesis` are
replicated into `flink-connector-aws-common`
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): yes
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
