This is because, within one segment only 1 value (omitP or not) is
possible, for all the docs in that segment.
This then means, on merging segments with different values for omitP,
Lucene must "reconcile" the different values, and that reconciliation
will favor omitting positions (if it went the o
Hi Mike,
Thanks for the information.But why is it that once omiited positions in the
past , it will always omit positions
even if omitPositions is made false.
Thanks,
Isan Fulia.
On 29 September 2011 17:49, Michael McCandless wrote:
> Once a given field has omitted positions in the past, even f
Once a given field has omitted positions in the past, even for just
one document, it "sticks" and that field will forever omit positions.
Try creating a new index, never omitting positions from that field?
Mike McCandless
http://blog.mikemccandless.com
On Thu, Sep 29, 2011 at 1:14 AM, Isan Fuli
Hi All,
My schema consisted of field textForQuery which was defined as
After indexing 10 lakhs of documents I changed the field to
So documents that were indexed after that omiited the position information
of the terms.
As a result I was not able to search the text which rely on position
in
