kennknowles commented on PR #28272: URL: https://github.com/apache/beam/pull/28272#issuecomment-1715736420
Actually each GBK has its own sequence of trigger firings, and when it comes to reshuffle there are two possibilities: 1. The reshuffle does a GBK then explodes it (per its expansion) in which case the sequence of pane indices come from the Reshuffle/always trigger on that GBK. 2. The reshuffle is a semantics "no op" at the PCollection level, in which case the pane indices would be preserved from an upstream aggregation, but reshuffle results in bundles from random upstream keys so they are deceptive. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
