Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix wrong pushdown name & a typo #8875

Merged
merged 1 commit into from
Jan 15, 2024
Merged

docs: fix wrong pushdown name & a typo #8875

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions datafusion/core/src/datasource/provider.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ pub trait TableProvider: Sync + Send {
/// expressions are `AND`ed together).
///
/// DataFusion pushes filtering into the scans whenever possible
/// ("Projection Pushdown"), and depending on the format and the
/// ("Filter Pushdown"), and depending on the format and the
/// implementation of the format, evaluating the predicate during the scan
/// can increase performance significantly.
///
Expand Down Expand Up @@ -143,7 +143,7 @@ pub trait TableProvider: Sync + Send {
/// possible, called "Limit Pushdown" as some sources can use this
/// information to improve their performance. Note that if there are any
/// Inexact filters pushed down, the LIMIT cannot be pushed down. This is
/// because inexact filters do not guarentee that every filtered row is
/// because inexact filters do not guarantee that every filtered row is
/// removed, so applying the limit could lead to too few rows being available
/// to return as a final result.
async fn scan(
Expand Down
Loading