Technical preview
Technical preview function is in a state that it can be tried. The development is complete, there is documentation and there are samples, tutorials and hands-on labs as appropriate.
The community is looking for feedback on the function before declaring it stable. This feedback may result in changes to the external interfaces.
Apache Atlas Integration Connector¶
Connector details
- Connector Category: Integration Connector
- Hosting Service: Catalog Integrator OMIS
- Hosting Server: Integration Daemon
- Source Module: atlas-integration-connector
- Jar File Name:
atlas-integration-connector.jar
Overview¶
The Apache Atlas integration connector publishes ACTIVE glossary terms to Apache Atlas. It can be configured to publish just from a single glossary or all glossaries. The connector makes no attempt to detect changes to these glossary terms in Apache Atlas. However, such changes will be overridden the next time the integration connector refreshes the glossary metadata in Apache Atlas.
Figure 1: Operation of the Apache Atlas integration connector
Configuration¶
This connector uses the Catalog Integrator OMIS running in the Integration Daemon.
This is its connection definition to use on the administration commands that configure the Catalog Integrator OMIS if you want all glossaries published to Apache Atlas.
Connection configuration for all glossaries
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
|
- Replace
{{atlasServerURL}}
with the URL of the Apache Atlas server.
Connection configuration for a selected glossary
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
|
- Replace
{{atlasServerURL}}
with the URL of the Apache Atlas server. - Replace
{{glossaryQualifiedName}}
with the qualified name of the Egeria glossary to publish to Apache Atlas.
Raise an issue or comment below