On Wed, May 8, 2013 at 9:03 AM, AarKay wrote:
> Thanks Mike. This is little bit clear to me now.
>
> Just to make sure I got it right, do you mean that we need to store just
> the offsets and set IndexOptions to DOCS_AND_FREQS_AND_POSITIONS_AND_OFFSETS
> to be able to use PostingsHighlighter?
> Al
Thanks Mike. This is little bit clear to me now.
Just to make sure I got it right, do you mean that we need to store just
the offsets and set IndexOptions to DOCS_AND_FREQS_AND_POSITIONS_AND_OFFSETS
to be able to use PostingsHighlighter?
Also we don't need to store TermVectors and Positions. Corre
OK this is a real bug; I opened
https://issues.apache.org/jira/browse/LUCENE-4986
Thanks Reg!
Mike McCandless
http://blog.mikemccandless.com
On Wed, May 8, 2013 at 7:09 AM, Michael McCandless
wrote:
> On Tue, May 7, 2013 at 8:12 PM, Reg wrote:
>> There you go. By the way, love your blogs.
>
On Tue, May 7, 2013 at 8:12 PM, Reg wrote:
> There you go. By the way, love your blogs.
Thanks :)
OK I got the test case ... I'll dig!
Mike McCandless
http://blog.mikemccandless.com
-
To unsubscribe, e-mail: java-user-unsubs
On Wed, May 8, 2013 at 4:23 AM, AarKay wrote:
> I see that Lucene 4.x has FieldInfo.IndexOptions that can be used to tell
> lucene whether to Index Documents/Frequencies/Positions/Offsets.
>
> We are in the process of upgrading from Lucene 2.9 to Lucene 4.x and I was
> wondering if there was a way
I see that Lucene 4.x has FieldInfo.IndexOptions that can be used to tell
lucene whether to Index Documents/Frequencies/Positions/Offsets.
We are in the process of upgrading from Lucene 2.9 to Lucene 4.x and I was
wondering if there was a way to tell lucene whether to index
docs/freqs/pos/offsets
