[
https://issues.apache.org/jira/browse/ATLAS-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharmadha Sainath updated ATLAS-1643:
-------------------------------------
Description:
1. Created hbase_table "employee" in UI .
2. Created hbase_column_family "personalData" in UI with its hbase_table as
"employee"
(Now association is correct for both hbase_column_family and hbase_table)
3.Created another hbase_table "employee_abc" in UI.
4.Edited personalData and modified hbase_table to be "employee_abc".
Now personalData's hbase_table is "employee_abc" and "employee_abc" has
personalData as one of its column_families . *But hbase_table employee still
has personalData as one of its column families. The broken association still
prevails* . And unable to edit hbase_table employee and remove "personalData".
was:
1. Created hbase_table "employee" in UI .
2. Created hbase_column_family "personalData" in UI with its hbase_table as
"employee"
(Now association was correct for both hbase_column_family and hbase_table)
3.Created another hbase_table "employee_abc" in UI.
4.Edited personalData and modified hbase_table to be "employee_abc".
Now personalData's hbase_table is "employee_abc" and "employee_abc" has
personalData as one of its column_families . *But hbase_table employee still
has personalData as one of its column families. The broken association still
prevails*
> Edit Entity in UI : simple entity s1 association to compound entity c1 not
> broken after s1 is associated to some other compound entity c2.
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-1643
> URL: https://issues.apache.org/jira/browse/ATLAS-1643
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 0.8-incubating
> Reporter: Sharmadha Sainath
> Priority: Critical
>
> 1. Created hbase_table "employee" in UI .
> 2. Created hbase_column_family "personalData" in UI with its hbase_table as
> "employee"
> (Now association is correct for both hbase_column_family and hbase_table)
> 3.Created another hbase_table "employee_abc" in UI.
> 4.Edited personalData and modified hbase_table to be "employee_abc".
> Now personalData's hbase_table is "employee_abc" and "employee_abc" has
> personalData as one of its column_families . *But hbase_table employee still
> has personalData as one of its column families. The broken association still
> prevails* . And unable to edit hbase_table employee and remove "personalData".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
