lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ritesh Nigam (JIRA)" <>
Subject [jira] Commented: (LUCENE-2280) IndexWriter.optimize() throws NullPointerException
Date Thu, 18 Mar 2010 13:27:27 GMT


Ritesh Nigam commented on LUCENE-2280:

I installed a test setup with lucene 3.0.0 and tried to reproduce the scenario with NPE, but
after the Exception thrown, main index file is not getting deleted but only optimize is failing
and i can see some small index file (.cfs) also along with main index file, and one more thing
here is i am not using commit yet, but using close(), does close do the same thing as commit

By looking at above behavior, is there a bug in 2.3.2 version where this kind of situaion
is not handled properly?

Can you please have a look at the log which i got after turning on the infostream for IndexWriter(for
lucene 2.3.2). Attached as

> 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
>         Attachments: lucene.jar,
> 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