You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the values of Hive partitions are projected within each of the various file format specific physical operators. As described in #2079 this has a number of drawbacks
Describe the solution you'd like
Rather than handling partition projection within the file scan operator, I would like to propose modifying ListingTable to add a ProjectionExec within TableProvider::scan instead of relying on the FileFormat implementations to do this. This ProjectionExec would be created with a set of literal expressions corresponding to the partition values
Therefore instead of TableProvider::scan generating something like
The logic could instead be moved to FileFormat::create_physical_plan implementations, but I think it would be better to keep what is a catalog detail close to the catalog implementation.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Part of #2079
Currently the values of Hive partitions are projected within each of the various file format specific physical operators. As described in #2079 this has a number of drawbacks
Describe the solution you'd like
Rather than handling partition projection within the file scan operator, I would like to propose modifying
ListingTable
to add aProjectionExec
withinTableProvider::scan
instead of relying on theFileFormat
implementations to do this. ThisProjectionExec
would be created with a set of literal expressions corresponding to the partition valuesTherefore instead of
TableProvider::scan
generating something likeIt would generate
Note: this will depend on #2289
Describe alternatives you've considered
The logic could instead be moved to
FileFormat::create_physical_plan
implementations, but I think it would be better to keep what is a catalog detail close to the catalog implementation.FYI @matthewmturner @yjshen @rdettai
The text was updated successfully, but these errors were encountered: