HeartSaVioR commented on PR #48570: URL: https://github.com/apache/spark/pull/48570#issuecomment-2425434238
The issue is a sort of correctness/data loss (as watermark advances faster than it should be), but it's not triggered by "current" optimization rules (by luck - filter pushdown pushes the filter "below EventTimeWatermark node" and hence prune filters do not prune EventTimeWatermark node). Since I don't see how this could happen in existing Spark versions (might not be 100% safe), I'd suggest not to port this back. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
