You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2009/08/28 15:36:59 UTC
[jira] Resolved: (LUCENE-1869) when checking tvx/fdx size mismatch,
also include whether the file exists
[ https://issues.apache.org/jira/browse/LUCENE-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-1869.
----------------------------------------
Resolution: Fixed
> when checking tvx/fdx size mismatch, also include whether the file exists
> -------------------------------------------------------------------------
>
> Key: LUCENE-1869
> URL: https://issues.apache.org/jira/browse/LUCENE-1869
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Trivial
> Fix For: 2.9
>
> Attachments: LUCENE-1869.patch
>
>
> IndexWriter checks, during flush and during merge, that the size of the index file for stored fields (*.fdx) and term vectors (*.tvx) matches how many bytes it has just written.
> This originally was added for LUCENE-1282, ie, as a safety to catch the nasty "off by 1" JRE hotspot bug that would otherwise silently corrupt the index.
> However, this check also seems to catch a different case, where the size of the file is zero. The most recent example is LUCENE-1521. I'd like to improve the message in the exception to include whether or not the file exists, to help understand why users are sometimes hitting this exception. My best theory at this point is something external is removing the file out from under the IndexWriter.
--
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