You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2021/03/08 17:06:00 UTC
[jira] [Commented] (BEAM-7555) Migrate AWS IOs to AWS SDK for Java
2
[ https://issues.apache.org/jira/browse/BEAM-7555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297535#comment-17297535 ]
Ismaël Mejía commented on BEAM-7555:
------------------------------------
We still need to solve two issues:
* Check that all functionality of AWSv1 is covered
* Decide what to do with the unsupported write of Kinesis in AWSv2
> Migrate AWS IOs to AWS SDK for Java 2
> -------------------------------------
>
> Key: BEAM-7555
> URL: https://issues.apache.org/jira/browse/BEAM-7555
> Project: Beam
> Issue Type: New Feature
> Components: io-java-aws
> Reporter: Ismaël Mejía
> Priority: P3
>
> [AWS SDK for Java 2 was released|https://github.com/aws/aws-sdk-java-v2/blob/master/docs/LaunchChangelog.md] last october and has many interesting features including cleaner APIs and support for HTTP client sharing and HTTP/2 in some APIs. So worth checking a migration path for AWS IOs.
> Due to incompatibility APIs + Binary objects the best strategy is to incrementally migrate each existing IO into a new module e.g. `sdks/java/io/amazon-web-services2` and then start migrating services one by one. Once we achieve feature completeness we can deprecate the IOs based in the 'old' AWS SDK for Java version 1 and eventually remove them once the other are in a good shape.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)