-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IGC OMRS Repository Connector clarification #135
Comments
Hello Chris,
It is not true (not for a long time :)
Maybe something like
Other metadata repositories that have their own API can create a connector
to translate OMRS calls to call to their API. The IGC OMRS Repository
Connector from the virtual-data-connector demo is an example of this type
of OMRS connector.
All the best
Mandy
…___________________________________________
Mandy Chessell CBE FREng CEng FBCS
IBM Distinguished Engineer
Master Inventor
Member of the IBM Academy of Technology
Visiting Professor, Department of Computer Science, University of
Sheffield
Email: mandy_chessell@uk.ibm.com
LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49
Assistant: Janet Brooks - jsbrooks12@uk.ibm.com
From: Christopher Grote <notifications@github.com>
To: odpi/egeria <egeria@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Date: 03/08/2018 15:08
Subject: [odpi/egeria] IGC OMRS Repository Connector clarification
(#135)
Is this statement still accurate?
"C - Other metadata repositories that have their own API can create a
connector to translate OMRS calls to call to their API. The IGC OMRS
Repository Connector is an example of this type of OMRS connector written
to support a specific metadata repository that is not Apache Atlas. This
OMRS Connector will be included in the Apache Atlas build so it can be
called directly from the Enterprise OMRS Connector rather than via a
remote REST call."
(
open-metadata-implementation/repository-services/docs/component-descriptions/connectors/repository-connector.md
)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
|
Thanks! Added to PR #139. |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this statement still accurate?
"C - Other metadata repositories that have their own API can create a connector to translate OMRS calls to call to their API. The IGC OMRS Repository Connector is an example of this type of OMRS connector written to support a specific metadata repository that is not Apache Atlas. This OMRS Connector will be included in the Apache Atlas build so it can be called directly from the Enterprise OMRS Connector rather than via a remote REST call."
(
open-metadata-implementation/repository-services/docs/component-descriptions/connectors/repository-connector.md
)The text was updated successfully, but these errors were encountered: