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
It impacts UI search bar of OpenMetadata released version 1.0.0
It reproduces while searching on keywords with "-" symbol. The system trim only first part of the request which cause significally more results of search. Example : when i try to search text "CR-11662" the system trims "-11662" and output all results which start from "CR"
Expected behavior
I expect that system filters values on my exact input and not to return similar values (eg. on the screenshot wrong value CR-13794)
Version:
OS: windows 10
Python version: NA
OpenMetadata version: 1.0.0
OpenMetadata Ingestion package version: NA
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
kirillbartosh
changed the title
Search engine for some cases doesn't work correctly
Search engine doesn't work correctly for some cases
May 12, 2023
The problem here is not in the yellow highlighter of the results. But in the relevancy of the results. As you can see there are no matches on the first page with my key word "CR-11662" and there is 18 pages which i should review to distinct all matches which I need.
It impacts UI search bar of OpenMetadata released version 1.0.0
It reproduces while searching on keywords with "-" symbol. The system trim only first part of the request which cause significally more results of search. Example : when i try to search text "CR-11662" the system trims "-11662" and output all results which start from "CR"
Expected behavior
I expect that system filters values on my exact input and not to return similar values (eg. on the screenshot wrong value CR-13794)
Version:
Additional context

Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: