[
https://issues.apache.org/jira/browse/SOLR-14996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325091#comment-17325091
]
Yevhen Tienkaiev commented on SOLR-14996:
-----------------------------------------
[~nathanmreinhardt] I think routing of requests also doesn't matter here.
I just wanna make sure that this issue will no go in history with unresolved
status, since it's critical and reproducible.
If collapsing not supported by Solr then it should throw error for this or
clearly mention in documentation.
For example Aggregates in Elasticsearch not supports collapsing and this is
clearly mentioned in documentation.
https://www.elastic.co/guide/en/elasticsearch/reference/current/collapse-search-results.html
{code}
The collapsing is applied to the top hits only and does not affect aggregations.
{code}
> Facet incorrect counts when FQ exclusion applied with collapsing
> ----------------------------------------------------------------
>
> Key: SOLR-14996
> URL: https://issues.apache.org/jira/browse/SOLR-14996
> Project: Solr
> Issue Type: Bug
> Components: faceting
> Affects Versions: 8.6.3
> Reporter: Yevhen Tienkaiev
> Priority: Critical
>
> *numFound* not correct according to what is displayed in facets with
> exclusion when used collapsing and FQ with tag.
> Here example query:
> {code}
> curl --location --request GET
> 'http://localhost:8981/solr/test/select?facet.field={!ex=selected}job_type&facet=on&fq={!collapse%20field=user_id}&fq={!tag=selected}job_type:thinker&q=*:*&rows=0'
> {code}
> result is:
> {code}
> {
> "responseHeader": {
> "zkConnected": true,
> "status": 0,
> "QTime": 15,
> "params": {
> "q": "*:*",
> "facet.field": "{!ex=selected}job_type",
> "fq": [
> "{!collapse field=user_id}",
> "{!tag=selected}job_type:thinker"
> ],
> "rows": "0",
> "facet": "on"
> }
> },
> "response": {
> "numFound": 850,
> "start": 0,
> "maxScore": 1.0,
> "numFoundExact": true,
> "docs": []
> },
> "facet_counts": {
> "facet_queries": {},
> "facet_fields": {
> "job_type": [
> "runner",
> 220,
> "developer",
> 202,
> "digger",
> 202,
> "thinker",
> 195,
> "ninja",
> 181
> ]
> },
> "facet_ranges": {},
> "facet_intervals": {},
> "facet_heatmaps": {}
> }
> }
> {code}
> as you can see there FQ with
> {code}
> {!tag=selected}job_type:thinker
> {code}
> and facets with
> {code}
> {!ex=selected}job_type
> {code}
> in results I see for *thinker* 195, but *numFound* is 850.
> Expected:
> *thinker* 195, *numFound* is 195
> *or*
> *thinker* 850, *numFound* is 850
> You can use this simple project to reproduce the issue
> https://github.com/Hronom/solr-cloud-basic-auth/tree/main/solr-cloud-playground-collapsing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
