Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A568E1097A for ; Mon, 18 Nov 2013 18:38:55 +0000 (UTC) Received: (qmail 75434 invoked by uid 500); 18 Nov 2013 18:38:53 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 75382 invoked by uid 500); 18 Nov 2013 18:38:53 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Delivered-To: moderator for java-user@lucene.apache.org Received: (qmail 66747 invoked by uid 99); 18 Nov 2013 18:35:42 -0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 504142.55763.bm@omp1013.mail.bf1.yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1384799712; bh=V/kwvDiSiQlhINT3tym62reFik68SsWK4Pnj8Gz72y8=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=x+lQZ0+ImW2qTCIeY/Oc83G/p3HME1UCx/bMfMfcBAD8nKpX2TQihVcDgxiMRdy7J3AExoCCbLwguxH3AzFkNEgc7jGlE3EqfH2lMVBuIHm/KKiVWeJBxIFwocFC1RHcuwrU1fQ/gn9RzDprUBS6bMMXqYdn2khF7eB4IerjEd8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=Q+8gr58Ofa6eCsejLGDnoQPQ4fRtcB7jZ39SEaiONtbxn64/b/JoC7I0paeEwvzz5nSd+Af1j7iV5IoxUhmcMkPHL2MXKQd6I4Kv6UIfvzHB28e9uHItj0WpZDPakcWh6ReoihpsfiRzW2WF6fd6QoR2RV/iFnyrqE4FjVEthDo=; X-YMail-OSG: RgX22yoVM1ng8ka8RqZNgqyS6H8DUA_Kdp.aKQoi7AWa79I mM0XLrNLSodGv9bSDvE.GuzCIq.TsfE7RQ9wJLeUJ7K1mn4ptQdK8T0yru02 pSkizkU2y5Ttee.YI.Y3p2.cETrfYzsb4frgWioKHGOMUkWWLqEeWqEJEgJ1 mpQSU11sQAHBOCeodjo2mvxyPSypxY3flZs9Z_DDlAjYAzQff4c.lQL_HEEa .QpHjx5NGWGEfnFMolwO.qkesfM2WCjtvridrqXWrkb.O.Ye8XFz7W4e0BZr bnwlHAEEmN.6wip3qR9ovn_tDDR5t07McJorHHWslH9JWEp3P35TRlcBO9HZ hCctXH9wF7J_ZOE8h3rZnxQk6mklV5.r61wi_BzFJSQGOLPyQXfjvvikS16t pC2TCxOwVT1GPS0sB800UD2QIYeQEZatxdBWgM_q3f1EVkt_IV6NxbxVUrc8 u8tde0kWu9dp8wH93pQNd2nryN6AuqmGwI2GiJCVcLx0zvS6ffm2sO4mKuUP RYrF_uI5EEEw11F3s5rGKmnbpe1piIdMFOGRjq6a60KtaEMKQFVg2AbkfJvX oESTHILzA_Q-- X-Rocket-MIMEInfo: 002.001,SW5pdGlhbGx5LCBJIHF1ZXJpZWQgb3VyICh2NC40KSBpbmRleCB3aXRoIGEgc2luZ2xlIE11bHRpRmllbGRRdWVyeVBhcnNlciBhbmTCoE9wZXJhdG9yLkFORCB0byBlbnN1cmUgdGhhdCBhbGwgc2VhcmNoIHRlcm1zIGFwcGVhcmVkIGluIHRoZSByZXN1bHRzLgoKU2luY2UgdGhlbiwgaG93ZXZlciwgd2UndmUgbmVlZGVkIHRvIHF1ZXJ5IG1vcmUgZmxleGlibHksIHVzaW5nIGEgQm9vbGVhblF1ZXJ5IHRvIG1lcmdlIHNldmVyYWwgc3VicXVlcmllcyAoaW4gb3JkZXIgdG8gYXBwbHkgZGlmZmVyZW50IGFuYWwBMAEBAQE- X-Mailer: YahooMailWebService/0.8.166.601 Message-ID: <1384799712.36684.YahooMailNeo@web140703.mail.bf1.yahoo.com> Date: Mon, 18 Nov 2013 10:35:12 -0800 (PST) From: Shahak Nagiel Reply-To: Shahak Nagiel Subject: QueryParser.Operator with BooleanQuery To: "java-user@lucene.apache.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-979624102-1391846994-1384799712=:36684" X-Virus-Checked: Checked by ClamAV on apache.org ---979624102-1391846994-1384799712=:36684 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Initially, I queried our (v4.4) index with a single MultiFieldQueryParser a= nd=A0Operator.AND to ensure that all search terms appeared in the results.= =0A=0ASince then, however, we've needed to query more flexibly, using a Boo= leanQuery to merge several subqueries (in order to apply different analyzer= s to different fields/field groups). =A0As a result, we've had to switch to= Operator.OR, since there was no guarantee that all search terms would appl= y to/match every clause of the boolean query.=0A=0AConsequently, there's mo= re "noise" in the returned results, since many of them don't contain ALL th= e original search terms.=0A=0ASo, is there a way to enforce this AND/MUST p= olicy in a cumulative sense across all subqueries (i.e. filter out results = which don't match all search terms)?=0A=0AThanks!=0A ---979624102-1391846994-1384799712=:36684--