atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-535) Support delete cascade efficently
Date Sat, 27 Feb 2016 00:32:18 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170198#comment-15170198
] 

Suma Shivaprasad commented on ATLAS-535:
----------------------------------------

Thanks for reviewing [~yhemanth]. Yes agreed, this has to be a lazy delete/async op. 

Yes, migration between option 2 and 2 is easy since we dont have any entity mutations required
during migration. Type definition updates should suffice.

I had assumed system defined Association Rules will be defined as part of type/model registration
phase and user defined association rules  have limited utility at this point since we do not
allow plugins at different phases - entity CRUD,  lineage etc which make use of user defined
association rules.

Also, like you mentioned the other things to think through is should we allow support for
operation specific rules to . 






> Support delete cascade efficently
> ---------------------------------
>
>                 Key: ATLAS-535
>                 URL: https://issues.apache.org/jira/browse/ATLAS-535
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: Suma Shivaprasad
>             Fix For: 0.7-incubating
>
>
> Currently there are some limitation in the typesystem and modelling to support delete
cascades at scale through the isComposite flag



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message