Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Date: 13 Feb 2004 12:44:50 -0000
Message-ID: <20040213124450.4129.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: lucene-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 26666]  -
    Endless loop since lucene 1.4RC1

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26666>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26666

Endless loop since lucene 1.4RC1


------- Additional Comments From julien.nioche@lingway.com  2004-02-13 12:44 -------
the endless loop is in the next() method of the BooleanScorer. The 'more'
variable is set to true even all the subscorers are done.
Forcing this value to false with a debugger makes the method return nicely - the
number of docs is correct as well. I just need to understand how this more
variable has been changed to 'true'.

This problem appears with any of my indices in 1.3 or 1.4 version. I tried to
create a RAMDirectory in a test file and populate it with some data but the
problem does not appear in that case.

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org