[
https://issues.apache.org/jira/browse/LUCENE-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3012:
--------------------------------
Attachment: LUCENE-3012_3x.patch
Updated patch (against branch_3x for simplicity) that uses the LUCENE-3014
comparator API.
Because separate norms files are independent of the version that created the
segment (e.g. one can call setNorm with 3.6 for a 3.1 segment), I think its
really important that we fix this in 3.2 to write the header.
If there are no objections, I'd like to commit, and then regenerate the
tentative 3.2 indexes for trunk's TestBackwardsCompatibility.
There's no need to change the fileformats.html documentation, as what we are
doing now is actually inconsistent with it, thus the bug.
> if you use setNorm, lucene writes a headerless separate norms file
> ------------------------------------------------------------------
>
> Key: LUCENE-3012
> URL: https://issues.apache.org/jira/browse/LUCENE-3012
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 3.2
>
> Attachments: LUCENE-3012.patch, LUCENE-3012_3x.patch
>
>
> In this case SR.reWrite just writes the bytes with no header...
> we should write it always.
> we can detect in these cases (segment written <= 3.1) with a
> sketchy length == maxDoc check.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
