You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2008/11/13 23:36:46 UTC
[jira] Updated: (LUCENE-1452) Binary field content lost during
optimize
[ https://issues.apache.org/jira/browse/LUCENE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki updated LUCENE-1452:
--------------------------------------
Attachment: binaryField-junit.patch
Test case to illustrate the problem. This happens both in 2.4.0 and trunk, although the patch is from trunk.
Unfortunately, I don't know the reason for this behavior, so I can't provide a fix.
> Binary field content lost during optimize
> -----------------------------------------
>
> Key: LUCENE-1452
> URL: https://issues.apache.org/jira/browse/LUCENE-1452
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.4, 2.9
> Environment: Ubuntu 8.04, x86_64
> Java HotSpot(TM) 64-Bit Server VM (build 11.0-b15, mixed mode)
> Reporter: Andrzej Bialecki
> Attachments: binaryField-junit.patch
>
>
> Scenario:
> * create an index with arbitrary content, and close it
> * open IndexWriter again, and add a document with binary field (stored but not compressed)
> * close IndexWriter _without_ optimizing, so that the new document is in a separate segment.
> * open IndexReader. You can read the last document and its binary field just fine.
> * open IndexWriter, optimize the index, close IndexWriter
> * open IndexReader. Now the field is still present (not null) and is marked as binary, but the data is not there - Field.getBinaryLength() returns 0.
--
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