This is an automated email from the ASF dual-hosted git repository.
uros-b pushed a commit to branch branch-4.x
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-4.x by this push:
new 4de7acf59c06 [SPARK-58679][DOC] Fix typos and grammar in the SQL name
resolution reference doc
4de7acf59c06 is described below
commit 4de7acf59c06819c39a9475df161017f3be4cc94
Author: Uros Bojanic <[email protected]>
AuthorDate: Mon Aug 10 04:27:58 2026 +0000
[SPARK-58679][DOC] Fix typos and grammar in the SQL name resolution
reference doc
### What changes were proposed in this pull request?
Fixes nine spelling and grammar errors in `docs/sql-ref-name-resolution.md`:
- `precendece` to `precedence`
- `Implict` to `Implicit`
- `Successsful` to `Successful`
- `raise a AMBIGUOUS_COLUMN_OR_FIELD` to `raise an ...`
- `An fully qualified` to `A fully qualified`
- `takes precedent` to `takes precedence`
- `Columns and parameter win` to `Columns and parameters win`
- `a column in table reference` to `a column in a table reference`
- removes a stray comma in `takes precedence, over a lateral column alias`
### Why 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_FIELD` twice,
`a column name in a table reference`, the adjacent `A partially qualified` and
`An unqualified`, and `takes precedence over` seven times without a comma.
`takes precedent` is the function-resolution example where a temporary function
wins over a persistent one, so `precedence` is 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, and `AMBIGUOUS_COLUMN_OR_FIELD` itself 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)
Closes #57882 from uros-b/typo-name-resolution-docs.
Authored-by: Uros Bojanic <[email protected]>
Signed-off-by: Uros Bojanic <[email protected]>
(cherry picked from commit 4374cb33299c9e808b339d6ccf25768f2407c717)
Signed-off-by: Uros Bojanic <[email protected]>
---
docs/sql-ref-name-resolution.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/sql-ref-name-resolution.md b/docs/sql-ref-name-resolution.md
index 3d574e58a9ad..797e12acde63 100644
--- a/docs/sql-ref-name-resolution.md
+++ b/docs/sql-ref-name-resolution.md
@@ -36,7 +36,7 @@ Identifiers in expressions can be references to any one of
the following:
Name resolution applies the following principles:
- The _closest_ matching reference wins, and
-- Columns and parameter win over fields and keys.
+- Columns and parameters win over fields and keys.
In detail, resolution of identifiers to a specific reference follows these
rules in order:
@@ -62,7 +62,7 @@ In detail, resolution of identifiers to a specific reference
follows these rules
A. Remove the last identifier and treat it as a field or key.
- B. Match the remainder to a column in table reference of the `FROM
clause`.
+ B. Match the remainder to a column in a table reference of the `FROM
clause`.
- If there is more than one such match, raise an
AMBIGUOUS_COLUMN_OR_FIELD error.
@@ -72,7 +72,7 @@ In detail, resolution of identifiers to a specific reference
follows these rules
If the field cannot be matched, raise a FIELD_NOT_FOUND error.
- If there is more than one field, raise a
AMBIGUOUS_COLUMN_OR_FIELD error.
+ If there is more than one field, raise an
AMBIGUOUS_COLUMN_OR_FIELD error.
- **`MAP`**: Raise an error if the key is qualified.
@@ -161,15 +161,15 @@ This restriction also applies to parameter references in
SQL functions.
> SELECT t.a FROM VALUES(named_struct('a', 1)) AS t(t);
1
--- A column takes precendece over a field
+-- A column takes precedence over a field
> SELECT t.a FROM VALUES(named_struct('a', 1), 2) AS t(t, a);
2
--- Implict lateral column alias
+-- Implicit lateral column alias
> SELECT c1 AS a, a + c1 FROM VALUES(2) AS T(c1);
2 4
--- A local column reference takes precedence, over a lateral column alias
+-- A local column reference takes precedence over a lateral column alias
> SELECT c1 AS a, a + c1 FROM VALUES(2, 3) AS T(c1, a);
2 5
@@ -204,7 +204,7 @@ This restriction also applies to parameter references in
SQL functions.
WHERE c4 = c2 * 2);
[UNRESOLVED_COLUMN] `c2`
--- Successsful usage of lateral correlation with keyword LATERAL
+-- Successful usage of lateral correlation with keyword LATERAL
> SELECT c1, c2, c3
FROM VALUES(1, 2) AS t(c1, c2),
LATERAL(SELECT c3 FROM VALUES(3, 4) AS s(c3, c4)
@@ -318,7 +318,7 @@ the effective search path, for example
> CREATE TABLE rel(c1 int);
> INSERT INTO rel VALUES(1);
--- An fully qualified reference to rel:
+-- A fully qualified reference to rel:
> SELECT c1 FROM spark_catalog.default.rel;
1
@@ -428,7 +428,7 @@ effective search path, for example
> CREATE FUNCTION func(a INT, b INT) RETURNS INT
RETURN a / b;
--- The temporary function takes precedent
+-- The temporary function takes precedence
> SELECT func(4, 2);
2
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
