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.

Sign up for GitHub

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

Jump to bottom

Terms don't show under Glossary with period character in name #13850

Closed
SaucySandel opened this issue Nov 5, 2023 · 0 comments · Fixed by #14206
Closed

Terms don't show under Glossary with period character in name #13850

SaucySandel opened this issue Nov 5, 2023 · 0 comments · Fixed by #14206
Assignees
@harshach

Comments

@SaucySandel
Copy link

Affected module
Does it impact the UI, backend or Ingestion Framework?
UI - Glossary

Describe the bug
A clear and concise description of what the bug is.
Terms don't show with period character in Glossary title. e.g. "Bug.Test"

To Reproduce
Create a new Glossary with a period in the Glossary title, next add a term to that glossary. The Glossary term will show in the explore tab under glossary but not under the Glossary that is was added.

Screenshots or steps to reproduce
image
image
image
image

Screen.Recording.2023-11-06.at.2.13.15.am.mov

Expected behavior
A clear and concise description of what you expected to happen.
Glossary terms should display under their related glossary name

Version:
v1.2.0 helm chart 1.2.1 running on minikube. Also tested on bare metal install

Additional context
Add any other context about the problem here.
@harshach harshach self-assigned this Nov 5, 2023
@harshach harshach moved this to Backend - Bugs & Minor Features in Release 1.2.3 Nov 22, 2023
harshach added a commit that referenced this issue Dec 2, 2023
@harshach
Fix #13850: Glossary FQN should be used
d97dc76
@harshach harshach mentioned this issue Dec 2, 2023
Merged
9 tasks
harshach added a commit that referenced this issue Dec 2, 2023
@harshach
Fix #13850: Glossary FQN should be used (#14206)
c9f3e3b 
* Fix #13850: Glossary FQN should be used

* Minor: Initializing Glossary doesn't skip if it exists already
@harshach harshach moved this from Backend - Bugs & Minor Features to Done in Release 1.2.3 Dec 2, 2023
harshach added a commit that referenced this issue Dec 5, 2023
@harshach
Fix #13850: Glossary FQN should be used (#14206)
9815baa 
* Fix #13850: Glossary FQN should be used

* Minor: Initializing Glossary doesn't skip if it exists already
MrVinegar pushed a commit to MrVinegar/OpenMetadata that referenced this issue Dec 15, 2023
@harshach
Fix open-metadata#13850: Glossary FQN should be used (open-metadata#1…
2558d15 
…4206)

* Fix open-metadata#13850: Glossary FQN should be used

* Minor: Initializing Glossary doesn't skip if it exists already
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@harshach harshach

Labels
None yet
Projects
No open projects
Release 1.2.3
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #13850: Glossary FQN should be used open-metadata/OpenMetadata
2 participants
@harshach @SaucySandel