You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/02/24 11:10:00 UTC
[jira] [Commented] (LUCENE-9212) Intervals.multiterm() should take
a CompiledAutomaton
[ https://issues.apache.org/jira/browse/LUCENE-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043422#comment-17043422 ]
ASF subversion and git services commented on LUCENE-9212:
---------------------------------------------------------
Commit ffb7cafe9351cd6cd5181bc06dd053d586f6d63f in lucene-solr's branch refs/heads/master from Alan Woodward
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ffb7caf ]
LUCENE-9212: Intervals.multiterm() should take CompiledAutomaton
> Intervals.multiterm() should take a CompiledAutomaton
> -----------------------------------------------------
>
> Key: LUCENE-9212
> URL: https://issues.apache.org/jira/browse/LUCENE-9212
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> LUCENE-9028 added a `multiterm` factory method for intervals that accepts an arbitrary Automaton, and converts it internally into a CompiledAutomaton. This isn't necessarily correct behaviour, however, because Automatons can be defined in both binary and unicode space, and there's no way of telling which it is when it comes to compiling them. In particular, for automatons produced by FuzzyTermsEnum, we need to convert them to unicode before compilation.
> The `multiterm` factory should just take `CompiledAutomaton` directly, and we should deprecate the methods that take `Automaton` and remove in master.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org