[
https://issues.apache.org/jira/browse/SOLR-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-18020:
--------------------------------------
Attachment: SOLR-18020.patch
Status: Open (was: Open)
I mentioned on the mailing list...
{quote}i don't have firm handle on why the "positive" vs "negative" fq usage
should behave differently.
I feel like understanding that is pretty damn important before diving in too
much on "fixing" the DocSet hashCode & equals impls – adding correct impls of
those methods may fix the symptoms, but the failure discrepency worries me ....
makes me think some other bug or innefficiency is hiding in here.
{quote}
...all of that is still true: I still can't wrap my head around it; and it
still scares me.
but in the meantime: as expected, adding equals() & hashCode() impls to the
DocSet classes seem to make the bug go away.
> KnnFloatVectorQuery cache misses when prefiltering (fq) params are negative
> ---------------------------------------------------------------------------
>
> Key: SOLR-18020
> URL: https://issues.apache.org/jira/browse/SOLR-18020
> Project: Solr
> Issue Type: New Feature
> Reporter: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-18020.patch, SOLR-18020.test.patch
>
>
> From the mailing list....
> [https://lists.apache.org/thread/3zl69n9vyjlhrlx7h3133cnb644rgno6]
> {quote}I have encountered an issue that the KnnFloatVectorQuery could not get
> the superset from queryResultCache when I have negative filters in the
> request.
> For example, {{{}fq=-some_field:value{}}}. But with positive fq it works fine:
> {{fq=some_field:value}}
> {quote}
> The working theory is that these cache failures (and inconsistent behavior
> between positive vs negative {{fq}} params) relates to the lack of hashCode
> (and equals) implementations in {{DocSet}} impls – even though
> {{DocSetQuery}} explicitly calls {{DocSet.hashCode}} (and {{DocSet.equals}}
> in it's own impls
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
