diff --git a/docs/streams/developer-guide/dsl-api.html b/docs/streams/developer-guide/dsl-api.html index e54d4491c739a..02f2441a57db7 100644 --- a/docs/streams/developer-guide/dsl-api.html +++ b/docs/streams/developer-guide/dsl-api.html @@ -261,7 +261,7 @@
You must specify SerDes explicitly if the key or value types of the records in the Kafka input topics do not match the configured default SerDes. For information about configuring default SerDes, available SerDes, and implementing your own custom SerDes see Data Types and Serialization.
-Several variants of stream exist, for example to specify a regex pattern for input topics to read from).
Several variants of stream exist. For example, you can specify a regex pattern for input topics to read from (note that all matching topics will be part of the same input topic group, and the work will not be parallelized for different topics if subscribed to in this way).
Table
diff --git a/streams/src/main/java/org/apache/kafka/streams/StreamsBuilder.java b/streams/src/main/java/org/apache/kafka/streams/StreamsBuilder.java index 609bce5caabaa..8d650d2dcefa5 100644 --- a/streams/src/main/java/org/apache/kafka/streams/StreamsBuilder.java +++ b/streams/src/main/java/org/apache/kafka/streams/StreamsBuilder.java @@ -148,7 +148,9 @@ public synchronized* If multiple topics are matched by the specified pattern, the created {@link KStream} will read data from all of - * them and there is no ordering guarantee between records from different topics. + * them and there is no ordering guarantee between records from different topics. This also means that the work + * will not be parallelized for multiple topics, and the number of tasks will scale with the maximum partition + * count of any matching topic rather than the total number of partitions across all topics. *
* Note that the specified input topics must be partitioned by key.
* If this is not the case it is the user's responsibility to repartition the data before any key based operation
@@ -167,7 +169,9 @@ public synchronized
* If multiple topics are matched by the specified pattern, the created {@link KStream} will read data from all of
- * them and there is no ordering guarantee between records from different topics.
+ * them and there is no ordering guarantee between records from different topics. This also means that the work
+ * will not be parallelized for multiple topics, and the number of tasks will scale with the maximum partition
+ * count of any matching topic rather than the total number of partitions across all topics.
*
* Note that the specified input topics must be partitioned by key.
* If this is not the case it is the user's responsibility to repartition the data before any key based operation