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.
Open Lineage Event Receiver Integration Connector¶
Connector details
- Connector Category: Integration Connector
- Hosting Service: Lineage Integrator OMIS
- Hosting Server: Integration Daemon
- Source Module: openlineage-integration-connectors
- Jar File Name:
openlineage-integration-connectors.jar
The OpenLineage Event Receiver integration connector receives open lineage events from an event topic and publishes them to the lineage integration connectors with OpenLineage listeners registered in the same instance of the Lineage Integrator OMIS.
Figure 1: Operation of the OpenLineage event receiver integration connector
It uses an embedded Open Metadata Topic Connector to receive events from the topic.
Configuration¶
This connector uses the Lineage Integrator OMIS running in the Integration Daemon.
The connection definition to use on the administration commands that configure the Lineage Integrator OMIS is a VirtualConnection with an embedded OpenMetadataTopicConnection.
Connection configuration
1 2 3 4 5 6 7 8 9 10 11 12 13 |
|
- Add the connection for the open metadata topic connector in the
embeddedConnections
section replacing {{topicConnection}}. This will have the topic name in the endpoint'snetworkAddress
. The example below shows the connection for the Kafka open metadata topic connector which supports events from Apache Kafka.
Kafka topic connection configuration
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
|
- Add the name of the topic in {{openLineageTopicName}}; the integration daemon's server id in {{localServerId}} and the endpoint for Apache Kafka (for example localhost:9092) in {{kafkaEndpoint}}.
Raise an issue or comment below