lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LUCENE-2672) speed up automaton seeking in nextString
Date Mon, 27 Sep 2010 17:19:32 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Muir resolved LUCENE-2672.
---------------------------------

      Assignee: Robert Muir
    Resolution: Fixed

Committed revision 1001781.

I left out the terms dict cache clone() thing, its something we can revisit if we ever need
to... 
not sure its a big deal especially if we can use it smarter (such as LUCENE-2674)


> speed up automaton seeking in nextString
> ----------------------------------------
>
>                 Key: LUCENE-2672
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2672
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: LUCENE-2672.patch, LUCENE-2672.patch, LUCENE-2672.patch
>
>
> While testing, i found there are some queries (e.g. wildcard ?????????) that do quite
a lot of backtracking.
> nextString doesn't handle this particularly well, when it walks the DFA, if it hits a
dead-end and needs to backtrack, it increments the bytes, and starts over completely.
> alternatively it could save the path information in an int[], and backtrack() could return
a position to restart from, instead of just a boolean.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message