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.
