davidcavazos commented on pull request #15479: URL: https://github.com/apache/beam/pull/15479#issuecomment-923088798
@aaltay I know it adds more complication and concepts and for the sample data it's not required, but I think it would be a good practice since someone might copy-paste this example to start a new runner, without even being aware that they might need a reshuffle for things to autoscale properly. How about we make the note more explicit saying that it is useful for runners that do fusion? @robertwb those warnings were introduced, I think in 2.30 or sometime around that version. It's now part of the standard running procedure and there's no way to remove them that I'm aware of. We could get rid of them by manually editing the code cell outputs (but it's very manual and error prone), or find a way to redirect stderr to /dev/null or something like that, but it might look hacky during the notebook setup. -- 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]
