You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
SDKs are simplified: transforming a CoGBK into a GBK is trivial while the reverse is not.
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:
Make GBK a composite transform in terms of CoGBK.
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
Imported from Jira BEAM-490. Original Jira may contain additional context.
Reported by: lcwik.
The text was updated successfully, but these errors were encountered:
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:
This requires the following modifications to the Beam code base:
*just like GroupByKeyViaGroupByKeyOnly and UnboundedReadFromBoundedSource
Imported from Jira BEAM-490. Original Jira may contain additional context.
Reported by: lcwik.
The text was updated successfully, but these errors were encountered: