From 90d0fd51d1e73d1bb93ba304c72972a515908a40 Mon Sep 17 00:00:00 2001 From: Bill Bejeck Date: Mon, 15 Oct 2018 21:26:18 -0700 Subject: [PATCH] MINOR: Doc changes for KIP-312 (#5789) Documentation changes for adding overloaded StreamsBuilder(java.util.Properties props) method in KIP-312 Reviewers: Matthias J. Sax , Guozhang Wang --- docs/streams/upgrade-guide.html | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/docs/streams/upgrade-guide.html b/docs/streams/upgrade-guide.html index c0f28efe98b..660b8179a86 100644 --- a/docs/streams/upgrade-guide.html +++ b/docs/streams/upgrade-guide.html @@ -140,10 +140,22 @@ If you implement custom windows, you should update your code accordingly. Similarly, WindowBytesStoreSupplier#segments() was deprecated and replaced with WindowBytesStoreSupplier#segmentInterval(). If you implement custom window store, you need to update your code accordingly. - Finally, Stores#persistentWindowStore(...) were deprecated and replaced with a new overload that does not allow to specify the number of segments any longer. + Finally, Stores#persistentWindowStore(...) were deprecated and replaced with a new overload that does not allow to specify the number of segments any longer. For more details, see KIP-319 (note: KIP-328 and - KIP-358 'overlap' with KIP-319). + KIP-358 'overlap' with KIP-319). +

+ +

+ We've added an overloaded StreamsBuilder#build method that accepts an instance of java.util.Properties with the intent of using the + StreamsConfig#TOPOLOGY_OPTIMIZATION config added in Kafka Streams 2.0. Before 2.1, when building a topology with + the DSL, Kafka Streams writes the physical plan as the user makes calls on the DSL. Now by providing a java.util.Properties instance when + executing a StreamsBuilder#build call, Kafka Streams can optimize the physical plan of the topology, provided the StreamsConfig#TOPOLOGY_OPTIMIZATION + config is set to StreamsConfig#OPTIMIZE. By setting StreamsConfig#OPTIMIZE in addition to the KTable optimization of + reusing the source topic as the changelog topic, the topology may be optimized to merge redundant repartition topics into one + repartition topic. The original no parameter version of StreamsBuilder#build is still available for those who wish to not + optimize their topology. Note that enabling optimization of the topology may require you to do an application reset when redeploying the application. For more + details, see KIP-312

Streams API changes in 2.0.0