jizezhang commented on issue #19573:
URL: https://github.com/apache/datafusion/issues/19573#issuecomment-3702781657

   Hi @alamb @BlakeOrth , those might uncommon cases, but I wonder what the 
expected behavior would be if 
   - Two tables happen to be created with the same path, e.g.
     ```
     > create external table test
     stored as parquet
     location 
's3://overturemaps-us-west-2/release/2025-12-17.0/theme=base/type=infrastructure/';
     0 row(s) fetched. 
     Elapsed 2.955 seconds.
     
     > create external table test2
     stored as parquet
     location 
's3://overturemaps-us-west-2/release/2025-12-17.0/theme=base/type=infrastructure/';
     0 row(s) fetched. 
     Elapsed 0.741 seconds.
     ```
     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?
   - Two statements using the same path directly, e.g.
     ```
     > select count(*) from 
's3://overturemaps-us-west-2/release/2025-12-17.0/theme=base/type=infrastructure/';
     +-----------+
     | count(*)  |
     +-----------+
     | 142969564 |
     +-----------+
     1 row(s) fetched. 
     Elapsed 2.305 seconds.
     
     > select count(*) from 
's3://overturemaps-us-west-2/release/2025-12-17.0/theme=base/type=infrastructure/';
     +-----------+
     | count(*)  |
     +-----------+
     | 142969564 |
     +-----------+
     1 row(s) fetched. 
     Elapsed 0.037 seconds.
     ```
     In this case, do we expect cache reuse? or how would we interpret "table 
scoped" in this case?
   
   Thanks a lot!
   


-- 
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]

Reply via email to