[
https://issues.apache.org/jira/browse/LUCENE-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039611#comment-13039611
]
Michael McCandless commented on LUCENE-3146:
--------------------------------------------
I think this behavior, while spooky, is correct. LUCENE-2846 flipped the norms
merging behavior so that omitNorm now "spreads", in 4.0 (not 3.x).
But the javadoc in Field.NOT_ANALYZED_NO_NORMS needs to be fixed, on trunk.
I think, also, SegmentReader.doSetNorm should throw an exc if you attempt to
set norm on a field that does not have norms... it's bad that we silently
ignore that... makes the app think the call succeeded when in fact nothing
happened.
> 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]
