You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,25 +11,25 @@ Using the SDK, you can build Java applications to automate data platform operati
11
11
- Notify downstream consumers when data contract tests have failed
12
12
- Publish data product costs and usage data to Data Mesh Manager
13
13
14
-
This SDK is designed as a foundation for building data platform integrations that run as long-running agents on customer's data platform, e.g., as containers running in a Kubernetes cluster or any other container-runtime.
14
+
This SDK is designed as a foundation for building data platform integrations that run as long-running connectors on customer's data platform, e.g., as containers running in a Kubernetes cluster or any other container-runtime.
15
15
16
16
It interacts with the Data Mesh Manager APIs to send metadata and to subscribe to events to trigger actions in the data platform or with other services.
17
17
18
18
19
-
Existing Integrations
19
+
Existing Connectors
20
20
---
21
21
22
-
We provide some agents for commonly-used platforms that that use this SDK and that can be used out-of-the-box or as a template for custom integrations:
22
+
We provide some connectors for commonly-used platforms that that use this SDK and that can be used out-of-the-box or as a template for custom integrations:
var eventListener =newDataMeshManagerEventListener(agentid, client, eventHandler, stateRepository);
128
-
eventListener.start(); // This will start a long-running agent that listens to events from Data Mesh Manager
127
+
var eventListener =newDataMeshManagerEventListener(connectorid, client, eventHandler, stateRepository);
128
+
eventListener.start(); // This will start a long-running connector that listens to events from Data Mesh Manager
129
129
```
130
130
131
-
If you have multiple agents in an application, make sure to start the `start()` methods in separate threads.
131
+
If you have multiple connectors in an application, make sure to start the `start()` methods in separate threads.
132
132
133
133
### State Repository
134
134
135
135
The `DataMeshManagerEventListener` requires a `DataMeshManagerStateRepository` to store the `lastEventId` that has been processed.
136
-
Also, you can use the state repository in other agents, if you need to store information what has been processed or what is the current state of your agent.
136
+
Also, you can use the state repository in other connectors, if you need to store information what has been processed or what is the current state of your connector.
137
137
You can implement this interface to store the state in a database, a file, or any other storage:
138
138
139
139
```java
@@ -146,8 +146,8 @@ public interface DataMeshManagerStateRepository {
146
146
For your convenience, you can use the `DataMeshManagerStateRepositoryRemote` to store the state directly in the Data Mesh Manager:
147
147
148
148
```java
149
-
varagentId="my-unique-event-listener-agent-id";
150
-
var stateRepository =newDataMeshManagerStateRepositoryRemote(agentId, client);
0 commit comments