Chris Hostetter wrote:
>
> This is one of the reasons why i was suggesting in a java-dev thread that
> *all* of the refrences to SegmentInfos be refactored out of IndexReader
> and into the subclasses -- any attempt to access the SegmentInfos in a
OK, I'm convinced that we should refactor segment
: I agree segmentInfos are not needed in this case. But it's used in
: aquireWriteLock(). What should we do?
This is one of the reasons why i was suggesting in a java-dev thread that
*all* of the refrences to SegmentInfos be refactored out of IndexReader
and into the subclasses -- any attempt to
Right now I am very confused.
I agree segmentInfos are not needed in this case. But it's used in
aquireWriteLock(). What should we do?
--
Chris Lu
-
Instant Scalable Full-Text Search On Any Database/Application
site: http://www.dbsight.net
demo: http://search.dbsight.com
: I found out in latest MultiReader.java, the "SegmentInfos" is set to null.
: However, segmentInfos are used in several places, causing NPEs.
: For example, in IndexReader.acquireWriteLock(),
MultiReader was refactored into two classes: MultiReader which is now only
constructed from other reade
Hi, Eric, I think I have the same problem.
I found out in latest MultiReader.java, the "SegmentInfos" is set to null.
public MultiReader(IndexReader[] subReaders) throws IOException {
super(subReaders.length == 0 ? null : subReaders[0].directory(),
null, false, subReaders);
}
H
Eric Louvard wrote:
> Hello while calling IndexReader.deletedoc(int) I am becomming a NPE.
>
> java.lang.NullPointerException
>at
> org.apache.lucene.index.IndexReader.acquireWriteLock(IndexReader.java:658)
>at
> org.apache.lucene.index.IndexReader.deleteDocument(IndexReader.java:6
Hello while calling IndexReader.deletedoc(int) I am becomming a NPE.
java.lang.NullPointerException
at
org.apache.lucene.index.IndexReader.acquireWriteLock(IndexReader.java:658)
at
org.apache.lucene.index.IndexReader.deleteDocument(IndexReader.java:686)
In the acquireWriteLock m
