Skip to content

chore(docs): Fix the documentation for TableProvider::scan()'s limit argument #25397

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

Merged
2010YOUY01 merged 1 commit into from
Sep 17, 2026
+2 −2
Merged

chore(docs): Fix the documentation for TableProvider::scan()'s limit argument #25397

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/session/src/table.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,8 +150,8 @@ pub trait TableProvider: Any + Debug + Sync + Send {
///
/// # Limit
///
/// If `limit` is specified, the scan must produce *at least* this many
/// rows, though it may return more. Like Projection Pushdown and Filter
/// If `limit` is specified, the scan must produce *at most* this many
/// rows, though it may return less. Like Projection Pushdown and Filter
/// Pushdown, DataFusion pushes `LIMIT`s as far down in the plan as
/// possible. This is called "Limit Pushdown", and some sources can use the
/// information to improve performance.
Expand Down