Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@www.apache.org Received: (qmail 83610 invoked from network); 28 Oct 2004 05:09:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Oct 2004 05:09:01 -0000 Received: (qmail 18899 invoked by uid 500); 28 Oct 2004 05:08:57 -0000 Delivered-To: apmail-jakarta-lucene-dev-archive@jakarta.apache.org Received: (qmail 18865 invoked by uid 500); 28 Oct 2004 05:08:56 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 18850 invoked by uid 99); 28 Oct 2004 05:08:56 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Wed, 27 Oct 2004 22:08:56 -0700 Received: (qmail 1896 invoked by uid 50); 28 Oct 2004 05:10:59 -0000 Date: 28 Oct 2004 05:10:59 -0000 Message-ID: <20041028051059.1895.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: lucene-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 31926] - Exception getting terms from IndexReader X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31926 Exception getting terms from IndexReader ephemeris.lappis@tiscali.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From ephemeris.lappis@tiscali.fr 2004-10-28 05:10 ------- I've been inspecting my code more closely, and i finally discovered a mistake : it closed the reader before the end of the enumeration. I suppose that in case of few occurences, all the terms can be loaded in a single read, but when the index contains more terms, the enumerator probably comes back to the reader to get data progressively. Logical... and fine !!! So... no bug ! Sorry for troubles... and thanks anyway. --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-dev-help@jakarta.apache.org