[
https://issues.apache.org/jira/browse/SOLR-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634618#comment-13634618
]
Yonik Seeley commented on SOLR-4701:
------------------------------------
Could you explain the approach used, in particular how it differs from the
existing "frange" (function range) functionality that now has the PostFilter
ability?
http://yonik.com/posts/advanced-filter-caching-in-solr/
http://yonik.com/posts/ranges-over-functions-in-solr-1-4/
> CollectorFilterQParserPlugin support Filter Collector at search with
> PostFilter
> -------------------------------------------------------------------------------
>
> Key: SOLR-4701
> URL: https://issues.apache.org/jira/browse/SOLR-4701
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 4.2
> Reporter: Linbin Chen
> Fix For: 4.3
>
> Attachments: SOLR-4701.patch
>
>
> example:
> * {code}fq={!cf name=in}status:(-1, 2){code}
> * {code}fq={!cf name=in not=true}status:(3,4){code}
> * {code}fq={!cf name=range}price:[100 TO 500]{code}
> * {code}fq={!cf name=range}log(page_view):[50 TO 120]{code}
> in operate like sql in， faster then OR boolean query.
> most of the case, range faster then TrieField in lucene query.
> how to do use:
> solrconfig.xml add
> {code:xml}
> <queryParser name="cf" class="solr.CollectorFilterQParserPlugin"/>
> {code}
> cf not use query cache, use PostFilter fiter collector
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
