Fix #13850: Glossary FQN should be used (#14206)

* Fix #13850: Glossary FQN should be used

* Minor: Initializing Glossary doesn't skip if it exists already
This commit is contained in:
Sriharsha Chintalapani 2023-12-02 11:12:19 -08:00 committed by GitHub
parent f5327eb2e2
commit c9f3e3b4fe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -118,6 +118,7 @@ public class GlossaryTermResource extends EntityResource<GlossaryTerm, GlossaryT
for (LoadGlossary loadGlossary : loadGlossaries) {
Glossary glossary =
GlossaryResource.getGlossary(glossaryRepository, loadGlossary.getCreateGlossary(), ADMIN_USER_NAME);
glossary.setFullyQualifiedName(glossary.getName());
glossaryRepository.initializeEntity(glossary);
List<GlossaryTerm> termsToCreate = new ArrayList<>();
@ -201,7 +202,7 @@ public class GlossaryTermResource extends EntityResource<GlossaryTerm, GlossaryT
EntityReference glossary = null;
if (glossaryIdParam != null) {
glossary = repository.getGlossary(glossaryIdParam);
fqn = glossary.getName();
fqn = glossary.getFullyQualifiedName();
}
// Filter by glossary parent term