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: docs/aws-s3-sink.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -146,7 +146,6 @@ Before using the AWS S3 sink connector, you need to configure it. This table out
146
146
|`batchTimeMs`| long | False | false | 1000 | The interval for batch submission. |
147
147
|`maxBatchBytes`| long | False | false | 10000000 | The maximum number of bytes in a batch. |
148
148
|`batchModel`| Enum | False | false | BLEND | Determines how records are batched. Options: `BLEND`, `PARTITIONED`. The BLEND which combines all topic records into a single batch, optimizing for throughput, and PARTITIONED which batches records separately for each topic, maintaining topic-level separation. Note: When set to PARTITIONED, the connector will cache data up to the size of the number of subscribed topics multiplied by maxBatchBytes. This means you need to anticipate the connector's memory requirements in advance. |
149
-
|`pendingQueueSize`| int | False | false | 10 | The number of records buffered in queue. By default, it is equal to `batchSize`. You can set it manually. |
150
149
|`skipFailedMessages`| Boolean | False | false | false | Configure whether to skip a message which it fails to be processed. If it is set to `true`, the connector will skip the failed messages by `ack` it. Otherwise, the connector will `fail` the message. |
151
150
|`withMetadata`| Boolean | False | false | false | Save message attributes to metadata. |
152
151
|`useHumanReadableMessageId`| Boolean | False | false | false | Use a human-readable format string for messageId in message metadata. The messageId is in a format like `ledgerId:entryId:partitionIndex:batchIndex`. Otherwise, the messageId is a Hex-encoded string. |
Copy file name to clipboardExpand all lines: docs/azure-blob-storage-sink.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,7 +127,6 @@ Before using the Azure Blob Storage sink connector, you need to configure it. Th
127
127
|`batchTimeMs`| long | False | false | 1000 | The interval for batch submission. |
128
128
|`maxBatchBytes`| long | False | false | 10000000 | The maximum number of bytes in a batch. |
129
129
|`batchModel`| Enum | False | false | BLEND | Determines how records are batched. Options: `BLEND`, `PARTITIONED`. The BLEND which combines all topic records into a single batch, optimizing for throughput, and PARTITIONED which batches records separately for each topic, maintaining topic-level separation. Note: When set to PARTITIONED, the connector will cache data up to the size of the number of subscribed topics multiplied by maxBatchBytes. This means you need to anticipate the connector's memory requirements in advance. |
130
-
|`pendingQueueSize`| int | False | false | 10 | The number of records buffered in queue. By default, it is equal to `batchSize`. You can set it manually. |
131
130
|`skipFailedMessages`| Boolean | False | false | false | Configure whether to skip a message which it fails to be processed. If it is set to `true`, the connector will skip the failed messages by `ack` it. Otherwise, the connector will `fail` the message. |
132
131
|`withMetadata`| Boolean | False | false | false | Save message attributes to metadata. |
133
132
|`useHumanReadableMessageId`| Boolean | False | false | false | Use a human-readable format string for messageId in message metadata. The messageId is in a format like `ledgerId:entryId:partitionIndex:batchIndex`. Otherwise, the messageId is a Hex-encoded string. |
Copy file name to clipboardExpand all lines: docs/google-cloud-storage-sink.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,6 @@ Before using the Google Cloud Storage sink connector, you need to configure it.
132
132
|`batchTimeMs`| long | False | false | 1000 | The interval for batch submission. |
133
133
|`maxBatchBytes`| long | False | false | 10000000 | The maximum number of bytes in a batch. |
134
134
|`batchModel`| Enum | False | false | BLEND | Determines how records are batched. Options: `BLEND`, `PARTITIONED`. The BLEND which combines all topic records into a single batch, optimizing for throughput, and PARTITIONED which batches records separately for each topic, maintaining topic-level separation. Note: When set to PARTITIONED, the connector will cache data up to the size of the number of subscribed topics multiplied by maxBatchBytes. This means you need to anticipate the connector's memory requirements in advance. |
135
-
|`pendingQueueSize`| int | False | false | 10 | The number of records buffered in queue. By default, it is equal to `batchSize`. You can set it manually. |
136
135
|`skipFailedMessages`| Boolean | False | false | false | Configure whether to skip a message which it fails to be processed. If it is set to `true`, the connector will skip the failed messages by `ack` it. Otherwise, the connector will `fail` the message. |
137
136
|`withMetadata`| Boolean | False | false | false | Save message attributes to metadata. |
138
137
|`useHumanReadableMessageId`| Boolean | False | false | false | Use a human-readable format string for messageId in message metadata. The messageId is in a format like `ledgerId:entryId:partitionIndex:batchIndex`. Otherwise, the messageId is a Hex-encoded string. |
0 commit comments