[LUCENE-2855] Contrib queryparser should not use CharSequence as Map key

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.3
• Fix Version/s: 3.0.4
• Component/s: modules/other
• Lucene Fields: New
• Assignee: Adriano Crestani
• Reporter: Adriano Crestani
• Created: 08/Jan/11 06:38
• Updated: 28/Aug/22 12:39
• Resolved: 11/Jan/11 02:44

Description

Today, contrib query parser uses Map<CharSequence,...> in many different places, which may lead to problems, since CharSequence interface does not enforce the implementation of hashcode and equals methods. Today, it's causing a problem with QueryTreeBuilder.setBuilder(CharSequence,QueryBuilder) method, that does not works as expected.

Issue Links

• relates to: LUCENE-2867 Change contrib QP API that uses CharSequence as string identifier