aokolnychyi commented on issue #1485:
URL: https://github.com/apache/iceberg/issues/1485#issuecomment-698457408
> It feels like the biggest issue here is that behavior of cache is not
consistent or well-defined
That's what I think as well. Previously, `InsertIntoDataSourceCommand`
always invalidated the cache and data sources did not have an option to change
that behavior. Right now, Spark does not do anything automatically for custom
catalogs (but does match the old behavior in its catalog) so I am not sure
whether the interpretation is now up to the catalog or not.
Also, caching of V2 tables is not supported at all now.
```
// throws CACHE TABLE is only supported with temp views or v1 tables.
spark.sql("CACHE TABLE " + tableName)
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
