Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-10 Thread Jack Krupansky
: positionIncrementGap in schema.xml - Doesn't seem to work Hi Jack, This works perfect. But the trouble comes when i query for wild cards. In that case i will not be using double quotes. So in that case what should i do? Thanks. On Mon, Feb 10, 2014 at 1:18 PM, Jack Krupansky-2 [via Lucene] <

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-10 Thread Kashish
; > That should not match your second document. But, > > "Eric solrUser"~102 > > would match. > > -- Jack Krupansky > > -Original Message- > From: Nirali Mehta > Sent: Monday, February 10, 2014 3:13 PM > To: [hidden email] <http://user/Sen

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-10 Thread Jack Krupansky
"Eric solrUser"~102 would match. -- Jack Krupansky -Original Message- From: Nirali Mehta Sent: Monday, February 10, 2014 3:13 PM To: solr-user@lucene.apache.org Subject: Re: positionIncrementGap in schema.xml - Doesn't seem to work Erick, Here is the example. The

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-10 Thread Nirali Mehta
Erick, Here is the example. There is a multivalued field 'name'. 1 document has following fields 1. Erick Erickson 2. Kashish Solruser 3. Some other user 2nd doc has following fields. 1. Erickson Eric 2. SolrUser Kashish Now we have designed our app in such a way that -> if the user gives any in

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-10 Thread Erick Erickson
Nirali: I really have no clue what you're trying to accomplish. Some examples of inputs and outputs would help. I really don't understand what multivalued fields have to do with your problem statement, it seems like you're getting the expected behavior. What's happening that shouldn't? Joins don'

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-10 Thread Nirali Mehta
Erick, I understand what you explaining to me. Let em point out few stuffs that i face W.R.T my field type that i mentioned in my first mail. 1. If the user explicityly gives double quotes, we search for exact phrases in exact order. 2. If they don't, its understood that they would just want those

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-10 Thread Erick Erickson
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 yo

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-09 Thread Kashish
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%20A

Re: positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-09 Thread Erick Erickson
Well, let's see the results of adding &debug=query to the URL, and let's see the actual query. you have to re-index after the change. You MUST be using phrases exclusively, i.e. name:"Erick Erickson". name:(Erick Erickson) will not mind the gap since the latter is not a phrase. You may well be s

positionIncrementGap in schema.xml - Doesn't seem to work

2014-02-09 Thread Kashish
Hi, I read about 'positionIncrementGap'. The purpose of it is very clear to me. I use eDismax query with my multivalued fields as I made sure that all the points me

Re: positionIncrementGap in schema.xml

2011-07-31 Thread randohi
It is not in stopwords list. The file was indexed with the following setting: Field Type: text_en Properties: Indexed, Tokenized, Stored, Multivalued Schema: Indexed, Tokenized, Stored, Multivalued Index: Indexed, Tokenized, Stored Position Increment Gap: 100 Index Analyzer: org.apache.solr.a

Re: positionIncrementGap in schema.xml

2008-10-06 Thread Erik Hatcher
he virtual space between the last token of one field instance and the first token of the next instance. With a gap of 100, this prevents phrase queries (even with a modest slop factor) from matching across instances. Erik -- View this message in context: http://www.nabb

Re: positionIncrementGap in schema.xml

2008-10-05 Thread sanraj25
nd the first token > of the next instance. With a gap of 100, this prevents phrase queries > (even with a modest slop factor) from matching across instances. > > Erik > > > -- View this message in context: http://www.nabble.com/positionIncrementGap-in-schema.xml-tp19794338p19832472.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: positionIncrementGap in schema.xml

2008-10-03 Thread Chris Hostetter
: Hi : what is the purpose of positionIncrementGap attribute in field : type tag of schema.xml. The value specified for that : positionIncrementGap=100. If we change the value what will happen? searching either the wiki, or google, or the example schema.xml answers this question... ht

Re: positionIncrementGap in schema.xml

2008-10-03 Thread Erik Hatcher
On Oct 3, 2008, at 5:10 AM, sanraj25 wrote: what is the purpose of positionIncrementGap attribute in field type tag of schema.xml. The value specified for that positionIncrementGap=100. If we change the value what will happen? Suppose a document has a multi-valued "author" field.

positionIncrementGap in schema.xml

2008-10-03 Thread sanraj25
/positionIncrementGap-in-schema.xml-tp19794338p19794338.html Sent from the Solr - User mailing list archive at Nabble.com.