Is your feature request related to a problem or challenge?
range_partitioning.slt currently needs a custom TableProvider / DataSource to declare that a scan has known Range output partitioning. This incurred a lot of test-only boilerplate, and there is no general external file/listing table API to declare scan output partitioning.
Describe the solution you'd like
Add a general output_partitioning: Option<Partitioning> API for file scans and listing tables:
- Add
FileScanConfig::with_output_partitioning, similar to with_output_ordering
- Update
range_partitioning.slt as first use case by registering a listing table with output_partitioning instead of a custom provider
Describe alternatives you've considered
Keep the current custom range-partitioned sqllogictest or add a one-off MemorySourceConfig output-partitioning builder. Both seem like bandaids and don't provide an external value.
Additional context
Follow-up from #22607.
Relevant discussions: #22607 (comment) #22607 (comment)
Is your feature request related to a problem or challenge?
range_partitioning.sltcurrently needs a customTableProvider/DataSourceto declare that a scan has knownRangeoutput partitioning. This incurred a lot of test-only boilerplate, and there is no general external file/listing table API to declare scan output partitioning.Describe the solution you'd like
Add a general
output_partitioning: Option<Partitioning>API for file scans and listing tables:FileScanConfig::with_output_partitioning, similar towith_output_orderingrange_partitioning.sltas first use case by registering a listing table withoutput_partitioninginstead of a custom providerDescribe alternatives you've considered
Keep the current custom range-partitioned sqllogictest or add a one-off
MemorySourceConfigoutput-partitioning builder. Both seem like bandaids and don't provide an external value.Additional context
Follow-up from #22607.
Relevant discussions: #22607 (comment) #22607 (comment)