r4ntix commented on issue #5466: URL: https://github.com/apache/arrow-datafusion/issues/5466#issuecomment-1479467422
> For TableProvider that don't have access to this information, such as ListingTable, I think it is perfectly acceptable to use a single config value for the metadata size hint, without some sort of catalog there isn't really a way around this @tustvold thinks for the suggestions. So your suggestion is the following? 1. Catalog-inference: Reserve single config value of `metadata_size_hint` for `infer_schema`. 2. Query processing: Support `metadata_size_hint` in `FileScanConfig` for `create_physical_plan`. Also, what about `infer_stats`? When `ListingOptions.collect_stat` is true, each file is scanned in the scan logic of `TableProvider`. -- 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]
