svn commit: r477207 - /lucene/java/trunk/CHANGES.txt

[yo...@apache.org]

Author: yonik
Date: Mon Nov 20 06:51:50 2006
New Revision: 477207

URL: http://svn.apache.org/viewvc?view=rev&rev=477207
Log:
expanded description of LUCENE-651

Modified:
    lucene/java/trunk/CHANGES.txt

Modified: lucene/java/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/java/trunk/CHANGES.txt?view=diff&rev=477207&r1=477206&r2=477207
==============================================================================
--- lucene/java/trunk/CHANGES.txt (original)
+++ lucene/java/trunk/CHANGES.txt Mon Nov 20 06:51:50 2006
@@ -193,7 +193,10 @@
     IOException after acquiring the write lock but before finishing
     instantiation. (Matthew Bogosian via Mike McCandless)
 
-22. LUCENE-651: Fixed a race condition in initialization of FieldCache.
+22. LUCENE-651: Multiple different threads requesting the same
+    FieldCache entry (often for Sorting by a field) at the same
+    time caused multiple generations of that entry, which was
+    detrimental to performance and memory use.
     (Oliver Hutchison via Otis Gospodnetic)
 
 Optimizations

Re: svn commit: r477207 - /lucene/java/trunk/CHANGES.txt

[Yonik Seeley <yo...@apache.org>]

On 11/20/06, yonik@apache.org <yo...@apache.org> wrote:
> -22. LUCENE-651: Fixed a race condition in initialization of FieldCache.
> +22. LUCENE-651: Multiple different threads requesting the same
> +    FieldCache entry (often for Sorting by a field) at the same
> +    time caused multiple generations of that entry, which was
> +    detrimental to performance and memory use.
>      (Oliver Hutchison via Otis Gospodnetic)

I changed this because "race condition" implies different (and
incorrect) results depending on the ordering of events.  Unless
someone was having performance problems, this isn't a bug they needed
to worry about.

-Yonik