cloud-fan commented on PR #48820: URL: https://github.com/apache/spark/pull/48820#issuecomment-2473143992
@ueshin After thinking more about it, I think the new test case should pass instead of fail. My opinion is: 1. In SQL, users can just write un-qualified column names to reference the outer plan. We should allow the same in DataFrame API. 2. Eventually, Spark Connect is the main API and DataFrame is always lazy. Then `.outer()` is only needed to avoid ambiguity when there are column name conflicts, to explicitly reference the outer plan only. -- 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]
