Tim Smith created LUCENE-4557:
---------------------------------
Summary: Indexed Offsets Can Be Lost During Merge
Key: LUCENE-4557
URL: https://issues.apache.org/jira/browse/LUCENE-4557
Project: Lucene - Core
Issue Type: Bug
Affects Versions: 4.0
Reporter: Tim Smith
Attachments: OffsetsTest.java
Primary Use case:
Start with pre-4.0 index (no indexed offsets available)
Start indexing new documents with indexed offsets
(IndexOptions.DOCS_AND_FREQS_AND_POSITIONS_AND_OFFSETS, previously was
IndexOptions.DOCS_AND_FREQS_AND_POSITIONS)
merge/optimize index
newly indexed documents will now no longer have offsets available
In general, it is impossible to ever change a field to have offsets indexed
when starting with an existing index as a merge will cause offsets to be
removed from the index.
Desirable behavior would be for new documents to have offsets indexed properly,
and old documents would have offset of "0, 0" for all positions after merging
with a segment that contains offsets
Current behavior can be very dangerous.
for example:
* Start indexing documents with indexed offsets
* change config to not index offsets by accident
* index 1 document
* revert config back
* offsets will start disappearing from documents as segments are merged
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
