You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 16:35:11 UTC

[GitHub] [beam] kennknowles opened a new issue, #18212: Consider a hint ParDo.withHighFanout()

kennknowles opened a new issue, #18212:
URL: https://github.com/apache/beam/issues/18212

   I'm finding myself again and again suggesting users on StackOverflow to insert fusion breaks after high-fanout ParDo's.
   
   I think we should just implement this as a hint on ParDo and MapElements transforms, like we have on GroupByKey.fewKeys() or Combine.withHotKeyFanout().
   
   E.g.: c.apply(ParDo.of(some high-fanout DoFn).withHighFanout()), and a runner that implements fusion could decide to insert a runner-specific fusion break. This somewhat sidesteps the issues in https://issues.apache.org/jira/browse/BEAM-730 and https://lists.apache.org/thread.html/ac34c9ac665a8d9f67b0254015e44c59ea65ecc1360d4014b95d3b2e@%3Cdev.beam.apache.org%3E because every runner can decide how to do the right thing, or is free to ignore the hint.
   
   Imported from Jira [BEAM-1234](https://issues.apache.org/jira/browse/BEAM-1234). Original Jira may contain additional context.
   Reported by: jkff.


-- 
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: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org