Sanraj - did you reindex after adjusting the value of
positionIncrementGap? It is an index-time factor.
Erik
On Oct 6, 2008, at 2:12 AM, sanraj25 wrote:
Hi,
Thanks Erik .I am clear.But when I checked with multiValued=true
for a
single field ,I gave
positionIncrementGap=100.That time also mismatch. for ex,
author: John Doe
author: Bob Smith
a phrase query of "doe bob" now matched even i specified
positionIncrementGap=100.again I changed
positionIncrementGap=0.Now also doe bob matched.may I give 200 or
300 to
that value? give some suggestions.
Thanks
-sanraj
Erik Hatcher wrote:
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. Like this:
author: John Doe
author: Bob Smith
With a position increment gap of 0, a phrase query of "doe bob" would
be a match. But often it is undesirable for that kind of match
across
different field values. A position increment gap controls the
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.nabble.com/positionIncrementGap-in-schema.xml-tp19794338p19832472.html
Sent from the Solr - User mailing list archive at Nabble.com.
