junyuc25 opened a new pull request, #44211:
URL: https://github.com/apache/spark/pull/44211
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'core/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other
DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
As Spark is moving to 4.0, one of the major improvement is to upgrade AWS
SDK to v2.
Currently other than directly using AWS SDKv1 codes, the Spark Kinesis
connector is also
using on these libraries that depends on SDKv1:
* Kinesis Client Library (KCL) allows users to easily consume and process
data from Amazon Kinesis
* Kinesis Producer Library (KPL) allows users to create reliable and
efficient message producers for Amazon Kinesis
The main purpose of this PR is to upgrading AWS SDK to v2 for the Spark
Kinesis
conector. While the changes includes upgrading AWS SDK and KCL to v2, we
will not
upgrade KPL because it has not yet been migrated to SDKv2.
* Parent Jira: parent Jira:
https://issues.apache.org/jira/browse/SPARK-44124.
* Previous PR to setup Kinesis tests in Github Actions:
https://github.com/apache/spark/pull/43736
* Previous stale PR: https://github.com/apache/spark/pull/42581
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
As the GA of AWS SDK v2, the SDKv1 has entered maintenance mode where its
future
release are only limited to address critical bug and security issues. More
details about the SDK maintenance policy can be found here. To keep Spark’s
dependent softwares up to date, we should consider upgrading the SDK to v2.
These changes could keep Spark Kinesis connector up to date, and enable
users to
receive continuous support from the above libraries.
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description and/or an example to show the
behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Spark versions or within the unreleased branches such as master.
If no, write 'No'.
-->
Yes. With this change, the Spark Kinesis connector will no longer work with
SDKv1.
Any applications that are running with previous version of Spark Kinesis
connector
would require update before migrating to Spark 4.0.
AWS SDKv2 and KCLv2 contain several major changes
that are not backward compatible with their previous versions. And some
public classes
in the module (i.e. KinesisInputDStream) are using one of these breaking
changes. Thus
these user-facing classes require updates as well.
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
If benchmark tests were added, please run the benchmarks in GitHub Actions
for the consistent environment, and the instructions could accord to:
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
-->
*
### Was this patch authored or co-authored using generative AI tooling?
<!--
If generative AI tooling has been used in the process of authoring this
patch, please include the
phrase: 'Generated-by: ' followed by the name of the tool and its version.
If no, write 'No'.
Please refer to the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
-->
No
--
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: reviews-unsubscr...@spark.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
