[LUCENE-3796] Disallow setBoost() on StringField, throw exception if boosts are set if norms are omitted

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 3.6, 4.0-ALPHA
• Lucene Fields: New
• Assignee: Robert Muir
• Reporter: Robert Muir
• Created: 17/Feb/12 06:50
• Updated: 28/Aug/22 13:08
• Resolved: 18/Feb/12 15:49

Description

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)