Yes, good point about asking on Twitter, Ahmet!
> On 19 Mar 2022, at 04:14, Ahmet Altay <al...@google.com> wrote:
>
> Moritz, thank you for your thoughtful approach.
>
> +1 to Alexey's suggestion. One minor additional suggestion, in addition to
> asking on user@ you can also ask on beam's twitter. Historically we were able
> to reach more users on Twitter compared to the user list.
>
> On Fri, Mar 18, 2022 at 10:01 AM Alexey Romanenko <aromanenko....@gmail.com
> <mailto:aromanenko....@gmail.com>> wrote:
> First of all - many thanks for your work to make "amazon-web-services2”
> stable and up-to-date with already supported features of v1 version.
>
> +1 to deprecate all "amazon-web-services” (AWS SDK v1) IOs and recommend to
> use only v2 API, but before I’d suggest to ask people on user@ if they have
> some specific reasons to delay it or any other feedback on this that we can
> miss.
>
> Regarding the major releases and removing deprecated code, IIUC, we agreed
> that deprecated code should stay (but not required to be supported), at
> least, 3 minor releases (x.y) and it can be finally deleted if we won’t
> discover any regressions or user complains till then.
>
> On the other hand, Beam 3.0 should be the next major release but I’m not sure
> it’s even on distant horizon for now since this is topic that we didn’t
> discuss for a long time (maybe it’s a good time to come back to this).
>
> —
> Alexey
>
>
>> On 18 Mar 2022, at 12:19, Moritz Mack <mm...@talend.com
>> <mailto:mm...@talend.com>> wrote:
>>
>> Dear all,
>>
>> I’d like to bring up an old discussion again [1].
>> Currently we have two different versions of AWS IO connectors in Beam for
>> the Java SDK:
>> amazon-web-services [2] and kinesis [3] for the AWS Java SDK v1
>> amazon-web-services2 (including kinesis) [4] for the AWS Java SDK v2
>>
>> Maintaining two different versions is obviously painful, so working towards
>> sunsetting the earlier v1 is important.
>> Though, historically v1 had (and likely still has) the broader adoption due
>> to a lack of awareness, but also certainly a lack of features in v2.
>>
>> I’ve recently focused a lot on preparing the deprecation of v1, specifically:
>> implementing all outstanding features in v2 (above all write support for
>> KinesisIO) [5]
>> full integration test coverage for all IOs in v2 (using localstack), but
>> also improved general test coverage & quality
>> more consistent configuration and tons of bug fixes
>>
>> Where I’m looking for general feedback is how to proceed next:
>> Deprecate (IO classes of) v1 immediately to force awareness of v2 with the
>> next release?
>> Just recommend v2 IOs over v1 IOs on the website [6] to hopefully push
>> adoption and gather more feedback before deprecating v1?
>>
>> Any thoughts or recommendations?
>>
>> Also, looking further ahead … is there a major release planned for Beam that
>> would allow to remove such deprecations?
>>
>> Thanks so much,
>> Moritz
>>
>>
>> [1] https://lists.apache.org/thread/b4opwr3x1rr63732b5j7f47r2bobq6h0
>> <https://lists.apache.org/thread/b4opwr3x1rr63732b5j7f47r2bobq6h0>
>> [2]
>> https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services
>> <https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services>
>> [3] https://github.com/apache/beam/tree/master/sdks/java/io/kinesis
>> <https://github.com/apache/beam/tree/master/sdks/java/io/kinesis>
>> [4]
>> https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services2
>> <https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services2>
>> [5] https://issues.apache.org/jira/browse/BEAM-13174
>> <https://issues.apache.org/jira/browse/BEAM-13174>
>> [6] https://issues.apache.org/jira/browse/BEAM-14125
>> <https://issues.apache.org/jira/browse/BEAM-14125>
>>
>> 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/>
