@itentialopensource/adapter-kafkav2 0.6.3 → 0.6.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,4 +1,20 @@
1
1
 
2
+ ## 0.6.5 [05-19-2023]
3
+
4
+ * added support for separate topics files per adapter
5
+
6
+ See merge request itentialopensource/adapters/notification-messaging/adapter-kafkav2!5
7
+
8
+ ---
9
+
10
+ ## 0.6.4 [05-19-2023]
11
+
12
+ * added support for separate topics files per adapter
13
+
14
+ See merge request itentialopensource/adapters/notification-messaging/adapter-kafkav2!5
15
+
16
+ ---
17
+
2
18
  ## 0.6.3 [05-19-2023]
3
19
 
4
20
  * added support for separate topics files per adapter
package/README.md CHANGED
@@ -92,6 +92,10 @@ This section defines **all** the properties that are available for the adapter,
92
92
  "check_ops_manager_status": false,
93
93
  "iap_apps_check_interval": 15000,
94
94
  "client": {
95
+ "brokers": [
96
+ "broker:9093"
97
+ ],
98
+ "clientId": "my-app",
95
99
  "connectTimeout": 10000,
96
100
  "requestTimeout": 30000,
97
101
  "autoConnect": true,
@@ -212,16 +216,39 @@ Example of adapter's configuration with multiple paritions and subscribers per t
212
216
  ```
213
217
  Note that if no parition is supplied only messages on partition 0 will be consumed. Additionally, if no rabbit topic is supplied, events will be published to a topic with the same name as the Kafka topic. For example, topic `test-6` above will be published to the `test-6` rabbit topic.
214
218
 
219
+ Example of adapter configuration to pass partitions array for one subscriber:
220
+
221
+ Note that you can pass multiple partitions to be consumed under the same subscriber. See example below -
222
+
223
+ ```json
224
+ "topics": [
225
+ {
226
+ "name": "test_topic",
227
+ "always": true,
228
+ "partitions": [
229
+ 1,
230
+ 2
231
+ ],
232
+ "subscriberInfo": [
233
+ {
234
+ "subname": "default",
235
+ "filters": [],
236
+ "rabbit": "test_topic",
237
+ "throttle": {}
238
+ }
239
+ ]
240
+ }
241
+ ]
242
+ ```
243
+
215
244
  ### Connection Properties
216
245
 
217
246
  These base properties are used to connect to Kafka upon the adapter initially coming up. It is important to set these properties appropriately.
218
- Kafka server location is set either by providing (host, port) tuple or by providing hostList property
219
247
 
220
248
  | Property | Description |
221
249
  | ------- | ------- |
222
250
  | host | Optional. A fully qualified domain name or IP address.|
223
251
  | port | Required if `host` set. Used to connect to the server.|
224
- | hostList | Optional. A string of kafka broker/host combination delimited by comma|
225
252
  | interval_time | Optional. The Kafka adapter keeps information about topics and offsets in memory in order to be more efficient. In order to work across restarts the adapter must persist the data. So the data is written into the .topics.json file. This write time defines how often to write the file.|
226
253
  | stub | Optional. Slightlu different meaning than normal, this is just telling the adapter whether to run the write topics interval. This should always be false unless you are running standalone tests.|
227
254
 
@@ -236,15 +263,10 @@ The following properties are used to define the Kafka Client. These properties a
236
263
 
237
264
  | Property | Description |
238
265
  | ------- | ------- |
239
- | connectTimeout | ms it takes to wait for a successful connection before moving to the next host.|
240
- | requestTimeout | ms for a kafka request to timeout .|
241
- | autoConnect | automatically connect when KafkaClient is instantiated otherwise you need to manually call connect.|
242
- | connectRetryOptions | object hash that applies to the initial connection.|
243
- | idleConnection | ms before allowing the broker to disconnect an idle connection from a client. |
244
- | reconnectOnIdle | when the connection is closed due to client idling, client will attempt to auto-reconnect.|
245
- | maxAsyncRequests | maximum async operations at a time toward the kafka cluster..|
266
+ | brokers | kafka broker:port list |
267
+ | clientId | Client-id is a logical grouping of clients with a meaningful name chosen by the client application |
246
268
  | ssl | Object, options to be passed to the tls broker sockets, ex. { rejectUnauthorized: false }.|
247
- | sasl | Object, SASL authentication configuration (only SASL/PLAIN is currently supported), ex. { mechanism: 'plain', username: 'foo', password: 'bar' }.|
269
+ | sasl | Object, SASL authentication configuration (Currently, supports PLAIN, SCRAM-SHA-256, SCRAM-SHA-512), ex. { mechanism: 'plain', username: 'foo', password: 'bar' }.|
248
270
 
249
271
  ### Producer Properties
250
272
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@itentialopensource/adapter-kafkav2",
3
- "version": "0.6.3",
3
+ "version": "0.6.5",
4
4
  "description": "Itential adapter to connect to kafka",
5
5
  "main": "adapter.js",
6
6
  "wizardVersion": "2.35.0",
Binary file