[
https://issues.apache.org/jira/browse/BEAM-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131636#comment-17131636
]
Beam JIRA Bot commented on BEAM-4372:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Need an undeprecated Reshuffle transform
> ----------------------------------------
>
> Key: BEAM-4372
> URL: https://issues.apache.org/jira/browse/BEAM-4372
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Raghu Angadi
> Priority: P2
> Labels: stale-P2
>
> {{Reshuffle}} transform is a convenient wrapper around GBK. It preserves user
> windowing correctly which is not always obvious for users. It usage has grown
> over many months since it was deprecated as it makes it easier for potential
> incorrect/unportable use of GroupByKey semantics. See [dev
> thread|https://lists.apache.org/thread.html/820064a81c86a6d44f21f0d6c68ea3f46cec151e5e1a0b52eeed3fbf@%3Cdev.beam.apache.org%3E]
> for more discussion.
>
> There is a broad agreement we do need a transform that is meant for its
> common used purpose in user pipeline : to control parallelism (e.g. to
> control connections to a DB).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
