Re: [PR] Fix sequential metadata fetching in ListingTable causing high latency [datafusion]

["alamb (via GitHub)" <gi...@apache.org>]

alamb commented on PR #14918:
URL: https://github.com/apache/datafusion/pull/14918#issuecomment-2694607224

   I tried to verify these changes but I couldn't figure out how to create an external table with explicitly listing the names via SQL.
   
   For posterity here is what I tried:
   
   
   This PR:
   ```
   > create external table hits stored as parquet OPTIONS('aws.region' 'eu-central-1') location 's3://clickhouse-public-datasets/hits_compatible/athena_partitioned/';
   0 row(s) fetched.
   Elapsed 2.690 seconds.
   ```
   
   Main
   ```
   > create external table hits stored as parquet OPTIONS('aws.region' 'eu-central-1') location 's3://clickhouse-public-datasets/hits_compatible/athena_partitioned/';
   0 row(s) fetched.
   Elapsed 2.284 seconds.
   ```
   
   I am going to try and whip up a smaller reproducer


-- 
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: github-unsubscribe@datafusion.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org