Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EPIC] Extract remaining physical optimizer out of core #11502

Open
6 of 14 tasks
jayzhan211 opened this issue Jul 17, 2024 · 0 comments
Open
6 of 14 tasks

[EPIC] Extract remaining physical optimizer out of core #11502

jayzhan211 opened this issue Jul 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jayzhan211
Copy link
Contributor

jayzhan211 commented Jul 17, 2024

Is your feature request related to a problem or challenge?

Given the research from #10782, we need to pull out physical optimizer first before extracting catalog.

Describe the solution you'd like

Pull physical optimizer rules to datafusion-physical-optimizer.

There are some tests that have dependencies on datasource, which they are not possible to move out of core at this moment. We may need to leave those tests inside core for now.

  • PhysicalOptimizerRule Create datafusion-physical-optimizer crate #11507
  • OutputRequirements
  • AggregateStatistics
  • JoinSelection
  • LimitedDistinctAggregation
  • EnforceDistribution
  • CombinePartialFinalAggregate
  • EnforceSorting
  • OptimizeAggregateOrder
  • ProjectionPushdown
  • CoalesceBatches
  • OutputRequirements
  • TopKAggregation
  • SanityCheckPlan

Describe alternatives you've considered

No response

Additional context

No response

@jayzhan211 jayzhan211 added the enhancement New feature or request label Jul 17, 2024
@alamb alamb changed the title [EPIC] Extract physical optimizer out of core [EPIC] Extract remaining physical optimizer out of core Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant