[
https://issues.apache.org/jira/browse/ATLAS-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861695#comment-15861695
]
David Kantor commented on ATLAS-1526:
-------------------------------------
Hi [~madhan.neethiraj], what is the status of this patch? I'm asking because
last week I had begun applying changes to the V2 code path for support auto
update of reverse references (ATLAS-499), and those changes had relied on the
new mappedFromRef constraint. When I saw your comment on Feb 6 that this
constraint was being removed, I discarded those changes and have been awaiting
the resolution of this Jira so I can move forward with the V2 changes. I have
implemented the V1 code path changes for 499 - see
https://reviews.apache.org/r/56287/ if you'd like to review.
> 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)
