Best practice for setting custom stop word list non-globally #12940
Closed
pdhall99
started this conversation in
Help: Best practices
Replies: 1 comment
-
Ideally, you'd create a custom language subclass that uses a If that's not an option, you can simplify the above code by eliminating the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
#10942 gives a recommendation for setting a custom stop word list. We might want to have several pipelines in the same session, some of which have default stop words, some of which have custom. Is there a better way to do this than the following, resetting to the default after loading?
Beta Was this translation helpful? Give feedback.
All reactions