[
https://issues.apache.org/jira/browse/LUCENE-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853002#action_12853002
]
Robert Muir commented on LUCENE-2265:
-------------------------------------
bq. Why can't you create UTF-8 Automaton from the get go?
Because high-level, users want automaton transitions to represent real
characters
(eg regular expressions, wildcards, etc) and do not much care about bytes!
So the utf-16 Automaton/RunAutomaton pair makes sense for the library...
But utf-32 is still easy to work with high-level (we just represent codepoint
intervals instead of codeunit),
and utf-8 is faster for working with lucene.
> improve automaton performance by running on byte[]
> --------------------------------------------------
>
> Key: LUCENE-2265
> URL: https://issues.apache.org/jira/browse/LUCENE-2265
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Affects Versions: Flex Branch
> Reporter: Robert Muir
> Priority: Minor
> Fix For: Flex Branch
>
> Attachments: LUCENE-2265.patch
>
>
> Currently, when enumerating terms, automaton must convert entire terms from
> flex's native utf-8 byte[] to char[] first, then step each char thru the
> state machine.
> we can make this more efficient, by allowing the state machine to run on
> byte[], so it can return true/false faster.
--
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]
