Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 71687 invoked from network); 16 Jun 2009 21:03:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Jun 2009 21:03:27 -0000 Received: (qmail 95085 invoked by uid 500); 16 Jun 2009 21:03:38 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 95025 invoked by uid 500); 16 Jun 2009 21:03:38 -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 95015 invoked by uid 99); 16 Jun 2009 21:03:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2009 21:03:38 +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; Tue, 16 Jun 2009 21:03:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5775729A0012 for ; Tue, 16 Jun 2009 14:03:07 -0700 (PDT) Message-ID: <1843397236.1245186187357.JavaMail.jira@brutus> Date: Tue, 16 Jun 2009 14:03:07 -0700 (PDT) From: "Yonik Seeley (JIRA)" To: solr-dev@lucene.apache.org Subject: [jira] Commented: (SOLR-1223) Query Filter fq with OR operator In-Reply-To: <1816063845.1245177307380.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-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720349#action_12720349 ] Yonik Seeley commented on SOLR-1223: ------------------------------------ The hardest part to this is passing the information through the Solr APIs to tell Solr to cache the clauses of a particular boolean query separately. 2 approaches: - a SolrQuery that wrapps a normal Query and adds extra metadata like "cache separately" or "don't cache" - replace Query with SolrFilter (that contains a Query as well as the extra metadata)... involves many deprecations. > Query Filter fq with OR operator > -------------------------------- > > Key: SOLR-1223 > URL: https://issues.apache.org/jira/browse/SOLR-1223 > Project: Solr > Issue Type: New Feature > Components: search > Reporter: Brian Pearson > Priority: Minor > > See this [issue|http://www.nabble.com/Query-Filter-fq-with-OR-operator-td23895837.html] for some background. Today, all of the Query filters specified with the fq parameter are AND'd together. > This issue is about allowing a set of filters to be OR'd together (in addition to having another set of filters that are AND'd). The OR'd filters would of course be applied before any scoring is done. > The advantage of this feature is that you will be able to break up complex filters into simple, more cacheable filters, which should improve performance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.