shrirangmhalgi commented on issue #56515: URL: https://github.com/apache/spark/issues/56515#issuecomment-4759761375
Thanks for filing the issue @mrjoe7 I reproduced this scenario on current master (5.0.0-SNAPSHOT) using the built-in V2 test catalog with a temp view source that reads from the MERGE target table - the test passes without assertion error. This was fixed by @cloud-fan in [SPARK-54873](https://issues.apache.org/jira/browse/SPARK-54873?jql=project%20%3D%20SPARK%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20assignee%20in%20(EMPTY)%20ORDER%20BY%20created%20DESC) (commit daa21cd2bd4) which simplified V2TableReference resolution and added a CheckAnalysis validation to ensure all V2TableReference nodes are resolved before planning. The fix is present on branch-4.2 and master, but not on branch-4.1. Upgrading to Spark 4.2 should resolve this 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. 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]
