From 676764b923bb8baca2d00b2a5260d243ee3239cf Mon Sep 17 00:00:00 2001 From: gustavomonarin Date: Wed, 11 Nov 2020 18:28:17 +0100 Subject: [PATCH] Fix documentation for kafka streams concurrency on binder level The property spring.cloud.stream.binder.configuration.num.stream.threads does not work and is silently ignored. The property spring.cloud.stream.kafka.streams.binder.configuration.num.stream.threads works fine and is already covered by tests at MultipleFunctionsInSameAppTests#125 resolves #987 --- docs/src/main/asciidoc/kafka-streams.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/kafka-streams.adoc b/docs/src/main/asciidoc/kafka-streams.adoc index 4b0249444..dd24dc1eb 100644 --- a/docs/src/main/asciidoc/kafka-streams.adoc +++ b/docs/src/main/asciidoc/kafka-streams.adoc @@ -1760,5 +1760,5 @@ When using this, you need to use it on the consumer. When you have more than one input bindings either in a function or `StreamListener`, set this on the first input binding. For e.g. when setting `spring.cloud.stream.bindings.process-in-0.consumer.concurrency`, it will be translated as `num.stream.threads` by the binder. If you have multiple processors and one processor defines binding level concurrency, but not the others, those ones with no binding level concurrency will default back to the binder wide property specified through -`spring.cloud.stream.binder.configuration.num.stream.threads`. +`spring.cloud.stream.kafka.streams.binder.configuration.num.stream.threads`. If this binder configuration is not available, then the application will use the default set by Kafka Streams. \ No newline at end of file