[
https://issues.apache.org/jira/browse/ATLAS-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857765#comment-15857765
]
David Radley commented on ATLAS-1526:
-------------------------------------
[~madhan.neethiraj] I suggest that this is put out in a small design document,
spelling out the V1 situations, the recent changes and the new proposal. In
that way, the wider community could be more readily engaged to feedback. I
think the way we implement relationships is key basic capability that deserves
this level of scrutiny, all the best, David.
> 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.3.patch, ATLAS-1526.4.patch,
> 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)
