[
https://issues.apache.org/jira/browse/SPARK-59721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun resolved SPARK-59721.
-----------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
Issue resolved by pull request 58979
[https://github.com/apache/spark/pull/58979]
> Ignore reported partitioning and ordering that reference unresolvable columns
> -----------------------------------------------------------------------------
>
> Key: SPARK-59721
> URL: https://issues.apache.org/jira/browse/SPARK-59721
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.4.0
> Reporter: Anurag Mantripragada
> Assignee: Anurag Mantripragada
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.4.0
>
>
> When a DSv2 scan reports a KeyGroupedPartitioning or an ordering that
> references a column the relation can't resolve, the query fails with
> `{{{}Unable to resolve X given {}}}{{{}[...]{}}}`.
> V2ScanPartitioningAndOrdering should check the columns referenced by the
> reported partition keys and ordering (recursively, including nested transform
> arguments) against the relation before converting them. If any can't be
> resolved, including a missing nested field or an ambiguous reference, it
> should log a warning naming the relation, the scan class, and the columns,
> and ignore the report: the partitioning falls back to unknown partitioning,
> and the ordering is dropped.
> Found while reviewing SPARK-58111 (PR
> [#55518|https://github.com/apache/spark/pull/55518]); this bug is general and
> pre-existing, not introduced there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
