Nigel Jones commented on ATLAS-1773:

There was a change to egeria yesterday which now requires a change in 

in saveRelationshipReference in the fragment after 'create the RelationshipDef' 
modify the assignment of the metadataCollectionId to:

metadataCollectionId = 

With those patches (plus a webapp/pom.xml atlas dependency change I missed) the 
connector can be started

Also in webapp/src/main/webapp/WEB-INFO/openMetadataContext.xml I *think* we 
need to inclde org.odpi.openmetadata in the spring component scan

My additions so far are attached (intellij 

> Create the OMRS Connector for Atlas
> -----------------------------------
>                 Key: ATLAS-1773
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1773
>             Project: Atlas
>          Issue Type: New Feature
>          Components:  atlas-core
>    Affects Versions: 1.0.0
>            Reporter: Mandy Chessell
>            Assignee: Graham Wallis
>            Priority: Major
>         Attachments: ATLAS-1773-2018-07-12.patch, 
> ATLAS-1773-intellijfix_pom_spring_latestegeria.patch
> This JIRA provides the definition of the OMRS Connector API and an 
> implementation of this API for a local Apache Atlas metadata repository and 
> for the OMRS REST API.
> The OMRS Connector has 3 API groups
> * The types API - this is the metadata API for a metadata repository
> * The entity and relationships APIs that provide the type-agnostic interfaces 
> that can access any type - even those added dynamically
> * The fine-grained type-safe APIs that are generated from the addons models 
> in the build.

This message was sent by Atlassian JIRA

Reply via email to