[
https://issues.apache.org/jira/browse/SOLR-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038669#comment-14038669
]
Robert Muir commented on SOLR-6178:
-----------------------------------
Its last minute because it can be potentially controversial. Deprecating the
lucene suggester has no impact to solr users. Putting a big warning in the
default configuration is a different story.
I didnt revert anything, your commit just didn't make it in time for the
release candidate. I dont want such controversy: I care about keeping things
stable and bad bugs. I can EASILY see such a warning turning into "we should
change the solr default" and spinning totally out of control and somehow
breaking the example.
I waited extra time for SOLR-6182 because it looked like a really bad bug. And
if a similar bug like that pops up I won't even have a second thought about
respinning for it. But by no means is this a blocker.
> Deprecate Jaspell suggester
> ---------------------------
>
> Key: SOLR-6178
> URL: https://issues.apache.org/jira/browse/SOLR-6178
> Project: Solr
> Issue Type: Improvement
> Components: spellchecker
> Reporter: Michael McCandless
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-6178.patch
>
>
> Right now Solr defaults to Jaspell, but we've deprecated it in LUCENE-5775
> ... and in trunk I'd like to remove it. But first we need to fix Solr to not
> default to it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
