You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Michael McCandless (Jira)" <ji...@apache.org> on 2021/06/18 16:41:00 UTC
[jira] [Commented] (LUCENE-9098) Report problematic term value when
fuzzy query is too complex
[ https://issues.apache.org/jira/browse/LUCENE-9098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365601#comment-17365601 ]
Michael McCandless commented on LUCENE-9098:
--------------------------------------------
Hmm while backporting the fix for LUCENE-9981, I noticed that at least some parts of this change were not backported, e.g. {{TestFuzzyQuery.testErrorMessage}} – I'll backport this one test during my backporting efforts, but [~mdrob] maybe you could double check that the rest of this fix was indeed backported? Did we miss anything else maybe?
> Report problematic term value when fuzzy query is too complex
> -------------------------------------------------------------
>
> Key: LUCENE-9098
> URL: https://issues.apache.org/jira/browse/LUCENE-9098
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Reporter: Mike Drob
> Assignee: Mike Drob
> Priority: Minor
> Fix For: main (9.0), 8.5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This is the lucene compliment to SOLR-13190, when fuzzy query gets a term that expands to too many states, we throw an exception but don't provide insight on the problematic term. We should improve the error reporting.
--
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