-
Notifications
You must be signed in to change notification settings - Fork 23
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
Misleading situation when using the recall keyword #323
Comments
@sephib pls note that Thiago is not working on this right now, it will take some days for a response |
Hi @sephib, when I run an example with recall I get the number of hits equal to the number of documents I want to recall, which I think is the behavior that you expect. For example, if you run this query notebook you see that in the end, we ask to recall two of the top 3 documents and we get exactly 2 documents back. Right? |
The difference between your notebook example and my code is that you provide the |
Could you paste the code you used for me to try to reproduce the issue? |
Closing for lack of activity. |
Hi,
I think there is a misleading situation when using the recall keyword with the number of results that are returned from the
app.query
When running
The number of results is
10
(default length ofhits
)I think the default
hits
should be the number of the docs in the recal_docsIf the number of recall docs are less then 10 - I would expect to get less the 10 results, thus when the number of docs in the recall is more then 10, I would expect to get all the hits for the docs in the recall list.
Does this sound reasonable?
The text was updated successfully, but these errors were encountered: