Skip to content

Conversation

@xinlifoobar
Copy link
Contributor

Which issue does this PR close?

Closes #11305

Rationale for this change

I moved part of the code from #11263 into this PR to reduce the # of planners we created. I read through the code and thought it is better for just one planner whole crate instead of one module for small usages...

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@github-actions github-actions bot added the core Core DataFusion crate label Jul 7, 2024
Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @xinlifoobar -- this looks good to me

I agree that minimizing the number of planners is probably a good thing (as the sql planner will iterate over all planners several times, so the fewer the better in my mind)

cc @dharanad @jayzhan211

@jayzhan211
Copy link
Contributor

Thanks @xinlifoobar and @alamb

@jayzhan211 jayzhan211 merged commit 940efd3 into apache:main Jul 8, 2024
findepi pushed a commit to findepi/datafusion that referenced this pull request Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Core DataFusion crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consolidate SQL expr planners so there are one in each module (like a UnicodePlanner rather than a PositionPlanner?

3 participants