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

CompiledAutomaton performance for determining common suffix



    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.1
    • Fix Version/s: None
    • Component/s: core/FSTs
    • Labels:
    • Lucene Fields:


      We're using the automaton package as part of Elasticsearch for doing regexp queries. Our business requires us to process rather complex regular expressions, for example (we have more complex examples, but this one illustrates the problem):


      With a large enough value of maxDeterminizedStates, this works. The problem we're having is that the conversion of this regular expression to a CompiledAutomaton takes very long. Almost all of the time goes into determining the common suffix for the Automaton (which is "d" in this example) - calculated with a call to Operations.getCommonSuffixBytesRef.

      This suffix is only used as an optimization. Skipping the calculation of this suffix allows us to process these kinds of queries.

      • Would it be possible to introduce a way to skip the calculation of this common suffix (ideally something we control from within our query to Elasticsearch)?
      • Or would it be possible to take a look at this getCommonSuffixBytesRef operation, to see if it can be optimized? Most of the time goes to determinizing the reversed automaton - maybe this can be avoided somehow?

      Reaction from Mike McCandless on the mailing list:
      This is just an optimization; maybe we should expose an option to disable it?
      Or maybe we can find the common suffix on an NFA instead, to avoid determinization?




            • Assignee:
              ThomasPoppe Thomas Poppe
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: