egalpin commented on PR #17112: URL: https://github.com/apache/beam/pull/17112#issuecomment-1092870262
So was the conclusion that the issue of holding back the watermark for in flight data being processed as part of a bundle was specific to FlinkRunner? i.e. other runners do in fact hold back the watermark during the processing of a bundle? I traced the threads and related PRs to the best of my ability, but I wasn't clear on the resolution pertaining to watermark handling during bundles (whereas the thread and PR dealt primarily with timers). Thanks! -- 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]
