lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jian chen" <>
Subject Re: storing term text internally as byte array and bytecount as prefix, etc.
Date Tue, 02 May 2006 02:24:36 GMT
Hi, Marvin,

Thanks for your quick response. I am in the camp of fearless refactoring,
even at the expense of breaking compatibility with previous releases. ;-)

Compatibility aside, I am trying to identify if changing the implementation
of Term is the right way to go for this problem.

If it is, I think it would be worthwhile rather than putting band-aid on the
existing API.



Changing the implementation of Term
> would have a very broad impact; I'd look for other ways to go about
> it first.  But I'm not an expert on SegmentMerger, as KinoSearch
> doesn't use the same technique for merging.
> My plan was to first submit a patch that made the change to the file
> format but didn't touch SegmentMerger, then attack SegmentMerger and
> also see if other developers could suggest optimizations.
> However, I have an awful lot on my plate right now, and I basically
> get paid to do KinoSearch-related work, but not Lucene-related work.
> It's hard for me to break out the time to do the java coding,
> especially since I don't have that much experience with java and I'm
> slow.  I'm not sure how soon I'll be able to get back to those
> bytecount patches.
> Marvin Humphrey
> Rectangular Research

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message