[
https://issues.apache.org/jira/browse/SPARK-58392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-58392.
---------------------------------
Fix Version/s: 4.3.0
Resolution: Fixed
Issue resolved by pull request 57585
[https://github.com/apache/spark/pull/57585]
> Pass table state options while loading relations
> ------------------------------------------------
>
> Key: SPARK-58392
> URL: https://issues.apache.org/jira/browse/SPARK-58392
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.2.0
> Reporter: Yan Yan
> Assignee: Yan Yan
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.3.0
>
>
> Follow-up to SPARK-58389, which lets catalogs declare options that affect
> table state through {{TableCatalog.tableStateOptionKeys()}}. Spark forwards
> only that declared projection to {{TableCatalog.loadTable(Identifier,
> TableContext, CaseInsensitiveStringMap)}} and retains the complete user
> option map on the resolved relation for scan planning.
> {{RelationCatalog.loadRelation(Identifier)}} remains the single-RPC path for
> ordinary reads with no table-state options, time travel, or write privileges.
> When table-state options are present, relation resolution uses
> {{TableCatalog.loadTable(Identifier, TableContext,
> CaseInsensitiveStringMap)}} for the table side. If the identifier is not a
> table, ordinary reads may fall back to {{ViewCatalog.loadView(Identifier)}}.
> Time-travel and write-privilege loads remain table-only.
> The shared table lookup matches table identity and declared table-state
> options, while each resolved relation retains its complete option map. This
> change adds no new {{RelationCatalog}} API.
> PR: https://github.com/apache/spark/pull/57585
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
