Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D22239030 for ; Fri, 19 Dec 2014 09:13:07 +0000 (UTC) Received: (qmail 5752 invoked by uid 500); 19 Dec 2014 09:13:03 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 5684 invoked by uid 500); 19 Dec 2014 09:13:03 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 5672 invoked by uid 99); 19 Dec 2014 09:13:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 09:13:01 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mkhludnev@griddynamics.com designates 209.85.160.179 as permitted sender) Received: from [209.85.160.179] (HELO mail-yk0-f179.google.com) (209.85.160.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 09:12:57 +0000 Received: by mail-yk0-f179.google.com with SMTP id 19so197469ykq.10 for ; Fri, 19 Dec 2014 01:12:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=griddynamics.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=4/59puLLSpnMg02w4wYekn++slP2KVHf85M76/LKgeg=; b=OfLn8O/3uvq6fgZVy74ACsHCrO9czowO7cyl+Fy48byF1k9ty7ubSwcLKl/5nd7eB+ QEOfVp0/hA4ezSpyDSLe18aTJjNHObwog6xnvrRG4378Os5SJIygEv1P1ZUFAkqlQPF/ 3gmobjCBmGoLz7s3YzRgLI0NG/wxJHUuFVeEo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=4/59puLLSpnMg02w4wYekn++slP2KVHf85M76/LKgeg=; b=h2QfDE/0+JapJA0nZT7F3AzBUFEmYAZuGpwzUSs3d3t+VhLTjtNyPOgsfLScJ/Ixyt ZJ+Qc1TH28HyOfE691eQmH8MS2/661Y6tKak47WMbOfiMioC8OCxTN17V7nasMSoYhx2 kItb6MtzfikRk04EB9nTjjeyzkHubh8nisFHviE9hXJEh5g71eub8YLttvXd6E+KiiLe OM+q8PiEREzac/8T6eO04y1F3x9biZZ2GD4qdE7gcciPLJmEqhdvXwFz56N0kxPJ/rhe kfCMFUDrHr4JugcmI+45CFbmmKOIs6THrnbIGDmPtRvIJe+vkKHn7PK1f3XEiaJ59ZjX 1W7A== X-Gm-Message-State: ALoCoQlFrDnPLW0H41P9hoLbY+/GYEcRsu1XvgrBLa6VE77xam/WHDXyYenbWlpd8lItQM95HFFS X-Received: by 10.236.221.168 with SMTP id r38mr5437065yhp.137.1418980356695; Fri, 19 Dec 2014 01:12:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.170.69.135 with HTTP; Fri, 19 Dec 2014 01:11:56 -0800 (PST) In-Reply-To: <1418978947667-4175188.post@n3.nabble.com> References: <1418978947667-4175188.post@n3.nabble.com> From: Mikhail Khludnev Date: Fri, 19 Dec 2014 12:11:56 +0300 Message-ID: Subject: Re: SOLR complex queries misunderstanding To: solr-user Content-Type: multipart/alternative; boundary=001a11c2cb7e1ac0ce050a8e1c27 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2cb7e1ac0ce050a8e1c27 Content-Type: text/plain; charset=UTF-8 Hello Nick, First of all, if you don't understand the results ask Solr to explain by debugQuery=true. The output is reeeeaally verbose and puzzling. That is. Then, I guess you tries to implement something like 'refinement', filtering aka faceted navigation. Try to supply the filtering clause via fq=.. . Filter queries don't influence scoring. eg fq=(text:(specific) OR title:(specific))&q=(text:(first long query) OR title:(first long query)) If I get your question right, you are puzzled by the weighting/normalization, which works pretty puzzling for multiple clauses queries with deep nesting. That is. On Fri, Dec 19, 2014 at 11:49 AM, Norgorn wrote: > > I'm trying to implement specifying queries - we have some results and need > to > search over them. > But query, I constructed, returns some strange results. > > q=(text:(specific) OR title:(specific)) AND (text:(first long query) OR > title:(first long query)) > > This query returns something, which contains "specific", but not "first > long query", but result differs a lot from simple "q=(text:(specific) OR > title:(specific))". > > I tried the following with same results: > q=(text:(specific) OR title:(specific)) +(text:(first long query) OR > title:(first long query)) > q=(text:(specific) OR title:(specific)) AND _query_:"(text:(first long > query) OR title:(first long query))" > > I'm sure, that this is the real query, going to SOLR, cause I checked it > before sending (SolrQuery.toString()) > > I can't find out what exactly am I misunderstanding (and what results am I > getting - they are really strange). > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SOLR-complex-queries-misunderstanding-tp4175188.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Sincerely yours Mikhail Khludnev Principal Engineer, Grid Dynamics --001a11c2cb7e1ac0ce050a8e1c27--