[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703299#action_12703299
]
Yonik Seeley commented on SOLR-773:
-----------------------------------
bq. I am not familiar with the function query internal - would it get called
for things that do not match the filter? Distance calculations are typically
the most expensive part of the query.
Right... function query currently *does* get called before filters are checked
- but that's because current function queries are part of the main relevancy
query. A function query that was only used to sort would only be called for
docs that match the main relevancy query and all filters though.
The performance issue would be the "boost" scenario - when the distance
calculation is part of the main query. That's another generic Solr issue we
should tackle at some point... filter efficiency. Related to LUCENE-1536 I
think (but we could already do this relatively easily for BitDocSet... just not
HashDocSet).
> Incorporate Local Lucene/Solr
> -----------------------------
>
> Key: SOLR-773
> URL: https://issues.apache.org/jira/browse/SOLR-773
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Attachments: lucene.tar.gz, SOLR-773-local-lucene.patch,
> SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch,
> SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch, SOLR-773.patch,
> SOLR-773.patch, spatial-solr.tar.gz
>
>
> Local Lucene has been donated to the Lucene project. It has some Solr
> components, but we should evaluate how best to incorporate it into Solr.
> See http://lucene.markmail.org/message/orzro22sqdj3wows?q=LocalLucene
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
