[
https://issues.apache.org/jira/browse/ATLAS-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Merryle Wang updated ATLAS-3336:
--------------------------------
Description:
Changes in dynAttributes should be propagated down to relevant entities.
table - \{db.name}..
column - \{table.db.name}.\{table.name}
If the corresponding db's name is changed, then the table's qualifiedName as
well as the column's qualifiedName must be updated as well.
was:
attr1
attr2 - \{attr1}_name
attr3 : \{attr2}_value
Here attr2 and attr3 are dynamic attributes
The order in which these should be computed is
# attr2
# attr3
The reason is attr3 is dependent on attr2
The same propagation logic should hold when we change a database name
table - \{db.name}..
column - \{table.db.name}.\{table.name}
Here table's qualifiedName should be updated first and then the column's name
> Propagating Dynamic Attribute changes
> -------------------------------------
>
> Key: ATLAS-3336
> URL: https://issues.apache.org/jira/browse/ATLAS-3336
> Project: Atlas
> Issue Type: Bug
> Reporter: Aadarsh Jajodia
> Assignee: Merryle Wang
> Priority: Major
>
>
> Changes in dynAttributes should be propagated down to relevant entities.
> table - \{db.name}..
> column - \{table.db.name}.\{table.name}
>
> If the corresponding db's name is changed, then the table's qualifiedName as
> well as the column's qualifiedName must be updated as well.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
