You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2019/02/22 02:37:00 UTC

[jira] [Created] (ATLAS-3056) update rdbms types to remove use of ownedRef/inverseRef constraints for relationships

Madhan Neethiraj created ATLAS-3056:
---------------------------------------

             Summary: update rdbms types to remove use of ownedRef/inverseRef constraints for relationships
                 Key: ATLAS-3056
                 URL: https://issues.apache.org/jira/browse/ATLAS-3056
             Project: Atlas
          Issue Type: Improvement
          Components:  atlas-core
            Reporter: Madhan Neethiraj
            Assignee: Madhan Neethiraj


RDBMS types use following attributes, with ownedRef/inverseRef constraints, to create relationships between entity-types:
- rdbms_instance.database, rdbms_db.instance
- rdbms_db.tables, rdbms_table.db
- rdbms_table.columns, rdbms_column.table
- rdbms_table.indexes, rdbms_index.table
- rdbms_table.foreign_keys, rdbms_foreign_key.table

These attributes are not necessary, as corresponding relationship-types (already present in the model) will automatically inject the same attributes as relationship-attributes.

Above change has several benefits, including:
- improved performance, due to use of only one edge between two related entities (compare this to 2 edges when ownedRef/inverseRef constraints are used)
- simper to update a container entity, as there is not need to provide all contained entities; same for contained entities as well




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)