[
https://issues.apache.org/jira/browse/ATLAS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299530#comment-15299530
]
Suma Shivaprasad edited comment on ATLAS-597 at 8/25/16 6:36 AM:
-----------------------------------------------------------------
The cluster entity will have the following properties
name
description
list<string> aliases - This will hold older cluster names or previous aliases
This also means that the hooks will have to pass the qualifiedName in entity
creates/updates such as "dbName.tableName@clusterId" instead of the
"dbName.tableName@clusterName"
was (Author: suma.shivaprasad):
The cluster entity will have the following properties
name
description
list<string> aliases - This will hold other cluster names
The plan is to keep an inmemory copy and be able to do a lookup by any of the
cluster names i.e aliases and also by the primary /current name which is stored
in "name" attribute
> Handle Cluster renaming
> -----------------------
>
> Key: ATLAS-597
> URL: https://issues.apache.org/jira/browse/ATLAS-597
> Project: Atlas
> Issue Type: Sub-task
> Affects Versions: 0.7-incubating
> Reporter: Suma Shivaprasad
>
> Cluster name could easily be changed by users which is used in qualified
> names to dedup entities. For eg: hive_table as <dbName.tableName@clusterName>
> . Hence all entities will be recreated if they are created again unless a
> mass update on repository is done with new cluster name.
> Hence cluster should be represented by an id which is constant and tied to
> clusterName which could change
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
