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

          Adriano Crestani created issue -
          Adriano Crestani made changes -
          Field Original Value New Value
          Assignee Adriano Crestani [ adriano_crestani ]
          Adriano Crestani made changes -
          Adriano Crestani made changes -
          Adriano Crestani made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Adriano Crestani made changes -
          Link This issue relates to LUCENE-2867 [ LUCENE-2867 ]
          Mark Thomas made changes -
          Workflow jira [ 12541926 ] Default workflow, editable Closed status [ 12563837 ]
          Mark Thomas made changes -
          Workflow Default workflow, editable Closed status [ 12563837 ] jira [ 12585360 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development