Lucene - Core
  1. Lucene - Core
  2. LUCENE-2855

Contrib queryparser should not use CharSequence as Map key

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.3
    • Fix Version/s: 3.0.4
    • Component/s: modules/other
    • Labels:
      None
    • Lucene Fields:
      New

      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

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Adriano Crestani
              Reporter:
              Adriano Crestani
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development