[SPARK-58679][DOCS] Fix typos and grammar in the SQL name resolution reference doc - #57882
Open
uros-b wants to merge 1 commit into
Open
[SPARK-58679][DOCS] Fix typos and grammar in the SQL name resolution reference doc#57882uros-b wants to merge 1 commit into
uros-b wants to merge 1 commit into
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
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?
Fixes nine spelling and grammar errors in
docs/sql-ref-name-resolution.md:precendecetoprecedenceImplicttoImplicitSuccesssfultoSuccessfulraise a AMBIGUOUS_COLUMN_OR_FIELDtoraise an ...An fully qualifiedtoA fully qualifiedtakes precedenttotakes precedenceColumns and parameter wintoColumns and parameters wina column in table referencetoa column in a table referencetakes precedence, over a lateral column aliasWhy are the changes needed?
Most of these are proven wrong by the same file writing the phrase correctly elsewhere: it already has
raise an AMBIGUOUS_COLUMN_OR_FIELDtwice,a column name in a table reference, the adjacentA partially qualifiedandAn unqualified, andtakes precedence overseven times without a comma.takes precedentis the function-resolution example where a temporary function wins over a persistent one, soprecedenceis what was meant.Does this PR introduce any user-facing change?
No, other than the corrected documentation.
How was this patch tested?
Documentation only. No error condition name, SQL keyword, identifier, or expected example output is touched: six of the fixes are on
--comment lines inside SQL example blocks, andAMBIGUOUS_COLUMN_OR_FIELDitself is unchanged (only the preceding article). Indentation of the nested list is byte-identical.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.8)