You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "charles shen (JIRA)" <ji...@apache.org> on 2019/03/08 01:59:00 UTC
[jira] [Updated] (ATLAS-2992) Rdbms model
[ https://issues.apache.org/jira/browse/ATLAS-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
charles shen updated ATLAS-2992:
--------------------------------
Description:
There's ownedRef/inverseRef between "rdbms_instance.database, rdbms_db.instance" and "rdbms_db.tables, rdbms_table.db" and more. This caused some performance issue described below:
When creating a rdbms_db with referenced entity rdbms_intance, both rdbms_db and rdbms_instance will be created, but when creating another rdbms_db with the same rdbms_instance, the rdbms_instance will be treated as update though they are indeed the same. Looking into the rdbms model, rdbms_instance has attribute "databases" and rdbms_db has attribute "instance" constrained with inverseref to "databases" attribute to rdbms_instance. One more thins is the relationship between rdbms_db and rdbms_instance and etc... are already defined in relationship types.
So for first creation, rdbms_db will populate the "databases" attribute for rdbms_instance, for the second creation, altas will consider the rdbms_instance not equal since the "databases" attributes are different. This sounds like a model bug.
was:
When creating a rdbms_db with referenced entity rdbms_intance, both rdbms_db and rdbms_instance will be created, but when creating another rdbms_db with the same rdbms_instance, the rdbms_instance will be treated as update though they are indeed the same. Looking into the rdbms model, rdbms_instance has attribute "databases" and rdbms_db has attribute "instance" constrained with inverseref to "databases" attribute to rdbms_instance.
So for first creation, rdbms_db will populate the "databases" attribute for rdbms_instance, for the second creation, altas will consider the rdbms_instance not equal since the "databases" attributes are different. This sounds like a model bug.
> Rdbms model
> -----------
>
> Key: ATLAS-2992
> URL: https://issues.apache.org/jira/browse/ATLAS-2992
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 1.0.0
> Reporter: charles shen
> Priority: Minor
>
> There's ownedRef/inverseRef between "rdbms_instance.database, rdbms_db.instance" and "rdbms_db.tables, rdbms_table.db" and more. This caused some performance issue described below:
> When creating a rdbms_db with referenced entity rdbms_intance, both rdbms_db and rdbms_instance will be created, but when creating another rdbms_db with the same rdbms_instance, the rdbms_instance will be treated as update though they are indeed the same. Looking into the rdbms model, rdbms_instance has attribute "databases" and rdbms_db has attribute "instance" constrained with inverseref to "databases" attribute to rdbms_instance. One more thins is the relationship between rdbms_db and rdbms_instance and etc... are already defined in relationship types.
> So for first creation, rdbms_db will populate the "databases" attribute for rdbms_instance, for the second creation, altas will consider the rdbms_instance not equal since the "databases" attributes are different. This sounds like a model bug.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)