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
wrong facet_counts, missing facet values with Semantic Search #1714
Comments
@Ku3mi41 This issue should not occur with |
Okay, now per_page: 250
per_page: 5
|
I checked but for the example data you have provided earlier, the counts are correct and matches the document field values returned in the response hits array. Can you please explain which facet count is different?
Yes, this is because, with semantic search, we are doing a top K operation (it's too expensive to exhaustively do vector search on the entire collection). The |
You can set |
It explains everything. Could you add this clarification to the documentation? Without vector search, all the numbers look correct, at least in the first 10 queries that I checked. Part of my initial problem was that the number of results actually turned out to be greater than the facet predicted. Thanks for the fix and clarification, I think this issue can be closed. |
Description
Wrong facet_count while using
vector_query
. Sometime facet values didn't exist in response at all.Steps to reproduce
Expected Behavior
Sum of all
counts
expect to be equalfound
. All facet values must be represented incounts
sections (sometime it's not, especially on bigger collection).Actual Behavior
Typesense Version: 26
The text was updated successfully, but these errors were encountered: