alamb commented on issue #19573: URL: https://github.com/apache/datafusion/issues/19573#issuecomment-3703700892
> By "table scoped", do we expect cache reuse in this case? If not, do we expect the cache key to be logically some "table identifier" instead of just table path? I personally think that the cache should be table scoped -- so in this case I propose that the `test2` table does not reuse the cache In my mind the core usecase the cache is when querying partitioned tables -- so that when querying on partition columns, querying with LIST is not required. @BlakeOrth mostly completed this use case already, but there is no way to introspect (see) what is cached without a session scoped object However, by creating a session scoped object we now have this unintended sharing -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
