fix: correct user guide URL in compatibility fallback messages#4854
Merged
Conversation
coderfender
approved these changes
Jul 7, 2026
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?
Closes #4851.
Rationale for this change
Fallback messages emitted in query plans (and the scaladoc on
SupportLevel) link tohttps://datafusion.apache.org/comet/user-guide/compatibility.html. After the user guide documentation was reorganized under a versionedlatest/path, the compatibility guide moved from a single page to a directory, so the old link is stale. The configured redirect (user-guide/compatibility.html->latest/compatibility.htmlindocs/source/conf.py) also no longer resolves because the target is now a directory rather than an.htmlfile.What changes are included in this PR?
Update the compatibility guide URL used in fallback messages and scaladoc to the current canonical location:
https://datafusion.apache.org/comet/user-guide/latest/compatibility/index.htmlThis matches how the compatibility guide is linked elsewhere in the docs (for example
docs/source/about/gluten_comparison.md).Only the compatibility guide link is changed. The tuning guide link still redirects correctly because that page remained a single file.
How are these changes tested?
The changes are limited to documentation URL string literals. The updated URL was verified to return HTTP 200 on the published documentation site.