[
https://issues.apache.org/jira/browse/ATLAS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-597:
-----------------------------------
Description:
Cluster name could easily be changed by users which is used in qualified names
to dedup entities. For eg: hive_table has a qualifiedName
<dbName.tableName@clusterName> . Hence all entities will be recreated if they
are renamed 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
was:
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 renamed 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
> 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 has a qualifiedName
> <dbName.tableName@clusterName> . Hence all entities will be recreated if they
> are renamed 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)
