HeartSaVioR commented on issue #24890: [SPARK-28074][DOC][SS] Document caveats on using multiple stateful operations in single query URL: https://github.com/apache/spark/pull/24890#issuecomment-504240504 > Is it possible to block the scenario(exception) or print warning in such cases? If you meant can we let Spark analyze query and check whether global watermark brings correctness issue for the query, then not sure we can. Instead, Spark could measure number of discarded rows in each stateful operator - that said, #21617 may be reopened - which helps letting end users indicate the issue from their query. I don't think it's sufficient though, as they would recognize while running query and the query would already push incorrect outputs to sink, and they have to stop the query and do non-trivial work (analyze, take workaround) to resolve the issue.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
