[LUCENE-2867] Change contrib QP API that uses CharSequence as string identifier

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.3
• Fix Version/s: 3.0.4
• Component/s: modules/other
• Lucene Fields: New, Patch Available
• Assignee: Adriano Crestani
• Reporter: Adriano Crestani
• Created: 13/Jan/11 16:32
• Updated: 28/Aug/22 12:39
• Resolved: 16/Jan/11 02:35

Description

There are some API methods on contrib queryparser that expects CharSequence as identifier. This is wrong, since it may lead to incorrect or mislead behavior, as shown on LUCENE-2855. To avoid this problem, these APIs will be changed and enforce the use of String instead of CharSequence on version 4. This patch already deprecate the old API methods and add new substitute methods that uses only String.

Issue Links

• is related to: LUCENE-2855 Contrib queryparser should not use CharSequence as Map key