Lucene - Core
  1. Lucene - Core
  2. LUCENE-2867

Change contrib QP API that uses CharSequence as string identifier

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 3.0.3
    • Fix Version/s: 3.0.4
    • Component/s: modules/other
    • Labels:
      None
    • Lucene Fields:
      New, Patch Available

      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

          Activity

          Mark Thomas made changes -
          Workflow Default workflow, editable Closed status [ 12564190 ] jira [ 12583974 ]
          Mark Thomas made changes -
          Workflow jira [ 12542411 ] Default workflow, editable Closed status [ 12564190 ]
          Adriano Crestani made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Assignee Adriano Crestani [ adriano_crestani ]
          Resolution Fixed [ 1 ]
          Adriano Crestani made changes -
          Adriano Crestani made changes -
          Field Original Value New Value
          Link This issue is related to LUCENE-2855 [ LUCENE-2855 ]
          Adriano Crestani created 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