atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-597) Handle Cluster renaming
Date Thu, 25 Aug 2016 06:38:20 GMT

     [ 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 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

  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 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


> 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 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)

Mime
View raw message