Andrzej Bialecki wrote:
Michael McCandless wrote:
+1
I guess we'd add a Fieldable.setOmitPositions? And then save that in
FieldInfos, and fix the postings writing/reading to respect it? Ie,
we can just change the index format. Encoding as negative numbers
Yes, that's what I had in mind. I was a bit shy of bumping the format
version, but likely there will be other changes that we can put under
the same next version of the format.
isn't great because the termFreq is written as a vInt, which consumes
5 bytes to encode any negative number. Wanna cough up a patch?
Heh .. that's the right term for it, I haven't looked at the details of
oal.index.* since 2.4-ish or so ... we'll see ;)
Ehh, sorry - I think I'll give up for now, after looking at the
combinatoric increase in the number of arguments to various indexing
classes ...
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
