You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2025/11/16 06:00:00 UTC

[jira] [Assigned] (SPARK-53924) Reload DSv2 tables in views created using plans on each access

     [ https://issues.apache.org/jira/browse/SPARK-53924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun reassigned SPARK-53924:
-------------------------------------

    Assignee: Anton Okolnychyi

> Reload DSv2 tables in views created using plans on each access
> --------------------------------------------------------------
>
>                 Key: SPARK-53924
>                 URL: https://issues.apache.org/jira/browse/SPARK-53924
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 4.1.0
>            Reporter: Anton Okolnychyi
>            Assignee: Anton Okolnychyi
>            Priority: Major
>              Labels: pull-request-available
>
> The current problem is that the view definition in the session catalog captures the analyzed plan that references DataSourceV2Relation and Table. If a connector doesn’t have an internal cache and produces a new Table object after TableCatalog$load, Table referenced in the view will become orphan and there will be no way to refresh it unless that Table instance auto refreshes on each scan (super dangerous).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org