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
Address translator support and configuration related documentation (#12)
* support for record to table mapping config
* some minor bug fixes
* error handling and ssl config support
* some typo mistake fix
* support for address translator
* documentation changes for new configs
* resolved review comments
* renamed ComposeAddressTranslator to ClusterAddressTranslator
* addressed review comments
Copy file name to clipboardExpand all lines: documentation/CONFIG.md
+82-6Lines changed: 82 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,15 @@ Connector-specific configuration properties are described below.
13
13
14
14
``scylladb.contact.points``
15
15
16
-
The ScyllaDB hosts to connect to. Scylla nodes use this list of hosts to find each other and learn the topology of the ring. You must change this if you are running multiple nodes.
17
-
It's essential to put at least 2 hosts in case of bigger cluster, since if first host is down, it will contact second one and get the state of the cluster from it.
18
-
Eg. When using the docker image, connect to the host it uses.
16
+
The ScyllaDB hosts to connect to. Scylla nodes use this list of hosts to find each other and learn the topology of the ring.
17
+
You must change this if you are running multiple nodes.
18
+
It's essential to put at least 2 hosts in case of bigger cluster, since if first host is down,
19
+
it will contact second one and get the state of the cluster from it.
20
+
Eg. When using the docker image, connect to the host it uses.
21
+
To connect to private Scylla nodes, provide a JSON string having all internal private network address:port mapped to
22
+
an external network address:port as key value pairs. Need to pass it as
Flag to determine if the connector should process deletes.
175
227
The Kafka records with kafka record value as null will result in deletion of ScyllaDB record
176
228
with the primary key present in Kafka record key.
@@ -206,6 +258,7 @@ Connector-specific configuration properties are described below.
206
258
* Default Value: True
207
259
208
260
``scylladb.max.batch.size.kb``
261
+
209
262
Maximum size(in kilobytes) of a single batch consisting ScyllaDB operations. This should be equal to
210
263
batch_size_warn_threshold_in_kb and 1/10th of the batch_size_fail_threshold_in_kb configured in scylla.yaml.
211
264
The default value is set to 5kb, any change in this configuration should be accompanied by change in scylla.yaml.
@@ -224,6 +277,27 @@ Connector-specific configuration properties are described below.
224
277
* Importance: Low
225
278
* Valid Values: [0,...]
226
279
* Default Value: 0
280
+
281
+
###ScyllaDB
282
+
283
+
``behavior.on.error``
284
+
285
+
Error handling behavior setting. Must be configured to one of the following:
286
+
287
+
``fail``
288
+
The Connector throws ConnectException and stops processing records when an error occurs while processing or inserting records into ScyllaDB.
289
+
290
+
``ignore``
291
+
Continues to process next set of records when error occurs while processing or inserting records into ScyllaDB.
292
+
293
+
``log``
294
+
Logs the error via connect-reporter when an error occurs while processing or inserting records into ScyllaDB and continues to process next set of records, available in the kafka topics.
295
+
296
+
* Type: string
297
+
* Default: FAIL
298
+
* Valid Values: [FAIL, LOG, IGNORE]
299
+
* Importance: medium
300
+
227
301
228
302
###Confluent Platform Configurations.
229
303
@@ -232,6 +306,7 @@ Connector-specific configuration properties are described below.
232
306
The maximum number of tasks to use for the connector that helps in parallelism.
233
307
234
308
* Type:int
309
+
* Default: 1
235
310
* Importance: high
236
311
237
312
``topics``
@@ -246,6 +321,7 @@ The name of the topics to consume data from and write to ScyllaDB.
246
321
A list of host/port pairs to use for establishing the initial connection to the Kafka cluster used for licensing. All servers in the cluster will be discovered from the initial connection. This list should be in the form <code>host1:port1,host2:port2,…</code>. Since these servers are just used for the initial connection to discover the full cluster membership (which may change dynamically), this list need not contain the full set of servers (you may want more than one, though, in case a server is down).
0 commit comments