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 Lucene Database Search in 3 minutes: http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes On 8/21/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > > : 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 readers, and MultiSegmentReader which is what > IndexReader.open returns when a directory contans multiple segments ... > segmentInfos shouldn't be needed in the first case -- and doesn't make > much sense at all. > > > > -Hoss > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
