[
https://issues.apache.org/jira/browse/SPARK-27504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859126#comment-16859126
]
Dongjoon Hyun commented on SPARK-27504:
---------------------------------------
This feature will be reverted by SPARK-27961.
> File source V2: support refreshing metadata cache
> -------------------------------------------------
>
> Key: SPARK-27504
> URL: https://issues.apache.org/jira/browse/SPARK-27504
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Gengliang Wang
> Assignee: Gengliang Wang
> Priority: Major
> Fix For: 3.0.0
>
>
> In file source V1, if some file is deleted manually, reading the
> DataFrame/Table will throws an exception with suggestion message "It is
> possible the underlying files have been updated. You can explicitly
> invalidate the cache in Spark by running 'REFRESH TABLE tableName' command in
> SQL or by recreating the Dataset/DataFrame involved.".
> After refreshing the table/DataFrame, the reads should return correct results.
> We should follow it in file source V2 as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
