docs: start Spark 4.1 known-limitations section, seeded with #4199#4202
Merged
mbutrovich merged 2 commits intoapache:mainfrom May 4, 2026
Merged
docs: start Spark 4.1 known-limitations section, seeded with #4199#4202mbutrovich merged 2 commits intoapache:mainfrom
mbutrovich merged 2 commits intoapache:mainfrom
Conversation
…ntry Start a Spark-4.1 "Known Limitations" section on the compatibility guide's spark-versions page, mirroring the existing Spark-4.0 section. First entry documents apache#4199 (parquet-rs rejects Spark's `BOOLEAN + Unknown` encoding for `NullType` columns) with the failure mode and a user-facing workaround so operators hitting the decode-time error have somewhere to land.
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
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.
Which issue does this PR close?
Starts a Spark 4.1 Known Limitations section so operator-facing compatibility issues on the experimental 4.1 profile have a home. First entry seeds it with #4199.
Rationale for this change
Spark 4.1 support is experimental and we're discovering a handful of limitations as we work through the 4.1 CI failures. Some of them are real user-visible gaps (not just test-side plumbing) and deserve a visible entry in the compatibility guide so users who hit them can self-diagnose.
What changes are included in this PR?
Additional 4.1 limitations will be appended to the section as they are characterised.
How are these changes tested?
Docs-only change; rendered locally to confirm markdown formatting.