[
https://issues.apache.org/jira/browse/ATLAS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458681#comment-16458681
]
David Radley commented on ATLAS-2139:
-------------------------------------
[~sethv] Mandy is not available this week.
My thoughts on your questions are:
1. getSkeletonEntity is javadoc says "Return an entity with the header and type
information filled out. The caller only needs to add properties and
classifications to complete the set up of the entity." The way I am reading
this is that I would not expect it to fill in properties, as the caller is
expected to do this.
2. The way the OMRS is, means that entities and relationships are created
independently, but you need information from more than 1 entity or
relationship, in order to issue the IGC call. If I have interpreted this
correctly, my suggestion is :
- the IGC local connector keeps the entities and relationships until it has
enough information (schema rids and the like) to issue the IGC request. Is
there a way you can persist this information in IGC.
or
-The local connector could query IGC for information that is not supplied in an
add entity, this may allow you to access the rid information you need.
> Map IGC meta model and Atlas OMRS open metadata types
> -----------------------------------------------------
>
> Key: ATLAS-2139
> URL: https://issues.apache.org/jira/browse/ATLAS-2139
> Project: Atlas
> Issue Type: Sub-task
> Reporter: Jerry He
> Assignee: Jerry He
> Priority: Major
> Attachments: Relational Tables and Columns.png
>
>
> Create the two-way mapping between IGC meta model and Atlas OMRS open
> metadata types.
> It is used by the IGC Event Mapper and IGC metadata repository connector.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
