gokselk opened a new pull request, #14111:
URL: https://github.com/apache/datafusion/pull/14111
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #14110.
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
This PR extends the physical planner to propagate table constraints (PRIMARY
KEY and UNIQUE) through the query plan. This allows us to optimize sort
operations by recognizing when ordering requirements are already satisfied by
existing constraints.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
- Added `Constraints` propagation through physical plans including:
- File scan executors (CSV, Parquet, Arrow, Avro, JSON)
- Memory table executor
- Aggregate executor
- Added constraint projection logic
- Updated `EquivalenceProperties` to consider constraints when evaluating
sort requirements
- Added tests for constraint propagation and sort optimization
- Updated protobuf definitions to include constraints in physical plan
serialization
## Are these changes tested?
Yes, the changes include:
- Tests for constraint projection and validation
- Tests for sort optimization with constraints
- sqllogictests verifying correct plan optimization
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
The changes are mostly internal optimizations, but users will see:
- Improved query plans that eliminate redundant sorts when constraints
guarantee ordering
- Updated EXPLAIN output that shows constraints in physical plans
- More efficient execution of queries with ORDER BY on primary key columns
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
