Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 14427 invoked from network); 27 Apr 2009 19:04:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Apr 2009 19:04:59 -0000 Received: (qmail 91343 invoked by uid 500); 27 Apr 2009 19:04:59 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 91249 invoked by uid 500); 27 Apr 2009 19:04:59 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 91239 invoked by uid 99); 27 Apr 2009 19:04:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2009 19:04:59 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2009 19:04:50 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 83DB7234C004 for ; Mon, 27 Apr 2009 12:04:30 -0700 (PDT) Message-ID: <1911016052.1240859070538.JavaMail.jira@brutus> Date: Mon, 27 Apr 2009 12:04:30 -0700 (PDT) From: "Yonik Seeley (JIRA)" To: solr-dev@lucene.apache.org Subject: [jira] Commented: (SOLR-773) Incorporate Local Lucene/Solr In-Reply-To: <1089092633.1221505424636.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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.