docs: split compatibility guide into multiple pages#4055
Merged
andygrove merged 21 commits intoapache:mainfrom Apr 23, 2026
Merged
docs: split compatibility guide into multiple pages#4055andygrove merged 21 commits intoapache:mainfrom
andygrove merged 21 commits intoapache:mainfrom
Conversation
…ity-guide # Conflicts: # docs/source/user-guide/latest/compatibility.md
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?
N/A, documentation restructuring.
Rationale for this change
The compatibility guide had grown into a single long page mixing scans, expressions, operators, regex, floating-point semantics, and the cast support matrix. Splitting it into topic-focused pages under
compatibility/makes each area easier to find and to extend as new notes accumulate.We also had some parquet scan compatibility docs in the contributor guide, so I moved those into the the user guide as well as part of the restructure.
This is also a step towards generating the expression documentation direct from code.
What changes are included in this PR?
Split into pages.
Separate page per expression category.
How are these changes tested?
Manually