Agreed that it should be undeprecated, many users are getting confused by this. I know that some people are working on a replacement for at least one of its use cases (RequiresStableInput), but the use case of breaking fusion is, as of yet, unaddressed, and there's not much to be gained by keeping it deprecated.
On Fri, May 18, 2018 at 7:45 AM Raghu Angadi <rang...@google.com> wrote: > I am interested in more clarity on this as well. It has been deprecated > for a long time without a replacement, and its usage has only grown, both > within Beam code base as well as in user applications. > > If we are certain that it will not be removed before there is a good > replacement for it, can we undeprecate it until there are proper plans for > replacement? > > On Fri, May 18, 2018 at 7:12 AM Ismaël Mejía <ieme...@gmail.com> wrote: > >> I saw in a recent thread that the use of the Reshuffle transform was >> recommended to solve an user issue: >> >> >> https://lists.apache.org/thread.html/87ef575ac67948868648e0a8110be242f811bfff8fdaa7f9b758b933@%3Cdev.beam.apache.org%3E >> >> I can see why it may fix the reported issue. I am just curious about >> the fact that the Reshuffle transform is marked as both @Internal and >> @Deprecated in Beam's SDK. >> >> Do we have some alternative? So far the class documentation does not >> recommend any replacement. >> >
