docs: Document the TableProvider evaluation order for filter, limit and projection#21091
Merged
alamb merged 3 commits intoapache:mainfrom Mar 23, 2026
Merged
docs: Document the TableProvider evaluation order for filter, limit and projection#21091alamb merged 3 commits intoapache:mainfrom
alamb merged 3 commits intoapache:mainfrom
Conversation
comphead
approved these changes
Mar 22, 2026
hareshkh
approved these changes
Mar 22, 2026
Contributor
Author
de-bgunter
pushed a commit
to de-bgunter/datafusion
that referenced
this pull request
Mar 24, 2026
…nd projection (apache#21091) ## Which issue does this PR close? - Follow on to apache#21057 ## Rationale for this change As mentioned by @hareshkh on apache#21057 (comment): It is not clear from the existing documentation that the (logical) evaluation order for push down operations is 'filter -> limit -> projection' this is the actual order implemented by the built in providers, but it wasn't documented anywhere explicitly ## What changes are included in this PR? 1. Explicitly document the evaluation order on TableProvider 2. Some drive by cleanups of the documentation ## Are these changes tested? By CI ## 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. -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
Rationale for this change
As mentioned by @hareshkh on #21057 (comment):
It is not clear from the existing documentation that the (logical) evaluation order for push down operations is 'filter -> limit -> projection'
this is the actual order implemented by the built in providers, but it wasn't documented anywhere explicitly
What changes are included in this PR?
Are these changes tested?
By CI
Are there any user-facing changes?