[
https://issues.apache.org/jira/browse/SOLR-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059830#comment-15059830
]
Alessandro Benedetti commented on SOLR-7219:
--------------------------------------------
I was wondering if it is really necessary to add the "filter" element in the
syntax when we want to re-use the filter.
Isn't always true we would ideally re-use all our boolean clauses ?
Of course doing this automatically could produce a very fast changing
filterCache.
But probably this should be completely trasparent to the user.
I got used to the concept of filter queries, but actually more the time passes
more I see the opportunity in having an automatic caching for all the boolean
clauses in the main query block.
What could be cons of that approach ?
> Access filter cache from lucene query syntax
> --------------------------------------------
>
> Key: SOLR-7219
> URL: https://issues.apache.org/jira/browse/SOLR-7219
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Fix For: 5.4
>
> Attachments: SOLR-7219.patch
>
>
> A filter query retrieves a set of documents matching a query from the filter
> cache. Since scores are not cached, all documents that match the filter
> produce the same score. Cached filters will be extremely fast when they are
> used again in another query.
> Filter Query Example:
> {code}
> description:HDTV OR filter(+promotion:tv +promotion_date:[NOW/DAY-7DAYS TO
> NOW/DAY+1DAY])
> {code}
> The power of the filter() syntax is that it may be used anywhere within a
> lucene/solr query syntax. Normal fq support is limited to top-level
> conjunctions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
