aokolnychyi commented on issue #1485: URL: https://github.com/apache/iceberg/issues/1485#issuecomment-698421717
I see merits in both approaches but the biggest concern for me is that we deviate from the way Spark handles cache for built-in tables. I am afraid this will cause a lot of confusion for the users. Moreover, our `SparkSessionCatalog` is not consistent now. It will invalidate cache for non-Iceberg tables only. > a temporary table that should reflect the state of the Dataset at the time it was created How Hive or Presto handle temp views? My understanding was that views provide a way to refer to and reuse a logical plan they are stateless. @danielcweeks, what do you think about case 2? ---------------------------------------------------------------- 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]
