[
https://issues.apache.org/jira/browse/LUCENE-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039614#comment-13039614
]
Michael McCandless commented on LUCENE-3146:
--------------------------------------------
Also, in trunk, we now store a separate global field infos file (.fnx), which
in theory could be used to catch this case when app attempts to use different
omitNorms for different docs. However, this only tracks field name -> number
mapping, not settings in the schema like omitNorms... if we added things like
omitNorms, omitTF to this, then we'd have more consistent behavior here, and
could fix this trap (if you uncomment the commit in the test case) where app
thinks it succeeded in setting a norm but in fact on future merging it did not
succeed.
> IndexReader.setNorms is no op if one of the field instances omits norms
> -----------------------------------------------------------------------
>
> Key: LUCENE-3146
> URL: https://issues.apache.org/jira/browse/LUCENE-3146
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/search
> Reporter: Shai Erera
> Fix For: 4.0
>
> Attachments: LUCENE-3146.patch
>
>
> If I add two documents to an index w/ same field, and one of them omit norms,
> then IndexReader.setNorms is no-op. I'll attach a patch w/ test case
--
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]
