Skip to content
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

Glossary search problem #9724

Closed
AnnaShevchuk23 opened this issue Jan 13, 2023 · 1 comment
Closed

Glossary search problem #9724

AnnaShevchuk23 opened this issue Jan 13, 2023 · 1 comment
Assignees

Comments

@AnnaShevchuk23
Copy link

AnnaShevchuk23 commented Jan 13, 2023

Affected module
Yes, it impact the UI.

Describe the bug
Found the following problem with the search in the glossary, which appeared in version 13.1, there was no such problem before. Do I understand correctly that now the search has become case sensitive? For example, 3 terms have been added to the glossary that have the word restructuring in their titles. 2 of them are written in uppercase and 1 in lowercase. When you enter the Rest value in the search, the search finds two values: Restructuring flg and Restruct, as well as some additional values that are in the Credit Agreement category along with Restruct. When you enter the rest value in the search, the search finds only 1 Flag restruct value. Also, when searching in the glossary, OMD gives the following errors: Error while fetching glossary term! and Error while fetching glossary! Previously, case-insensitive search returned all 3 required results without padding.

To Reproduce
If you enter the words "Rest" and "rest" in the glossary search in the sandbox, you can clearly see the problem
Search result in upper case "Rest":

12

Search result in lower case "rest":

21

Expected behavior
There are 3 terms in the Glossary that deal with restructuring, I expected that regardless of case, when asked in a search, the search would return all 3 results

Version:
-OS: [e.g. Windows 10]
-OpenMetadata version: [e.g. 13.1]

Additional context
I recorded a video of the problem in your sandbox, where this problem is clearly visible.
2023-01-11-14-25-40

I would also like to add that reindexing the elastic search did not help.

@harshach
Copy link
Collaborator

This is fixed in latest release

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

No branches or pull requests

4 participants