You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Aadarsh Jajodia (JIRA)" <ji...@apache.org> on 2019/07/15 21:47:00 UTC
[jira] [Updated] (ATLAS-3336) Propagating Dynamic Attribute changes
[ https://issues.apache.org/jira/browse/ATLAS-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aadarsh Jajodia updated ATLAS-3336:
-----------------------------------
Description:
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
was:
attr1
attr2 - \{attr1}_name
attr3 : \{attr2}_value
Here attr2 and attr3 are dynamic attributes
The order in which these should be computed is that first attr2 and then attr3.
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
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)