You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2018/04/30 21:08:00 UTC
[jira] [Created] (ATLAS-2628) Restrict update to qualifiedName of
AtlasGlossary
Apoorv Naik created ATLAS-2628:
----------------------------------
Summary: Restrict update to qualifiedName of AtlasGlossary
Key: ATLAS-2628
URL: https://issues.apache.org/jira/browse/ATLAS-2628
Project: Atlas
Issue Type: Bug
Reporter: Apoorv Naik
Assignee: Apoorv Naik
h2. Description
1. Create a glossary "org" with following information :
{code:java}
displayName: "org",
shortDescription: "org",
longDescription: "organisation"
{code}
GUID <guid1> and qualifiedName "org" is assigned to the glossary org.
2. Create a glossary "orgn" with following information:
{code:java}
displayName: "orgn",
shortDescription: "orgn",
longDescription: "organisation"
{code}
GUID <guid2> and qualifiedName "orgn" is assigned to the glossary.
Now update the "orgn" and modify its qualifiedName and other attributes as :
{code:java}
{
"guid": "<guid2>",
"displayName": "org",
"shortDescription": "org",
"longDescription": "organisation",
"qualifiedName": "org"
}
{code}
Hence now 2 glossaries with same displayName , same qualifiedName are present.
The above PUT request should fail with exception message "Glossary with same qualifiedName org exists".
During duplicate glossary creation , it is thrown. While update also it should be thrown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)