[
https://issues.apache.org/jira/browse/ATLAS-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855304#comment-15855304
]
Madhan Neethiraj commented on ATLAS-1526:
-----------------------------------------
[~jnhagelb] - thanks for the details. It looks like foreignKey/mappedFromRef
constraints do not handle all the possible use of isComposite/reverseAttribute.
I will shortly update the V2 model with their equivalents - named isOwned,
inverseReferenceBy. I will also remove foreignKey/mappedFromRef - until we have
more clarity on their usage and how they fit with use of
isOwned/inverseReferenceBy.
> update AtlasAttribute with methods to derive legacy flags
> isComposite/reverseAttribute
> --------------------------------------------------------------------------------------
>
> Key: ATLAS-1526
> URL: https://issues.apache.org/jira/browse/ATLAS-1526
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 0.8-incubating
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1526.patch, Atlas-legacy-to-new-ModelMapping.pdf
>
>
> The logic to map legacy attribute flags isComposite/reverseAttribute to its
> equivalent constraints in the new data model is spread across multiple
> locations. Consolidating this logic to a single class will make it easier to
> manage.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
