+1 Yes, long waiting thing! Makes sense for me since 2+ two years should be quite enough to move to AWS v2 Io connectors. Though, I'd recommend to announce it on user@ as well in advance.
--- Alexey On 2024/12/12 20:25:20 Danny McCormick via dev wrote: > Hey everyone, I've been working on upgrading our Java version of protobuf > to protobuf 4 (also needed to keep many other dependencies up to date). As > part of this, I've found that the AWS v1 KinesisIO [1] is incompatible with > protobuf 4 (on upgrade, tests now hang [2]). Other v1 libraries likely are > incompatible as well. > > These IOs have been deprecated since Beam 2.41.0 (July 2022), with the > message "You are using a deprecated IO for DynamoDB. Please migrate to > module 'org.apache.beam:beam-sdks-java-io-amazon-web-services2'." [3], and > the new libraries have been recommended for longer than that. The > underlying libraries are in maintenance mode, with EOL scheduled for the > end of next year [4]. Rather than trying to find a workaround to patch > these libraries, I'd like to remove them in favor of the non-deprecated > libraries right after next week's release cut. Are there any objections to > this approach? If I don't hear any objections, I will proceed with this > approach next week (draft PR [5]). > > Thanks, > Danny > > [1] > https://github.com/apache/beam/tree/master/sdks/java/io/kinesis/src/main/java/org/apache/beam/sdk/io/kinesis > [2] > https://github.com/apache/beam/actions/runs/12263616473/job/34215568385?pr=33192 > [3] > https://github.com/apache/beam/commit/f5435c0575870062f39575271c0f483117908403 > [4] > https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-java-v1-x-on-december-31-2025/ >
