Github user viirya commented on the issue: https://github.com/apache/spark/pull/18968 I'd moved the original check to `CheckAnalysis`. The valid IN subquery should have equal size value expressions and subquery output. If not, we should throw user-facing error. To prevent possible issue brought by optimization rules, the additional check is put in `resolved`. This is not user-facing error. I think we can rely the newly proposed structural integrity check to detect this.
--- 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