[
https://issues.apache.org/jira/browse/BEAM-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132159#comment-17132159
]
Beam JIRA Bot commented on BEAM-490:
------------------------------------
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.
> Swap to using CoGBK as grouping primitive instead of GBK
> --------------------------------------------------------
>
> Key: BEAM-490
> URL: https://issues.apache.org/jira/browse/BEAM-490
> Project: Beam
> Issue Type: Improvement
> Components: beam-model
> Reporter: Luke Cwik
> Priority: P2
> Labels: backwards-incompatible, portability, stale-P2
>
> The intent is for the semantics of both GBK and CoGBK to be
> unchanged, just swapping their status as primitives.
> CoGBK is a more powerful operator then GBK allowing for two key benefits:
> 1) SDKs are simplified: transforming a CoGBK into a GBK is trivial while the
> reverse is not.
> 2) It will be easier for runners to provide more efficient implementations of
> CoGBK as they will be responsible for the logic which takes their own
> internal grouping implementation and maps it onto a CoGBK.
> This requires the following modifications to the Beam code base:
> 1) Make GBK a composite transform in terms of CoGBK.
> 2) Move the CoGBK from contrib to runners-core as an adapter*. Runners that
> more naturally support GBK can just use this and everything executes exactly
> as before.
> *just like GroupByKeyViaGroupByKeyOnly and UnboundedReadFromBoundedSource
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
