You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Jan Høydahl (Jira)" <ji...@apache.org> on 2022/02/10 11:35:00 UTC

[jira] [Commented] (SOLR-13230) Move JaSpell code into Solr and deprecate the factory

    [ https://issues.apache.org/jira/browse/SOLR-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490143#comment-17490143 ] 

Jan Høydahl commented on SOLR-13230:
------------------------------------

This issue is tagged for 9.0. Is there anything that needs to be done here? As I can read, JaSpell is still in Lucene so nothing will break here?

> Move JaSpell code into Solr and deprecate the factory
> -----------------------------------------------------
>
>                 Key: SOLR-13230
>                 URL: https://issues.apache.org/jira/browse/SOLR-13230
>             Project: Solr
>          Issue Type: Task
>          Components: spellchecker
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Major
>             Fix For: 8.2, 9.0
>
>         Attachments: SOLR-13230.patch
>
>
> The JaSpell suggester is deprecated, and will be removed from the lucene codebase.  However, it's currently the default implementation for suggesters in Solr, and its Solr factory is *not* deprecated, so users won't have been receiving any warnings.
> I suggest that we deprecate the factory, and move the relevant bits of code from lucene into Solr, as a first step.  In a follow-up we should change the default implementation (possibly by just removing the default, and forcing people to choose a factory?) and remove the deprecated code form Solr as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org