[
https://issues.apache.org/jira/browse/LUCENE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781694#action_12781694
]
Robert Muir commented on LUCENE-2090:
-------------------------------------
Hi Mike, I think an easier win is to perhaps add endsWith() byte[] comparison
in TermRef.
(for now, I can use regular endsWith(), or run the machine backwards, or
something like that).
I can use this in "dumb mode", i.e. *N, where I know the first part of the
machine is a loop.
for whatever reason dumb mode checks "constant prefix" right now, which is
useless, it will always be 0 in dumb mode.
instead I should build "constant suffix" in dumb mode. this would be much more
useful for a quick comparison.
> 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
>
>
> 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]