You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2015/03/23 09:13:11 UTC

[jira] [Commented] (LUCENE-6367) Can PrefixQuery subclass AutomatonQuery?

    [ https://issues.apache.org/jira/browse/LUCENE-6367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375556#comment-14375556 ] 

Robert Muir commented on LUCENE-6367:
-------------------------------------

i think the boolean is fine. For the other subclasses, they are taking "patterns" and inspecting characters for that reason, so thats different.

> Can PrefixQuery subclass AutomatonQuery?
> ----------------------------------------
>
>                 Key: LUCENE-6367
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6367
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: Trunk, 5.1
>
>         Attachments: LUCENE-6367.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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