[
https://issues.apache.org/jira/browse/LUCENE-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041213#comment-13041213
]
Michael McCandless commented on LUCENE-3146:
--------------------------------------------
I agree we should first fix IR.setNorm to throw exc today... I like
IllegalStateEx.
And then open a separate issue; I agree add/updateDocument should fail. Or,
maybe, we allow the case you described (and it means all norms will now be
omitted for this field), but the reverse case (you have been omitting norms up
until now and suddenly you try to add a doc not omitting norms) we throw exc?
> 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]