-
Notifications
You must be signed in to change notification settings - Fork 120
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
Finding first match not working as expected? #218
Comments
Notes to self: When I run the above code (without setting
and get this response:
(Redis Stack Docker container, Redis OM 0.0.25). I'll look at how |
Behaviour I see is that when using
|
@msarm I think you're right, and that
I'll look at a PR for this, and I suspect that both Thanks for looking into this. |
This will be fixed in the next release. |
Fixed in 0.0.26. |
Reported by @msarm initially as part of #207 :
I see 'ft.search' round trip got reduced now after defaulting the page size to 1000 and this helps other queries to run even faster but my results are not coming this time may be a different issue now.
When I perform the Person query:
Here is the
ft.search
performed.When the last fired
ft.search
is performed it does not return any results it retries for every.Since are looking just for the first record, can we just fire the first
ft.search
and return the results?When I set explicitly the
exhaust_results=False
in thefirst()
function, I see quick results with no extra query. Is that right the fix?Original code:
The text was updated successfully, but these errors were encountered: