[ https://issues.apache.org/jira/browse/ATLAS-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856151#comment-15856151 ]
Jeffrey Hagelberg commented on ATLAS-1526: ------------------------------------------ [~madhan.neethiraj] - Thanks. Do you think you could wait until I merge the changes for ATLAS-746 before you commit this? I'll probably do that some time today. I just spent nearly all of yesterday getting all of the new and old test in EntityV2JerseyResourceIT test passing with the latest changes that use the foreignKey/mappedFromRef constraints. These types of changes are very disruptive. > 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.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)