Phase I sounds fine. Apache Beam follows semantic versioning and I believe removing the IOs will be a backwards incompatible change unless they were marked experimental which will be a problem for Phase 2.
What is the feasibility of making the V1 transforms wrappers around V2? On Mon, Nov 25, 2019 at 1:46 PM Cam Mach <cammac...@gmail.com> wrote: > Hello Beam Devs, > > I have been working on the migration of Amazon Web Services IO connectors > into the new AWS SDK for Java V2. The goal is to have an updated > implementation aligned with the most recent AWS improvements. So far we > have already migrated the connectors for AWS SNS, SQS and DynamoDB. > > In the meantime some contributions are still going on V1 IOs. So far we > have dealt with those by porting (or asking contributors) to port the > changes into V2 IOs too because we don’t want features of both versions to > be unaligned but this may quickly become a maintenance issue, so we want to > discuss a plan to stop supporting (deprecate) V1 IOs and encourage users to > move to V2. > > Phase I (ASAP): > > - > > Mark migrated AWS V1 IOs as deprecated > - > > Document migration path to V2 > > Phase II (end of 2020): > > - > > Decide a date or Beam release to remove the V1 IOs > - > > Send a notification to the community 3 months before we remove them > - > > Completely get rid of V1 IOs > > > Please let me know what you think or if you see any potential issues? > > Thanks, > Cam Mach > >
