[
https://issues.apache.org/jira/browse/SOLR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466616
]
Hoss Man commented on SOLR-80:
------------------------------
I was strating to think the same thing as Mike: but doing more testing i seee
what yonik's refering to (note to self: test more then one query when doing
cache testing) ... only the first use of a negative query results in the double
insert .. afterthat every thing is golden.
Mike: i think the key is that unless faceting is turned on, the
StandardRequestHandler only calls getDocList, not getDocListAndSet ... so by
the time the call makes it to getDocListC the falgs never contain GET_DOCSET,
so the main query isn't included in the list passed to getDocSet.
> negative filter queries
> -----------------------
>
> Key: SOLR-80
> URL: https://issues.apache.org/jira/browse/SOLR-80
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Yonik Seeley
> Attachments: negative_filters.patch, negative_filters.patch
>
>
> There is a need for negative filter queries to avoid long filter generation
> times and large caching requirements.
> Currently, if someone wants to filter out a small number of documents, they
> must specify the complete set of documents to express those negative
> conditions against.
> q=foo&fq=id:[* TO *] -id:101
> In this example, to filter out a single document, the complete set of
> documents (minus one) is generated, and a large bitset is cached. You could
> also add the restriction to the main query, but that doesn't work with the
> dismax handler which doesn't have a facility for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
