Quick side note: The recommended upgrade path is to upgrade to 2.9.latest,
fix all of the deprecation warnings, *then* upgrade to 3.0. The 2.9.X -> 3.0
upgrade just removed all the deprecated stuff.....


On Mon, Mar 8, 2010 at 8:51 AM, Ritesh Nigam (JIRA) <jira@apache.org> wrote:

   [ https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842657#action_12842657 ]

Ritesh Nigam commented on LUCENE-2280:

I checked the documentation of IndexWriter in 2.3.2, API commit() is not available with this version (I think it is introduced in 2.4), I am not explicitely setting autoCommit, so it should take default value which I believe is "true".

One more thing I am catching any exception hitting during indexing or optimizing, and then in finally block i am closing the IndexWriter by calling close(), method which sould take care of commit internally? Please suggest me if there is any equivalent method which i can use in place of commit()

I have not upgraded to the newer version of lucene, but probably i will try 3.0.0 version of lucene in future.

> IndexWriter.optimize() throws NullPointerException
> --------------------------------------------------
>                 Key: LUCENE-2280
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2280
>             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 says
> ------------------------------------------------------------------------
> Caused by:
> java.lang.NullPointerException
>       at org.apache.lucene.store.BufferedIndexOutput.writeBytes(BufferedIndexOutput.java:49)
>       at org.apache.lucene.store.IndexOutput.writeBytes(IndexOutput.java:40)
>       at org.apache.lucene.index.SegmentMerger.mergeNorms(SegmentMerger.java:566)
>       at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:135)
>       at org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3273)
>       at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2968)
>       at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:240)
> ------------------------------------------------------------------------
> 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 (http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200809.mbox/%3C6E4A40DB-5EFC-42DA-A857-D59F4EC3496B@mikemccandless.com%3E) 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org