[
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842710#action_12842710
]
Michael McCandless commented on LUCENE-2280:
--------------------------------------------
bq. 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".
Ahh right sorry. Hard to remember that far back!
bq. 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()
That's right, though, Lucene doesn't call "fsync" (to the OS) in
2.3.x... so if the machine/OS crashes it could corrupt your index. So
it's not quite doing the same thing as commit() does in newer Lucene
releases (ensure durability), but it does save everything to the
index.
bq. I have not upgraded to the newer version of lucene, but probably i will try
3.0.0 version of lucene in future.
OK.
> 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-d59f4ec34...@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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
