[ATLAS-3391] Issues after renaming of Glossary and/or Terms

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Assignee: Saqeeb Shaikh
• Reporter: Rahul Kurup
• Created: 27/Aug/19 06:58
• Updated: 24/Jan/24 08:50

Description

 This issue comprises of 2 problem areas.

1st problem area (How to reproduce):

1. Create a glossary 'G', and within it a term 'T'. Then, rename the Glossary to 'G_R'.
2.  Fire the Attribute Value API with the following parameters:http://localhost:21000/api/atlas/v2/search/attribute?attrValuePrefix=T&typeName=AtlasGlossaryTerm&limit=10&offset=0
3. The above API returns 'T@G' instead of 'T@G_R'

 

2nd problem area:

1.  Basic search will always trigger search for the previous 'T@G'  parameter. Due to the 1st problem, it is not possible to search by 'T@G_R' in the "Search By Term" field in Basic Search.
2. If a search is triggered using the API instead through curl or postman, then we get an error response as follows:

 

API Url : 
http://localhost:21000/api/atlas/v2/search/basic
Body:
{
 "excludeDeletedEntities":true,
 "includeSubClassifications":true,
 "includeSubTypes":true,
 "includeClassificationAttributes":true,
 "entityFilters":null,
 "tagFilters":null,
 "attributes":null,
 "limit":25,
 "offset":0,
 "typeName":null,
 "classification":null,
 "termName":"T@G_R"
}
 Response:
{
"errorCode":"ATLAS-400-00-06E",
"errorMessage":"T@G_R: Unknown/invalid glossary term"
}

 

 

Ideally, an error notification should be triggered when user searches for "T@G", not "T@G_R", as it has been renamed.

[ADDED NOTE]

The renamed glossaries and terms do not get updated even on stopping and restarting Atlas service.

Issue Links

• links to: Review request