-
Notifications
You must be signed in to change notification settings - Fork 223
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.
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
Document "no limit" behavior for LanceQueryBuilder #796
Labels
documentation
Improvements or additions to documentation
Comments
The API is focused on search so a limit is always required in that case. And we just set a limit of 10 to prevent users from accidentally shooting themselves in the foot. E.g., BI tools always have a limit that's on by default (but that you can manually turn off). On the documentation gap, that's a good point. Let's keep this issue open and we'll make a fix (also open to PRs if you're interested). |
changhiskhan
added a commit
that referenced
this issue
Jan 9, 2024
changhiskhan
added a commit
that referenced
this issue
Jan 10, 2024
koolamusic
pushed a commit
to tecmie/lancedb
that referenced
this issue
Jan 12, 2024
raghavdixit99
pushed a commit
to raghavdixit99/lancedb
that referenced
this issue
Apr 5, 2024
raghavdixit99
pushed a commit
to raghavdixit99/lancedb
that referenced
this issue
Apr 5, 2024
westonpace
pushed a commit
that referenced
this issue
Apr 5, 2024
westonpace
pushed a commit
that referenced
this issue
Apr 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
lancedb/python/lancedb/query.py
Line 263 in 1216872
The type annotation for
LanceQueryBuilder.limit()
says limit must be an int and there's no mention of what you should pass if you want "no limit" (it'sNone
... a user might think you need to pass inlimit=-1
?). Type annotation should be changed toOptional[int]
andNone
behavior should be documented accordingly.Somewhat related - it is a little non-intuitive that the default behavior is
limit = 10
as opposed to no limit.Link
No response
The text was updated successfully, but these errors were encountered: