vladimirg-db opened a new pull request, #57696: URL: https://github.com/apache/spark/pull/57696
### What changes were proposed in this pull request? Add deterministic ordering to result-sensitive subqueries in `in-limit.sql` that combine `IN` or `NOT IN` with `LIMIT` or `OFFSET`. Regenerate the execution and analyzer golden files. ### Why are the changes needed? Without an ordering, `LIMIT` and `OFFSET` may select different membership values under different physical row orders, making the golden results flaky. Ordering by the projected membership column makes tied rows semantically equivalent. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? `build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite -- -z in-limit.sql"` ### Was this patch authored or co-authored using generative AI tooling? Generated-by: OpenAI Codex (GPT-5) -- 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]
