Unexpected and missing search results with Advanced search
See also the question in the forum which I'll CC here:
For our on-prem installation, we enabled the elastic search integration because we hoped search results would be better, but apparently, they aren’t.
Amongst other types of content, we collect Java stack traces in issues. These contain many qualified names of the shape “a.b.C” (words delimited by a dot, e.g., “java.lang.IllegalStateException”).
I had expected to find issues with such content by querying for a segment of the qualified name, e.g., “IllegalStateException” but no results with such content was found. Only the full name in the query would reveal that content “java.lang.IllegalStateException”.
Since I cannot believe this is intentional behavior, I wanted to ask if my expectation is wrong.
Release notes
We have changed the Elasticsearch analyzer for GitLab Issues to support searching code-like issue descriptions. This will make descriptions that contain things like code snippets and logs more likely to be found. Previously, these descriptions may not have been found in searches.