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 A431918E68 for ; Thu, 10 Sep 2015 10:37:42 +0000 (UTC) Received: (qmail 99773 invoked by uid 500); 10 Sep 2015 10:37:41 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 99711 invoked by uid 500); 10 Sep 2015 10:37:41 -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 Received: (qmail 99697 invoked by uid 99); 10 Sep 2015 10:37:40 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Sep 2015 10:37:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3F2FD1A0BC1 for ; Thu, 10 Sep 2015 10:37:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.101 X-Spam-Level: ***** X-Spam-Status: No, score=5.101 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_COUK=1.1, KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id RhZAtrX5yFny for ; Thu, 10 Sep 2015 10:37:30 +0000 (UTC) Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 4D0D3201FB for ; Thu, 10 Sep 2015 10:37:30 +0000 (UTC) Received: by lamp12 with SMTP id p12so24477822lam.0 for ; Thu, 10 Sep 2015 03:37:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:message-id:mime-version :subject:date:references:to:in-reply-to; bh=ffjpUPV8jV/g9FS0AcL0zGdtqVKJl5Y5xQQgYmBj5dA=; b=A2o1uhHB44qEJ8y90/sIA57dP6xcgeSXm2EDOY9V9C9MvNpzxbnWKhC1soCllKfj2E P675JbVyk6Arg8gRfd/97eeYwUa/1MJv3VBYXjhCrIfv40MNjUbt/rlUlqj8Z/IJLkyi G24SlUxymALs2pz5OfADaYq4xrbTJQMxCt04urXP0kjqad+g5w0zRuuFyt2HK8XBY7vy jg7JvQfVbsjwDGztlPk/+yDQn3q3UesexGjNRRlsAC8IW/h5uR6p8QG3dg/bb5JcM70G 5clcnpCI7C8iXWtHABZYEgudxd8d1O5wOYLePf6zamJlYgD+GSyw3JcRcGDqQLfaQLV5 M49g== X-Gm-Message-State: ALoCoQmwAy00Er7vphjcpXbjXzc1V6HaTF1m+BIoC/RoKU3k4YmBO/vYK8baLwaqXPaPhYXK31gh X-Received: by 10.112.140.104 with SMTP id rf8mr32168184lbb.30.1441881449658; Thu, 10 Sep 2015 03:37:29 -0700 (PDT) Received: from pc12299.corp.local ([91.214.20.181]) by smtp.gmail.com with ESMTPSA id da6sm887943lbb.47.2015.09.10.03.37.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Sep 2015 03:37:28 -0700 (PDT) From: Alan Woodward Content-Type: multipart/alternative; boundary="Apple-Mail=_85B73644-6529-4419-ACC8-E06BADEAE772" Message-Id: <3321F9BC-7F2D-4C7E-AA32-5CEC13F7F499@flax.co.uk> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Use SloppyPhraseScorer in SpanNearQuery Date: Thu, 10 Sep 2015 11:37:33 +0100 References: To: java-user@lucene.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1878.6) --Apple-Mail=_85B73644-6529-4419-ACC8-E06BADEAE772 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi, SpanNearQuery will also take into account the =91width=92 of the match, = so that terms that are closer together will score more highly. Is that = what you=92re looking for? Alan Woodward www.flax.co.uk On 10 Sep 2015, at 10:43, aurelien.mazoyer@francelabs.com wrote: > Hi all, >=20 > SpanNearQuery and SloppyPhraseQuery can have similar behavior in some = use cases. On the one hand, I have to distinguish between ordered and = unordered terms (that=92s enabled with SpanNearQuery) but on the other = hand, I want to use the SloppyPhraseScorer, that takes the relative = positions of the terms into account for the score calculation. As far I = understood, this is possible with SloppyPhraseQuery but not with = SpanNearQuery. Do you think there is there a way to combine these two = features to have the best of both worlds? >=20 > Thanks! >=20 > Aur=E9lien >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org >=20 --Apple-Mail=_85B73644-6529-4419-ACC8-E06BADEAE772--