[I] Comet should choose the most suitable Parquet scan implementation automatically [datafusion-comet]

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

andygrove opened a new issue, #1881:
URL: https://github.com/apache/datafusion-comet/issues/1881

   ### What is the problem the feature request solves?
   
   We currently support three different Parquet scan implementations:
   
   - `native_comet`
   - `native_datafusion`
   - `native_iceberg_compat`
   
   We really shouldn't expose the details of this or expect users to choose which implementation to use, since this is a very low level technical detail. It would be better if Comet just used the most appropriate one based on the Parquet schema and knowledge of supported features and known issues in the different scan implementations. For example, some of these scans do not support S3 or encryption currently.
   
   
   ### Describe the potential solution
   
   _No response_
   
   ### Additional context
   
   _No response_


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