xi-db opened a new pull request, #52585: URL: https://github.com/apache/spark/pull/52585
### What changes were proposed in this pull request? Spark Connect is a decoupled client-server architecture that allows remote connectivity to Spark clusters using the DataFrame API and unresolved logical plans as the protocol, which is well documented in https://spark.apache.org/docs/latest/spark-connect-overview.html. However, there is a lack of guidance to help users understand the behavioral differences between Spark Classic and Spark Connect and to avoid unexpected behavior. In this PR, a document is added that details the behavioral differences between Spark Connect and Spark Classic, lazy schema analysis and name resolution, and their implications. ### Why are the changes needed? This doc helps users migrating from Spark Classic to Spark Connect to understand the behavioral differences. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? <!-- If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible. If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future. If tests were not added, please describe why they were not added and/or why it was difficult to add. If benchmark tests were added, please run the benchmarks in GitHub Actions for the consistent environment, and the instructions could accord to: https://spark.apache.org/developer-tools.html#github-workflow-benchmarks. --> N/A. ### Was this patch authored or co-authored using generative AI tooling? No. -- 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]
