[jira] [Commented] (ATLAS-3391) Issues after renaming of Glossary and/or Terms

["Aileen Toleikis (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810274#comment-17810274 ] 

Aileen Toleikis commented on ATLAS-3391:
----------------------------------------

Any updates on this issue?
We have a customer using Atlas in production facing the same issue.
It would be great if someone could rebase the patch and merge it.

> Issues after renaming of Glossary and/or Terms
> ----------------------------------------------
>
>                 Key: ATLAS-3391
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3391
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Rahul Kurup
>            Assignee: Saqeeb Shaikh
>            Priority: Major
>         Attachments: 0001-ATLAS-3391-Qualified-name-of-term-not-being-updated-.patch
>
>
>  This issue comprises of 2 problem areas.
> 1st problem area (How to reproduce):
>  # Create a glossary *'G'*, and within it a term *'T'*. Then, rename the Glossary to *'G_R'*.
>  #  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]
>  # The above API returns *'T@G'* instead of *'T@G_R'*
>  
> 2nd problem area:
>  #  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.
>  # If a search is triggered using the API instead through curl or postman, then we get an error response as follows:
>  
> {code:java}
> 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"
> }
> {code}
>  
>  
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)