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 Busch (JIRA)" <ji...@apache.org> on 2007/11/29 05:43:43 UTC
[jira] Resolved: (LUCENE-1071) SegmentMerger doesn't set payload
bit in new optimized code
[ https://issues.apache.org/jira/browse/LUCENE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Busch resolved LUCENE-1071.
-----------------------------------
Resolution: Fixed
Committed.
> SegmentMerger doesn't set payload bit in new optimized code
> -----------------------------------------------------------
>
> Key: LUCENE-1071
> URL: https://issues.apache.org/jira/browse/LUCENE-1071
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Michael Busch
> Assignee: Michael Busch
> Fix For: 2.3
>
> Attachments: lucene-1071.patch
>
>
> In the new optimized code in SegmentMerger the payload bit is not set correctly
> in the merged segment. This means that we loose all payloads during a merge!
> The Payloads unit test doesn't catch this. Now that we have the new
> DocumentsWriter we buffer much more docs by default then before. This means
> that the test cases can't assume anymore that the DocsWriter flushes after 10
> docs by default. TestPayloads however falsely assumed this, which means that no
> merges happen anymore in TestPayloads. We should check whether there are
> other testcases that rely on this.
> The fixes for TestPayloads and SegmentMerger are very simple, I'll attach a patch
> soon.
--
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