Remove dependency on physical-optimizer on functions-aggregates #14134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft it is based on #14083 from @mnpwWhich issue does this PR close?
This is a follow up to
SanityChecker
intophysical-optimizer
crate #14083 from @mnpwRationale for this change
We are trying to make sure
datafusion-physical-optimizers
are not dependent on the actual function implementations so ensuring the crate doesn't have dependency will let the compiler ensure thisWhat changes are included in this PR?
Remove the dependency
Are these changes tested?
Are there any user-facing changes?