Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.9
    • Fix Version/s: 2.9
    • Component/s: modules/other
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      We should rename the new QueryParser so it's clearer that it's
      Lucene's default QueryParser, going forward, and not just a temporary
      "bridge" to a future new QueryParser.

      How about we rename oal.queryParser.original -->
      oal.queryParser.standard (can't use "default": it's a Java keyword)?
      Then, leave the OriginalQueryParserHelper under that package, but
      simply rename it to QueryParser?

      This way if we create other sub-packages in the future, eg
      ComplexPhraseQueryParser, they too can have a QueryParser class under
      them, to make it clear that's the "top" class you use to parse
      queries.

        Attachments

        1. LUCENE-1782.patch
          848 kB
          Michael McCandless
        2. LUCENE-1782.patch
          823 kB
          Michael McCandless

          Issue Links

            Activity

              People

              • Assignee:
                mikemccand Michael McCandless
                Reporter:
                mikemccand Michael McCandless
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: