New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Search] Enhance Lucene word boundaries / stopwords handling #350

Open

plutonik-a opened this issue Nov 11, 2019 · 0 comments

Labels

Search

Contributor

plutonik-a commented Nov 11, 2019 •

edited

Loading

Try out different Lucene analyzers and/or add advanced search form controls to see what combination can produce our expected results

For more on stopwords, see:

Lucene's default list of stopwords: https://stackoverflow.com/questions/17527741/what-is-the-default-list-of-stopwords-used-in-lucenes-stopfilter
Pros/cons of stopwords: https://www.elastic.co/guide/en/elasticsearch/guide/current/stopwords.html (linked from the stackoverflow page above)
Example of how our use of default stopwords leads to unexpected/unwanted search hits, see https://twitter.com/awmarrs/status/893213357251203077

Originally posted by @joewiz in

plutonik-a mentioned this issue

Assemble list of quirks with our full text search engine (esp. punctuation) #255

Open

plutonik-a added the Search label

joewiz mentioned this issue

Drop stopwords from Lucene HistoryAtState/frus#270

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment