[
https://issues.apache.org/jira/browse/SOLR-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680245#comment-14680245
]
Yonik Seeley commented on SOLR-7219:
------------------------------------
bq. Just curious; why is this feature implemented as a change to the query
grammar versus adding a QParser?
The feature was about being able to access the filter cache anywhere within a
lucene/solr query string.
Since qparsers can't encapsulate arbitrary query clauses in lucene syntax, one
would need to use additional params.
{code}
foo:bar filter(instock:true)
vs
foo:bar {!filter v=$myfilt}&myfilt=instock:true
{code}
So possible with just a qparser, but not as easy or nice looking.
> 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
