Thanks a lot Cam for bringing this document to the mailing list (I let some comments there). There was a recent proposal doc about supporting async on Beam so you can be interested on taking a look at the evolution of that [1]. It is definitely interesting for the implications for IO authors.
I piggyback a bit this email to make other members of the community aware of the ongoing work by Cam. He has been a contributor for a while in the Java IO front, he contributed the IO for DynamoDB and due to his work there he started working on the update of all the Amazon Web Services (AWS) related IOs (SNS, SQS, etc) to use the new AWS SDK (v2), that’s how he got into the Kinesis migration point, btw AWS IO migration is an ongoing effort so if other people are interested on contributing into this area, do not hesitate to contact him (or me). BEAM-7555 [2] for more info. (Sorry for the ad :P) Ismaël [1] https://lists.apache.org/thread.html/26d0b7b4f89dcc265fd5deb9cdca3f3bc6daa7cdf2fe56e09b5e7a36@%3Cdev.beam.apache.org%3E [2] https://issues.apache.org/jira/browse/BEAM-7555 On Mon, Sep 30, 2019 at 2:02 PM Cam Mach <[email protected]> wrote: > > Hello Beam Dev, > > I have discussed with a couple of Beam dev regarding this topic. We found > something interesting in the new AWS Kinesis SDK and Libraries V2, so like to > propose a design for this migration. > > Here is the design doc: > https://docs.google.com/document/d/1XeIVbiDHBReZY8rEI2OWA3cTEQuaR7RPdwGAup6S1DM > > I would love to hear from you, your feedback and comments > > Thanks, > Cam > >
