[
https://issues.apache.org/jira/browse/SOLR-14996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376183#comment-17376183
]
Michael Gibney commented on SOLR-14996:
---------------------------------------
Thanks for reporting back. I'm reluctant (and not in a position) to weigh in on
what the "correct" behavior should be. But I feel pretty confident in my
diagnosis of what _is_ happening, and fwiw I can readily hypothesize use cases
where the current behavior _would_ be the desired behavior (facet counts
consistent with collapsed result domain), even if you find it undesirable in
your particular case.
Also, leaving aside the question of what one might consider to be the "correct"
behavior, I strongly encourage you to take another look at {{join}} query,
because I'm pretty sure that's the way to achieve the behavior you're looking
for. (If I'm interpreting correctly "we cannot mention [user_id] during query
time", please note: my example query -- {{\{!join from=user_id to=user_id
v='job_type:thinker'\}}} -- is completely literal. i.e., "user_id" in that
query is the literal name of the field, not a standin for a particular user_id
value. And user_id, provided it is indexed and has docValues enabled, should
indeed be able to be referenced in such a query).
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
