You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/18 16:50:59 UTC
[jira] [Resolved] (LUCENE-3796) Disallow setBoost() on StringField,
throw exception if boosts are set if norms are omitted
[ https://issues.apache.org/jira/browse/LUCENE-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved LUCENE-3796.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.6
Assignee: Robert Muir
> Disallow setBoost() on StringField, throw exception if boosts are set if norms are omitted
> ------------------------------------------------------------------------------------------
>
> Key: LUCENE-3796
> URL: https://issues.apache.org/jira/browse/LUCENE-3796
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Robert Muir
> Priority: Blocker
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3796.patch, LUCENE-3796.patch
>
>
> Occasionally users are confused why index-time boosts are not applied to their norms-omitted fields.
> This is because we silently discard the boost: there is no reason for this!
> The most absurd part: in 4.0 you can make a StringField and call setBoost and nothing complains... (more reasons to remove StringField totally in my opinion)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org