[
https://issues.apache.org/jira/browse/LUCENE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782409#action_12782409
]
Michael McCandless edited comment on LUCENE-2090 at 11/25/09 1:06 PM:
----------------------------------------------------------------------
BTW, we've discussed someday having a codec whose terms dict (or maybe just
terms index) is represented as an FST, at which point AutomatonTermsEnum would
be an intersection + walk of two FSTs. Because suffix's are also shared in the
FST, you could more easily (more efficiently) handle \*XXX cases as well (it'd
just be symmetic with the XXX\* cases).
was (Author: mikemccand):
BTW, we've discussed someday having a codec whose terms dict (or maybe just
terms index) is represented as an FST, at which point AutomatonTermsEnum would
be an intersection + walk of two FSTs. Because suffix's are also shared in the
FST, you could more easily (more efficiently) handle *XXX cases as well (it'd
just be symmetic with the XXX* cases).
> convert automaton to char[] based processing and TermRef / TermsEnum api
> ------------------------------------------------------------------------
>
> Key: LUCENE-2090
> URL: https://issues.apache.org/jira/browse/LUCENE-2090
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Robert Muir
> Priority: Minor
> Fix For: 3.1
>
> Attachments: LUCENE-2090_TermRef_flex.patch,
> LUCENE-2090_TermRef_flex2.patch
>
>
> The automaton processing is currently done with String, mostly because
> TermEnum is based on String.
> it is easy to change the processing to work with char[], since behind the
> scenes this is used anyway.
> in general I think we should make sure char[] based processing is exposed in
> the automaton pkg anyway, for things like pattern-based tokenizers and such.
--
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: [email protected]
For additional commands, e-mail: [email protected]
