This is an automated email from the ASF dual-hosted git repository.
alamb pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git
The following commit(s) were added to refs/heads/main by this push:
new 848f6c395a update doc (#8686)
848f6c395a is described below
commit 848f6c395afef790880112f809b1443949d4bb0b
Author: Devin D'Angelo <[email protected]>
AuthorDate: Sun Dec 31 07:34:54 2023 -0500
update doc (#8686)
---
datafusion/core/src/datasource/provider.rs | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/datafusion/core/src/datasource/provider.rs
b/datafusion/core/src/datasource/provider.rs
index 275523405a..c1cee849fe 100644
--- a/datafusion/core/src/datasource/provider.rs
+++ b/datafusion/core/src/datasource/provider.rs
@@ -141,7 +141,11 @@ pub trait TableProvider: Sync + Send {
/// (though it may return more). Like Projection Pushdown and Filter
/// Pushdown, DataFusion pushes `LIMIT`s as far down in the plan as
/// possible, called "Limit Pushdown" as some sources can use this
- /// information to improve their performance.
+ /// 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
+ /// removed, so applying the limit could lead to too few rows being
available
+ /// to return as a final result.
async fn scan(
&self,
state: &SessionState,
