You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 <[email protected]>
<pclass="first">Manually trigger repartitioning of the stream with desired number of partitions. (<aclass="reference external"href="/{{version}}/javadoc/org/apache/kafka/streams/kstream/KStream.html#repartition--">details</a>)</p>
766
766
767
-
<code><spanclass="pre">repartition()</span></code> is similar to <code><spanclass="pre">through()</span></code> however Kafka Streams will manage the topic for you.
767
+
Kafka Streams will manage the topic for <code><spanclass="pre">repartition()</span></code>.
768
768
Generated topic is treated as internal topic, as a result data will be purged automatically as any other internal repartition topic.
769
769
In addition, you can specify the desired number of partitions, which allows to easily scale in/out downstream sub-topologies.
770
-
<code><spanclass="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><spanclass="pre">transform()</span></code> et al.) that do not trigger auto repartitioning when key changing operation is performed beforehand.
770
+
<code><spanclass="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><spanclass="pre">process()</span></code> et al.) that do not trigger auto repartitioning when key changing operation is performed beforehand.
0 commit comments