(kafka) branch 4.0 updated: MINOR: remove transform and through from repartition description (#19291)

[mjsax]

This is an automated email from the ASF dual-hosted git repository.

mjsax pushed a commit to branch 4.0
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/4.0 by this push:
     new 33fa572a1c3 MINOR: remove transform and through from repartition 
description (#19291)
33fa572a1c3 is described below

commit 33fa572a1c3de5630c3dc196ec5ef824863e2c40
Author: PoAn Yang <pay...@apache.org>
AuthorDate: Wed Apr 9 09:10:25 2025 +0800

    MINOR: remove transform and through from repartition description (#19291)
    
    `transform` and `through` are removed in 4.0. Since users cannot
    reference them in 4.0 document, it's not good to keep using them as
    example in `repartition` description.
    
    Reviewers: Matthias J. Sax <matth...@confluent.io>
---
 docs/streams/developer-guide/dsl-api.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/streams/developer-guide/dsl-api.html 
b/docs/streams/developer-guide/dsl-api.html
index b59ac764f32..8e8a36f76c0 100644
--- a/docs/streams/developer-guide/dsl-api.html
+++ b/docs/streams/developer-guide/dsl-api.html
@@ -764,10 +764,10 @@ KTable&lt;byte[], String&gt; table = 
stream.toTable();</code></pre>
                         <td>
                             <p class="first">Manually trigger repartitioning 
of the stream with desired number of partitions. (<a class="reference external" 
href="/{{version}}/javadoc/org/apache/kafka/streams/kstream/KStream.html#repartition--">details</a>)</p>
 
-                            <code><span 
class="pre">repartition()</span></code> is similar to <code><span 
class="pre">through()</span></code> however Kafka Streams will manage the topic 
for you.
+                            Kafka Streams will manage the topic for 
<code><span class="pre">repartition()</span></code>.
                             Generated topic is treated as internal topic, as a 
result data will be purged automatically as any other internal repartition 
topic.
                             In addition, you can specify the desired number of 
partitions, which allows to easily scale in/out downstream sub-topologies.
-                            <code><span 
class="pre">repartition()</span></code> operation always triggers 
repartitioning of the stream, as a result it can be used with embedded 
Processor API methods (like <code><span class="pre">transform()</span></code> 
et al.) that do not trigger auto repartitioning when key changing operation is 
performed beforehand.
+                            <code><span 
class="pre">repartition()</span></code> operation always triggers 
repartitioning of the stream, as a result it can be used with embedded 
Processor API methods (like <code><span class="pre">process()</span></code> et 
al.) that do not trigger auto repartitioning when key changing operation is 
performed beforehand.
 
                             <pre class="line-numbers"><code 
class="language-java">KStream&lt;byte[], String&gt; stream = ... ;
 KStream&lt;byte[], String&gt; repartitionedStream = 
stream.repartition(Repartitioned.numberOfPartitions(10));</code></pre>