You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What we're after:
We are making several changes to the way Elasticsearch will handle queries. This will hopefully help with several issues:
Removal of reserve/stop words from search results
Removal of stemming from search results
Exact string matching
So far, in the development environment, we have re-indexed to use the standard analyzer. Important note: This has only been done for current MURs, since re-indexing archived MURs is very resource intensive. We hope to get cursory feedback about current MURs first before we apply the re-index for archived MURs.
In addition, we would like to switch to using the simple_query_string which provides a simpler query syntax, lenient on invalid syntax, and simplifies the query syntax.
**Blocked by #6360
Summary
What we're after:
We are making several changes to the way Elasticsearch will handle queries. This will hopefully help with several issues:
So far, in the development environment, we have re-indexed to use the
standard
analyzer. Important note: This has only been done for current MURs, since re-indexing archived MURs is very resource intensive. We hope to get cursory feedback about current MURs first before we apply the re-index for archived MURs.In addition, we would like to switch to using the
simple_query_string
which provides a simpler query syntax, lenient on invalid syntax, and simplifies the query syntax.Related issues
Usability testing steps
Tech steps or considerations
Completion criteria
The text was updated successfully, but these errors were encountered: