-
Notifications
You must be signed in to change notification settings - Fork 186
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.
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
The search with (*) does not return all the expected results. #5750
Comments
These results are related to the searchable fields. In the OpenSearch documentation https://opensearch.org/docs/2.6/api-reference/index-apis/create-index/ there is a option called
So every time we search without a field, your search looks in more fields than the ones displayed by the Discover in the events section. That explains why you can see different results, or why sometimes you've got results that you don't know why they match. If you expand the event details, you will see the matched field and value. |
Wildcards can be used as prefix and suffix without problems. However, in the case of keyword mappings, only exact (case-sensitive) results are allowed, so wildcards have no effect on these mappings. Sources: |
Description
The goal of this test is search works without specifying a field and using (*)
It shows results but not all that should. I identified 2 specific cases.
I consider that by default, all results should be displayed, and the option not to filter administrator events should be disabled.
If we enable the option, the events should not appear .
Note: Found on Demo environment 4.5.0 in testing E2E.
Steps to reproduce
Case 1: When start with (*)
env-1
is selected.Events
view.v4
*v4
Case 2: When finish with (*)
env-1
is selected.Events
view.MASQUERADE
*MASQU*
Expected Result
Actual Result
Case 1: When start with (*)
Shows results that have contents with the word selected
Doesn't show events that have titles with the word selected as showing the first list.
Case 2: When finish with (*)
The text was updated successfully, but these errors were encountered: