Minor typo: "result _is_ a" > "result _in_ a" (#11876)

Reviewers Bill Bejeck <bbejeck@apache.org>
This commit is contained in:
aSemy 2022-03-10 20:03:12 +01:00 committed by GitHub
parent 84b41b9d3a
commit 38e3787d76
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -1732,7 +1732,7 @@ KTable&lt;String, Integer&gt; aggregated = groupedTable.aggregate(
You may follow a procedure such as outlined below. You may follow a procedure such as outlined below.
It is recommended to repartition the topic with fewer partitions to match the larger partition number of avoid bottlenecks. It is recommended to repartition the topic with fewer partitions to match the larger partition number of avoid bottlenecks.
Technically it would also be possible to repartition the topic with more partitions to the smaller partition number. Technically it would also be possible to repartition the topic with more partitions to the smaller partition number.
For stream-table joins, it's recommended to repartition the KStream because repartitioning a KTable might result is a second state store. For stream-table joins, it's recommended to repartition the KStream because repartitioning a KTable might result in a second state store.
For table-table joins, you might also consider to size of the KTables and repartition the smaller KTable.</p> For table-table joins, you might also consider to size of the KTables and repartition the smaller KTable.</p>
<ol class="arabic"> <ol class="arabic">
<li><p class="first">Identify the input KStream/KTable in the join whose underlying Kafka topic has the smaller number of partitions. <li><p class="first">Identify the input KStream/KTable in the join whose underlying Kafka topic has the smaller number of partitions.