lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-2280) IndexWriter.optimize() throws NullPointerException
Date Tue, 23 Feb 2010 11:48:27 GMT


Michael McCandless commented on LUCENE-2280:

Are you sure you're using a stock version 2.3.2 of Lucene?

I ask because... the line numbers in SegmentMerger (specifically 566) don't correlate to 2.3.2.
 The other line numbers do match.  It's odd.

But looking at the code I don't see how either of the arrays being passed to System.arraycopy
can be null.

Can you turn on IndexWriter's infoStream and capture & post the output?

It's also strange that this leads to index corruption; it shouldn't (the merge should just
fail, and the index should be untouched).  Can you run CheckIndex on the index and post what
corruption it uncovers.

Does this happen in a Sun JRE?

> IndexWriter.optimize() throws NullPointerException
> --------------------------------------------------
>                 Key: LUCENE-2280
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.3.2
>         Environment: Win 2003, lucene version 2.3.2, IBM JRE 1.6
>            Reporter: Ritesh Nigam
> I am using lucene 2.3.2 search APIs for my application, i am indexing 45GB database which
creates approax 200MB index file, after finishing the indexing and while running optimize()
i can see NullPointerExcception thrown in my log and index file is getting corrupted, log
> ------------------------------------------------------------------------
> Caused by: 
> java.lang.NullPointerException
> 	at
> 	at
> 	at org.apache.lucene.index.SegmentMerger.mergeNorms(
> 	at org.apache.lucene.index.SegmentMerger.merge(
> 	at org.apache.lucene.index.IndexWriter.mergeMiddle(
> 	at org.apache.lucene.index.IndexWriter.merge(
> 	at org.apache.lucene.index.ConcurrentMergeScheduler$
> ------------------------------------------------------------------------
> and this is happening quite frequently, although I am not able to reproduce it on demand,
I saw an issue logged which is some what related to mine issue (
but the only difference here is I am not using Store.Compress for my fields, i am using Store.NO
instead. please note that I am using IBM JRE for my application.
> Is this an issue with lucene?, if yes it is fixed in which version?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message