Export datafusion_physical_optimizer
, only use datafusion
crate in the examples
#14305
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.
Which issue does this PR close?
datafusion-physical-optimizer
#14300 (comment) with @berkaysynnadaRationale for this change
DataFusion is largely intended to be used via the
datafusion
crate. It is split into multiple subcrates largely for project organization rather than for users to use subcratesThe examples currently use many of the datafusion subcrates (e.g.
datafusion_common
) directly. This is non ideal becauseThus I think our examples should only use the DataFusion crate
What changes are included in this PR?
datafusion
ApplyOrder
indatafusion::optimizer
to make it easier to usedatafusion_physical_optimizer
asdatafusion::physical_optimizer
for consistencyAre these changes tested?
Yes, by CI
Are there any user-facing changes?
use datafusion::optimizer::ApplyOrder
in addition to what they currently douse datafusion::optimizer::optimizer::ApplyOrder