Re: Copying few field using copyField to non multiValued field

2012-11-27 Thread Erick Erickson
It Depends (tm). In this case on what you mean by "exact match". In Solr land, that has a precise meaning of a single token. So in your example it wouldn't match since you have two tokens that happen to be next to each other, not a single token"billy corgan". But if you mean that you want a match

Re: Copying few field using copyField to non multiValued field

2012-11-26 Thread Barry Galaxy
thanx erick! oh, there was a typo in my example... i meant: /*full_name = first_name + last_name */ you are correct, i would like to use keywordtokenizer to get an exact hit on a query such as: full_name:"Billy Corgan" coming from a source document with: */Billy & Corgan/* is this possible

Re: Copying few field using copyField to non multiValued field

2012-11-23 Thread Erick Erickson
Barry: This is just an artifact of the output. If you set positionIncremenGap to 1 (or maybe 0, but I think 1) then phrase searches will work just fine across multiple entries. With the proper setting for positionIncrementGap, there is really no difference between multiValued and non-multiValued f

Re: Copying few field using copyField to non multiValued field

2012-11-21 Thread Barry Galaxy
i would also like to copy a few fields to a single-valued field. my reasoning for this is to then perform exact-match search on the concatenated field. e.g. full_name = first_name + last+name i would then like to search: full_name:"john foo" but copyField is making the full_name field look like

Re: Copying few field using copyField to non multiValued field

2011-06-16 Thread Michael Kuhlmann
Hi Omri, there are two limitations: 1. You can't sort on a multiValued field. (Anyway, on which of the copied fields would you want to sort first?) 2. You can't make the multiValued field the unique key. Both are no real limitations: 1. Better sort on at_country, at_state, at_city instead. 2. Sim

Re: Copying few field using copyField to non multiValued field

2011-06-15 Thread Omri Cohen
er | SirsiDynix > P: 800.288.8020 X6943 | bob.sandif...@sirsidynix.com > www.sirsidynix.com > > > > -Original Message- > > From: Omri Cohen [mailto:omri...@gmail.com] > > Sent: Wednesday, June 15, 2011 8:42 AM > > To: solr-user@lucene.apache.org > >

Re: Copying few field using copyField to non multiValued field

2011-06-15 Thread Michael Kuhlmann
In addition to Bob's response: Am 15.06.2011 13:59, schrieb Omri Cohen: [...] > stored="true" required="false" /> > stored="true" required="false" /> > stored="true" required="false" /> > stored="true" required="false" />. 1. The value for "indexed" should either be "true" or "fals

Re: Copying few field using copyField to non multiValued field

2011-06-15 Thread Jan Høydahl
How would the resulting single-valued field look like? Concatenate all input fields into one long string? If that's what you need, I've written a FieldCopy UpdateProcessor which can do that. I'll contribute it in https://issues.apache.org/jira/browse/SOLR-2599 -- Jan Høydahl, search solution ar

Re: Copying few field using copyField to non multiValued field

2011-06-15 Thread Gora Mohanty
On Wed, Jun 15, 2011 at 6:11 PM, Omri Cohen wrote: > thanks for the quick response, though as I said in my original post: > > *"some one has any idea, how I solve this without changing at_location to > multiField? "* [...] This requirement makes little sense on the face of it, and as far as I kno

RE: Copying few field using copyField to non multiValued field

2011-06-15 Thread Bob Sandiford
andiford | Lead Software Engineer | SirsiDynix P: 800.288.8020 X6943 | bob.sandif...@sirsidynix.com www.sirsidynix.com > -Original Message- > From: Omri Cohen [mailto:omri...@gmail.com] > Sent: Wednesday, June 15, 2011 8:42 AM > To: solr-user@lucene.apache.org > Subject: Re: Cop

Re: Copying few field using copyField to non multiValued field

2011-06-15 Thread Omri Cohen
thanks for the quick response, though as I said in my original post: *"some one has any idea, how I solve this without changing at_location to multiField? "* thank you very much though * * *Omri Cohen* Co-founder @ yotpo.com | o...@yotpo.com | +972-50-7235198 | +972-3-6036295 My profiles

RE: Copying few field using copyField to non multiValued field

2011-06-15 Thread Bob Sandiford
Omri - you need to indicate to Solr that your at_location field can accept multiple values. Add this to the field declaration: multiValued="true" See this reference for more information / options: http://wiki.apache.org/solr/SchemaXml Bob Sandiford | Lead Software Engineer | SirsiDyn