Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/17540
The new test failures are caused by a check I inserted. Moving where
`withNewExecutionId` gets called could result in missing SQL queries in the UI,
so anywhere I'm replacing `withNewExecutionId` with `checkSQLExecutionId` that
will cause tests (and only tests) to fail. That way, we can catch all of the
call stacks that should have it.
This caught problems in SQL command execution and I've added a patch to fix
it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
