Hi,
After some thinking about it, I may have found out the reason why not to
expose EventTimeStatsAccum as a named accumulator. The reason is that it's
an internal part of how event-time watermark works and should not be
exposed via web UI as much as if it was part of a Spark app (the web UI is
Hi,
I'm curious why EventTimeStatsAccum is not a named accumulator (not to
mention SQLMetric) so the event-time watermark could be monitored in web UI?
I've changed the code for EventTimeWatermarkExec physical operator to
register EventTimeStatsAccum as a named accumulator and the values are
