[SPARK-50814][DOCS] Remove unused SQL error pages #49486
Closed
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
Contributor
Author
|
cc @MaxGekk as I believe you have recently reviewed similar doc PRs. |
MaxGekk
approved these changes
Jan 15, 2025
Member
|
+1, LGTM. Merging to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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?
Remove standalone SQL error pages that were made obsolete by the work completed in #44971.
Also fix the formatting of the error message for
QUERY_ONLY_CORRUPT_RECORD_COLUMN, since it was incorrect and overflowing the table cell it belongs to.Why are the changes needed?
These error pages are either already captured completely in
common/utils/src/main/resources/error/error-conditions.json, or are obsolete and not needed (and are not being rendered in the documentation output anyway).The formatting of
QUERY_ONLY_CORRUPT_RECORD_COLUMNbefore and after:Does this PR introduce any user-facing change?
Yes, documentation formatting.
How was this patch tested?
Built the docs locally and reviewed them in my browser.
Was this patch authored or co-authored using generative AI tooling?
No.