lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <>
Subject Re: Lucene 1.4.2?
Date Mon, 20 Sep 2004 16:49:13 GMT
To be clear, you are proposing that we branch from the 1.4.1 tag in CVS 
and re-apply the patches below?  I'm not opposed to that, if you 
volunteer to do the work.

I also agree with Otis that we should wait until we have a good solution 
to the Sort-related memory leak issue before we make a release.

Finally, I don't think this is urgent.  Except for #4 below, these bugs 
don't break applications that worked prior 1.4.  The Sort-related bugs 
are bugs in a new feature that has never worked correctly.  In general 
we should urgently fix bugs in code that previously worked correctly. 
Fixing bugs in new features is important, but a lower priority.

Re #4: Did this fix a bug that was introduced in 1.4, or had the bug 
always been there?


Daniel Naber wrote:
> This bug could actually lead to incorrect results. So what about releasing 
> Lucene 1.4.2? Here is a list of fixes that could be part of that release:
> -4. Fixed a bug in IndexWriter.addIndexes(IndexReader[] readers) that
>     prevented deletion of obsolete segments. (Christoph Goller)
> -13. Fixed bug #31241: Sorting could lead to incorrect results (documents
>     missing, others duplicated) if the sort keys were not unique and there
>     were more than 100 matches. (Daniel Naber)
> -There was a compile problem with StandardTokenizer.jj because of an 
> missing import.
> Opinions?
> Regards
>  Daniel

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message