[LUCENENET-526] Multifieldqueryparser now throws a KeyNotFoundException if all search fields do not have boosts set

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: Lucene.Net 3.0.3
• Component/s: Lucene.Net Core
• Assignee: Itamar Syn-Hershko
• Reporter: Chris Dondanville
• Created: 10/Oct/13 18:20
• Updated: 21/Feb/14 11:23
• Resolved: 21/Feb/14 11:23

Description

Using the Multifieldqueryparser overload that accepts a Dictionary<string, float> of boosts used to only require setting boosts for fields whose default boost needed to be changed. After upgrading from 2.9.2 to 3.0.3, MultiFieldQueryParser now throws a KeyNotFoundException unless I add entries for the remaining fields to the boost Dictionary.