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
There are several settings specific to the library.
30
30
31
-
-`withBlocker` sets the `Blocker` on which blocking Java Kafka `AdminClient` functions are executed. Unless specified, a default fixed single-thread pool is created as part of admin client initialization, with the thread name using the `fs2-kafka-admin-client` prefix.
32
-
33
31
-`withCloseTimeout` controls the timeout when waiting for admin client shutdown. Default is 20 seconds.
34
32
35
33
-`withCreateAdminClient` changes how the underlying Java Kafka admin client is created. The default creates a Java `AdminClient` instance using set properties, but this function allows overriding the behaviour for e.g. testing purposes.
@@ -39,7 +37,7 @@ There are several settings specific to the library.
39
37
Once settings are defined, we can use create an admin client in a `Stream`.
Copy file name to clipboardExpand all lines: docs/src/main/mdoc/consumers.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,8 +144,6 @@ In addition, there are several settings specific to the library.
144
144
145
145
-`withCreateConsumer` changes how the underlying Java Kafka consumer is created. The default merely creates a Java `KafkaConsumer` instance using set properties, but this function allows overriding the behaviour for e.g. testing purposes.
146
146
147
-
-`withBlocker` sets the `Blocker` on which blocking Java Kafka consumer functions are executed. Unless specified, a default fixed single-thread pool is created as part of consumer initialization, with the thread name using the `fs2-kafka-consumer` prefix.
148
-
149
147
-`withMaxPrefetchBatches` adjusts the maximum number of record batches per topic-partition to prefetch before backpressure is applied. The default is 2, meaning there can be up to 2 record batches per topic-partition waiting to be processed.
150
148
151
149
-`withPollInterval` alters how often consumer `poll` should take place. Default is 50 milliseconds.
@@ -344,7 +342,7 @@ To achieve this behavior we could use a `stopConsuming` method on a` KafkaConsum
344
342
We could combine `stopConsuming` with the custom resource handling and implement a graceful shutdown. Let's try it:
Copy file name to clipboardExpand all lines: docs/src/main/mdoc/producers.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,8 +134,6 @@ The following settings are specific to the library.
134
134
135
135
-`withCreateProducer` changes how the underlying Java Kafka producer is created. The default merely creates a Java `KafkaProducer` instance using set properties, but this function allows overriding the behaviour for e.g. testing purposes.
136
136
137
-
-`withBlocker` sets the `Blocker` on which blocking Java Kafka producer functions are executed. Unless specified, a default fixed single-thread pool is created as part of producer initialization, with the thread name using the `fs2-kafka-producer` prefix.
138
-
139
137
## Producer Creation
140
138
141
139
Once [`ProducerSettings`][producersettings] is defined, use `KafkaProducer.stream` to create a [`KafkaProducer`][kafkaproducer] instance.
0 commit comments