+1

Thanks, David
________________________________
From: Alexey Romanenko <aromanenko....@gmail.com>
Sent: 26 April 2022 18:17
To: user@beam.apache.org <user@beam.apache.org>
Subject: Re: [SURVEY] Deprecation of Beam AWS IOs v1 (Java)

+1 to deprecate AWS Java SDK v1 connectors in the next Beam release.

—
Alexey

On 26 Apr 2022, at 18:51, Moritz Mack 
<mm...@talend.com<mailto:mm...@talend.com>> wrote:

Hi Beam AWS user,

as you might know, there’s currently two different versions of AWS IO 
connectors in Beam for the Java SDK:

  *   amazon-web-services  [1] and kinesis [2] for the AWS Java SDK v1
  *   amazon-web-services2 (including kinesis) [3] for the AWS Java SDK v2


With the recent release of Beam 2.38.0 [4] amazon-web-services2 has reached 
feature parity with version 1 and we encourage users to give it a try if you 
haven’t done so.

I’m reaching out to see if there’s any blockers, difficulties or other 
obstacles preventing users from migrating to version 2.

Maintaining multiple versions of the same IOs is obviously painful.
Based on your feedback, we hope to then deprecate the earlier version with one 
of the next few Beam releases.

Best,
Moritz

[1] https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services
[2] https://github.com/apache/beam/tree/master/sdks/java/io/kinesis
[3] https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services2
[4] https://beam.apache.org/blog/beam-2.38.0/



As a recipient of an email from Talend, your contact personal data will be on 
our systems. Please see our privacy notice.<https://www.talend.com/privacy/>




----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal 
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on 
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------

Reply via email to