From 33fa572a1c3de5630c3dc196ec5ef824863e2c40 Mon Sep 17 00:00:00 2001 From: PoAn Yang Date: Wed, 9 Apr 2025 09:10:25 +0800 Subject: [PATCH] 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 --- 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<byte[], String> table = stream.toTable();

Manually trigger repartitioning of the stream with desired number of partitions. (details)

- repartition() is similar to through() however Kafka Streams will manage the topic for you. + Kafka Streams will manage the topic for repartition(). 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. - repartition() operation always triggers repartitioning of the stream, as a result it can be used with embedded Processor API methods (like transform() et al.) that do not trigger auto repartitioning when key changing operation is performed beforehand. + repartition() operation always triggers repartitioning of the stream, as a result it can be used with embedded Processor API methods (like process() et al.) that do not trigger auto repartitioning when key changing operation is performed beforehand. 
KStream<byte[], String> stream = ... ;
 KStream<byte[], String> repartitionedStream = stream.repartition(Repartitioned.numberOfPartitions(10));