You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Mandy Chessell (JIRA)" <ji...@apache.org> on 2017/05/25 19:54:04 UTC

[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas

    [ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025286#comment-16025286 ] 

Mandy Chessell commented on ATLAS-1773:
---------------------------------------

JIRA ATLAS-1700 (https://issues.apache.org/jira/browse/ATLAS-1700) describes the types of constraints that are needed to support the glossary model.  The OMRS Connect needs to support the specification/implementation of constraint classes that are called by the generated OMAS Connector.

> 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: 0.9-incubating
>            Reporter: Mandy Chessell
>            Assignee: Mandy Chessell
>
> 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
(v6.3.15#6346)