positionIncrementGap is only really relevant for phrase searches. For non-phrase searches you can effectively ignore it.
The problem here is what you mean by "consecutive element". In your original example, if you mean that searching for "michael singer" should NOT match, then you want to use phrase searches with a positionIncrementGap as Tanguy says and no slop. Maybe this will help. The purpose of setting positionIncrementGap to non-zero is to do the opposite of what you want. Say each entry in a multiValued field is a sentence and you do NOT want a search that contains words in two different sentences to match. Say further that your sentences will never be longer than 100 words. Setting positionIncrementGap to 100 and using phrases for all your searches like this "word search"~100 would guarantee that no match would occur for a document in which one sentence contained "word" and another sentence contained "search", but documents *would* match where single sentence contained both words. Best Erick On Thu, Dec 22, 2011 at 1:17 AM, meghana <meghana.rav...@amultek.com> wrote: > Hi Tanguy, > > Thanks for your reply.. this is really useful. but i have one questions on > that. > > my multivalued field is not just simple text. it has values like below > <str>1s:[This is very nice day.]</str> > <str>3s:[Christmas is about come and christmas]</str> > <str>4s:[preparation is just on ]</str> > now i if i search with "christmas preparation" , then this should match. if > i set positionIncrementGap to 0 then do it will match? Or how value of > positionIncrementGap behave on my search? > > Meghana > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Mutivalue-field-search-on-different-elements-tp3604213p3605938.html > Sent from the Solr - User mailing list archive at Nabble.com.
