[
https://issues.apache.org/jira/browse/LUCENE-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041234#comment-13041234
]
Shai Erera commented on LUCENE-3146:
------------------------------------
bq. maybe, we allow the case you described (and it means all norms will now be
omitted for this field)
Though I don't like the idea of someone mistakenly adding a field w/
omitNorms=true, and suddenly all norms disappear, I think we must allow that
scenario in order to apps to be able to disable all norms for a field.
Basically, I hope that apps don't do crazy things and are consistent :). I'll
open a separate issue to track that.
> 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]
