Description
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.
Attachments
Issue Links
- relates to
-
SPARK-27961 DataSourceV2Relation should not have refresh method
- Resolved
- links to