[
https://issues.apache.org/jira/browse/SOLR-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078296#comment-16078296
]
Erick Erickson commented on SOLR-10992:
---------------------------------------
I do see one issue here. First let me say I'm all for removing stopwords (+1,
just to see if it's only a plus sign in the leading position that seems to get
stripped lately). For that matter I'm also in favor of removing all the extra
languages etc and super-especially the things like elevate that break
startup.... OK, enough ranting.
I usually recommend to clients when they upgrade that they take the configs
from the new version and copy/paste their changes over from their old
configuration rather than just carry their old ones forward to a new version,
especially when they're moving to a new major version.
This is going to bite them a bit as it's likely they'll overlook something like
removing stopwords for the fields they use "as is", which many do (text_en
comes to mind).
That said bout the max I'd advocate is a comment in the configs or maybe the
upgrade notes in CHANGES.txt to the effect of "compare your schema definitions
carefully since stopwords have been removed". Well, something better than that
but you get the idea. I suppose it's one more incentive to re-index.
> the default for stopwords should be disabled
> --------------------------------------------
>
> Key: SOLR-10992
> URL: https://issues.apache.org/jira/browse/SOLR-10992
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Components: config-api
> Affects Versions: 6.6
> Environment: All
> Reporter: Rick Leir
> Priority: Minor
> Labels: beginner
>
> Suggest removing the stopword filter from the example configs. It is not a
> “best practice” or even a recommended practice.
> This was discussed in the user mailing list (link below).
> I chose the wrong component above, what should it have been?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
