Return-Path: 
 <solr-user-return-42581-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org
Received: (qmail 8315 invoked from network); 21 Oct 2010 04:19:12 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 21 Oct 2010 04:19:12 -0000
Received: (qmail 40363 invoked by uid 500); 21 Oct 2010 04:19:10 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 40052 invoked by uid 500); 21 Oct 2010 04:19:09 -0000
Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-user-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-user-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-user@lucene.apache.org>
List-Id: <solr-user.lucene.apache.org>
Reply-To: solr-user@lucene.apache.org
Delivered-To: mailing list solr-user@lucene.apache.org
Received: (qmail 40044 invoked by uid 99); 21 Oct 2010 04:19:09 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Oct 2010 04:19:09 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of Jason.Brown@sjp.co.uk
 designates 217.64.225.170 as permitted sender)
Received: from [217.64.225.170] (HELO mail.sjp.co.uk) (217.64.225.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Oct 2010 04:19:01 +0000
Received: from sjp10exc04vm.sjp.co.uk (Not Verified[10.44.90.107]) by
 mail.sjp.co.uk with MailMarshal (v6,7,2,8378)
	id <B4cbfbf200000>; Thu, 21 Oct 2010 05:18:40 +0100
Received: from SJP10VEX02.sjp.co.uk ([10.44.91.161]) by sjp10exc04vm.sjp.co.uk
 with Microsoft SMTPSVC(6.0.3790.3959);
	 Thu, 21 Oct 2010 05:18:40 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01CB70D7.09D7C785"
Subject: RE: Dismax phrase boosts on multi-value fields
Date: Thu, 21 Oct 2010 05:16:38 +0100
Message-ID: <E84B412318790649B9B694EBD5139E9895CB52@SJP10VEX02.sjp.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
 <E84B412318790649B9B694EBD5139E9895CB52@SJP10VEX02.sjp.co.uk>
Thread-Topic: Dismax phrase boosts on multi-value fields
Thread-Index: ActwrDNKwP2ZGeymRmaYGq8rTTAadQAEvP7CAAXmkF0=
References: <E84B412318790649B9B694EBD5139E9895CB30@SJP10VEX02.sjp.co.uk>
 <E84B412318790649B9B694EBD5139E9895CB32@SJP10VEX02.sjp.co.uk>
 <E84B412318790649B9B694EBD5139E9895CB3D@SJP10VEX02.sjp.co.uk>
 <4CBDC6E1.5010405@jhu.edu>
 <E84B412318790649B9B694EBD5139E9895CB40@SJP10VEX02.sjp.co.uk>,<AANLkTinhgS+MVhP_zOxRK+6WczC8uGnEBpb2ng9CQto=@mail.gmail.com>
 <90FF863A96E1EC42B8B240D04C88FB1D133E5E86E2@JHEMTEXVS2.win.ad.jhu.edu>
From: "Jason Brown" <Jason.Brown@sjp.co.uk>
To: <solr-user@lucene.apache.org>
X-OriginalArrivalTime: 21 Oct 2010 04:18:40.0684 (UTC)
 FILETIME=[0A832EC0:01CB70D7]
X-Virus-Checked: Checked by ClamAV on apache.org

------_=_NextPart_001_01CB70D7.09D7C785
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks - I was hoping it wouldnt match - and I belive you've confimred it=
=20wont in my case as the default positionIncrementGap is set.

Many Thanks

Jason.


-----Original Message-----
From: Jonathan Rochkind [mailto:rochkind@jhu.edu]
Sent: Thu 21/10/2010 02:27
To: solr-user@lucene.apache.org
Subject: RE: Dismax phrase boosts on multi-value fields
=20
Which is why the positionIncrementGap is set to a high number normally (1=
00 in the sample schema.xml).  With this being so, phrases won't match ac=
cross values in a multi-valued field. If for some reason you were using a=
=20dismax ps phrase slop that was higher than your positionIncrementGap, =
you could get phrase boost matches accross individual values.  But normal=
ly that won't happen unless you do something odd to make it happen becaus=
e you actually want it to, because positionIncrementGap is 100. If for so=
me reason you wanted to use a phrase slop of over 100 but still make sure=
=20it didn't go accross individual value boundaries you could just set po=
sitionIncrementGap to something absurdly high (I'm not entirely sure why =
it isn't something absurdly high in the sample schema.xml, instead of the=
=20high-but-not-absurdly-so 100, since most people will probably expect i=
ndividual values to be entirely seperate).=20

Jason, are you _trying_ to make that happen, or hoping it won't?  Ordinar=
ily, it won't.=20
________________________________________
From: Erick Erickson [erickerickson@gmail.com]
Sent: Wednesday, October 20, 2010 7:11 PM
To: solr-user@lucene.apache.org
Subject: Re: Dismax phrase boosts on multi-value fields

Well, it all depends (tm). your example wouldn't match, but if you
didn't have an increment gap greater than 1, "black cat his blue" #would#=

match.

Best
Erick


On Wed, Oct 20, 2010 at 3:22 AM, Jason Brown <Jason.Brown@sjp.co.uk> wrot=
e:

> Thanks Jonathan.
>
> To further clarify, I understand the the match of
>
> my blue rabbit
>
> would have to be found in 1 element (of my multi-valued defined field) =
for
> the phrase boost on that field to kick in.
>
> If for example my document had the following 3 entries for the multi-va=
lue
> field....
>
>
> my black cat
> his blue car
> her pink rabbit
>
> Then I assume the phrase boost would not kick-in as the search term (my=

> blue rabbit) isnt found in a single element (but can be found across th=
em).
>
> Thanks again
>
> Jason.
>
> ________________________________
>
> From: Jonathan Rochkind [mailto:rochkind@jhu.edu]
> Sent: Tue 19/10/2010 17:27
> To: solr-user@lucene.apache.org
> Subject: Re: Dismax phrase boosts on multi-value fields
>
>
>
> You are correct.  The query needs to match as a phrase. It doesn't need=

> to match "everything". Note that if a value is:
>
> "long sentence with my blue rabbit in it",
>
> then query "my blue rabbit" will also match as a phrase, for phrase
> boosting or query purposes.
>
> Jonathan
>
> Jason Brown wrote:
> >
> >
> > Hi - I have a multi-value field, so say for example it consists of
> >
> > 'my black cat'
> > 'my white dog'
> > 'my blue rabbit'
> >
> > The field is whitespace parsed when put into the index.
> >
> > I have a phrase query boost configured on this field which I understa=
nd
> kicks in when my search term is found entirely in this field.
> >
> > So, if the search term is 'my blue rabbit', then I understand that my=

> phrase boost will be applied as this is found entirley in this field.
> >
> > My question/presumption is that as this is a multi-valued field, only=
=201
> value of the multi-value needs to match for the phrase query boost (giv=
en my
> very imaginative set of test data :-) above, you can see that this obvi=
ously
> matches 1 value and not them all)
> >
> > Thanks for your help.
> >
> >
> >
> >
> >
> >
> > If you wish to view the St. James's Place email disclaimer, please us=
e
> the link below
> >
> > http://www.sjp.co.uk/portal/internet/SJPemaildisclaimer
> >
> >
>
>
>
> If you wish to view the St. James's Place email disclaimer, please use =
the
> link below
>
> http://www.sjp.co.uk/portal/internet/SJPemaildisclaimer
>


If you wish to view the St. James's Place email disclaimer, please use th=
e link below

http://www.sjp.co.uk/portal/internet/SJPemaildisclaimer

------_=_NextPart_001_01CB70D7.09D7C785--