-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
TermsFacet across index returns wrong results (0.90) #2797
Comments
IMHO, that's somehow the same issue as #1305, isn't it? |
I'm familiar with that issue, but people are reporting there single shards of multiple indexes works for them, and use that approach as a workaround. If this indeed is the same issue, this becomes a regression issue. Either way, we would really like to have this fixed... |
What people are reporting as far as I understand is that when your narrow your search on a single shard, you will will have the exact values. But I can be wrong here. |
This is indeed a duplicate of #1305 and there is no easy fix, just workarounds:
It is the nature of distributed search... |
When faceting on more than one index, each with one shard, no replicas, and containing the same data structure, TermsFacet will return the wrong counts. This can be easily verified by running a simple query with the facet value. Additionally, changing the size parameter will cause facet results to change (while we only expected to get a shorter/longer list , we actually see values change and terms disappear).
Our faceting query:
The text was updated successfully, but these errors were encountered: