[GitHub] [beam] kennknowles commented on issue #23379: [Feature Request]: Expose TimerStateInternals.currentOutputWatermarkTime to allow for DoFns to handle elements behind the watemark differently

[GitBox <gi...@apache.org>]

kennknowles commented on issue #23379:
URL: https://github.com/apache/beam/issues/23379#issuecomment-1259875113

   Just to clarify definitions, these days _late_ = element arriving for aggregation after the watermark has exceeded the end of window for that aggregation. Is there a reason that processing late panes is not sufficient here?
   
   My main concern is increasingly directly basing the output of a transform on nondeterministic inputs will break any invariants we might hope for. Like mostly we want code to not be sensitive to this, or to be sensitive to it in well-behaved ways.


-- 
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

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