[SPARK-53882][CONNECT][DOCS] Add documentation comparing behavioral differences between Spark Connect and Spark Classic #52585
+423
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xi-db
changed the title
xi-db
changed the title
hvanhovell
reviewed
Oct 13, 2025
docs/spark-connect-gotchas.md
Outdated
| limitations under the License. | ||
| --- | ||
|
|
||
| The comparison highlights key differences between Spark Connect and Spark Classic in terms of execution and analysis behavior. While both utilize lazy execution for transformations, Spark Connect emphasizes deferred schema analysis, introducing unique considerations like temporary view handling and UDF evaluation. The guide outlines common gotchas and provides strategies for mitigation. |
There was a problem hiding this comment.
, Spark Connect emphasizes deferred schema analysis -> , Spark Connect also defers analysis/, Spark Connect analyzes lazily
try to avoid too much indirection.
There was a problem hiding this comment.
Yes, done, and updated several other places as well.
hvanhovell
reviewed
Oct 13, 2025
docs/spark-connect-gotchas.md
Outdated
|
|
||
| **When does this matter?** These differences are particularly important when migrating existing code from Spark Classic to Spark Connect, or when writing code that needs to work with both modes. Understanding these distinctions helps avoid unexpected behavior and performance issues. | ||
|
|
||
| **Note:** The examples in this guide use Python, but the same principles apply to Scala and Java. |
There was a problem hiding this comment.
Please be a champ and also add Scala/Java
There was a problem hiding this comment.
Good point, I've just added Scala examples.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
N/A.
Was this patch authored or co-authored using generative AI tooling?
No.