OK, nothing in that parsed query will respect positionIncrementGap. That is only relevant for _phrase_ queries and has no relevance to regular Boolean queries.
Using positionIncrementGap to keep matches from occurring across the gaps in multiValued field requires phrases and slop. I.e. lets say your gap is 100. Let's say you've indexed the following two values Erick Erickson Kashish Solruser Searching as you are for just +Erick +Kashish in the same field is only asking whether the terms appear anywhere and you'll get a match. Searching for "Erick Kashish" (with quotes) will fail because the positions are roughly 1 and 103. Likewise, searching "Erick Kashish"~100 will fail. Searching for "Erick Kashish"~110 will succeed because those two terms are less than 110 positions apart. So I really think you're misunderstanding the use of positionIncrementGap. What, from a high level, are you trying to accomplish? Best, Erick On Sun, Feb 9, 2014 at 7:19 PM, Kashish <nirali...@gmail.com> wrote: > Hi Erik, > Thanks for your reply. > > I am not using exact phrases here as i need to incorporate various forms of > searches. So i seperate the user input by 'AND clauses if the user > exclusively doesn't ask for exact match. > > I use the query as > > http://localhost:8983/solr/all/select?q=%28akaName:%28a%29%20AND%20akaName:%28team%29%29&debug=true > and my debug gives me > <str name="rawquerystring">(akaName:(a) AND akaName:(team))</str><str > name="querystring">(akaName:(a) AND akaName:(team))</str><str > name="parsedquery">(+(+akaName:a +akaName:team))/no_coord</str><str > name="parsedquery_toString">+(+akaName:a +akaName:team)</str> > > Is there any other better approach you suggest to me in this case? > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/positionIncrementGap-in-schema-xml-Doesn-t-seem-to-work-tp4116405p4116408.html > Sent from the Solr - User mailing list archive at Nabble.com. >
