kennknowles commented on issue #23379: URL: https://github.com/apache/beam/issues/23379#issuecomment-1263783149
I want to be clear that I think the general pattern here is valuable and I would like to do it a non-hacky way. We know that it works with state & timers by buffering and emitting with a watermark timer, right? We do already let users observe the input watermark approximately via event time timers, and that let's you approximately observe the output watermark from upstream transforms. So I'm not totally opposed to exposing it. But it is a pretty major design decision that needs thought. Probably too much for a feature request comment thread and needing some document exploring possible pitfalls and what the requirements are for it to not allow semantic weirdness, send to dev@ list? -- 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]
