Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 97259 invoked from network); 14 May 2009 18:41:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 May 2009 18:41:29 -0000 Received: (qmail 39516 invoked by uid 500); 14 May 2009 18:41:26 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 39478 invoked by uid 500); 14 May 2009 18:41:26 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 39446 invoked by uid 99); 14 May 2009 18:41:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2009 18:41:26 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2009 18:41:17 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M4frU-0000AI-Pa for solr-dev@lucene.apache.org; Thu, 14 May 2009 11:40:56 -0700 Message-ID: <23546176.post@talk.nabble.com> Date: Thu, 14 May 2009 11:40:56 -0700 (PDT) From: "jayson.minard" To: solr-dev@lucene.apache.org Subject: Re: Lucene errors with latest Solr tip In-Reply-To: <23546165.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jayson.minard@gmail.com References: <23545805.post@talk.nabble.com> <23546134.post@talk.nabble.com> <23546165.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Since Yonik answered over on the Lucene side, continuing this there: http://www.nabble.com/Getting-errors-reading-lucene-indexes-using-recent-lucene-from-Solr-td23545868.html#a23546172 jayson.minard wrote: > > Code used is this: > > Directory directory = new FSDirectory(new File(luceneIndexDir), null); > reader = IndexReader.open(directory, true); // open directory read-only > > ... > reader.document(curDoc++, FIELD_SELECTOR); > ... > > and it bombs on the document() call. > > > > jayson.minard wrote: >> >> This is with an optimized index. If I copy it back into the index dir, >> Solr opens it up fine and searches it. But the code opening and scanning >> via Lucene fails on the same data. >> >> >> jayson.minard wrote: >>> >>> After using latest Solr tip I now get errors in Lucene during >>> post-optimize callbacks that scan the index. >>> >>> java.lang.IndexOutOfBoundsException: Index: 24, Size: 0 >>> at java.util.ArrayList.RangeCheck(ArrayList.java:547) >>> at java.util.ArrayList.get(ArrayList.java:322) >>> at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:253) >>> at org.apache.lucene.index.FieldsReader.doc(FieldsReader.java:218) >>> at >>> org.apache.lucene.index.SegmentReader.document(SegmentReader.java:914) >>> >>> I'll report this over in Lucene, but might be endangering current tip. >>> Not sure if bug is on read or write side. >>> >>> --j >>> >> >> > > -- View this message in context: http://www.nabble.com/Lucene-errors-with-latest-Solr-tip-tp23545805p23546176.html Sent from the Solr - Dev mailing list archive at Nabble.com.