Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-6367

Can PrefixQuery subclass AutomatonQuery?

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1, 6.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Spinoff/blocker for LUCENE-5879.

      It seems like PrefixQuery should "simply" be an AutomatonQuery rather than specializing its own TermsEnum ... with maybe some performance improvements to ByteRunAutomaton.run to short-circuit once it's in a "sink state", AutomatonTermsEnum could be just as fast as PrefixTermsEnum.

      If we can do this it will make LUCENE-5879 simpler.

        Attachments

        1. LUCENE-6367.patch
          21 kB
          Michael McCandless
        2. LUCENE-6367.patch
          31 kB
          Michael McCandless

        Issue Links

          Activity

            People

            • Assignee:
              mikemccand Michael McCandless
              Reporter:
              mikemccand Michael McCandless

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment