diff --git a/docs/streams/architecture.html b/docs/streams/architecture.html index 75d6d3dfb86a1..3ef9dfeed1f90 100644 --- a/docs/streams/architecture.html +++ b/docs/streams/architecture.html @@ -116,7 +116,7 @@

Local

Kafka Streams provides so-called state stores, which can be used by stream processing applications to store and query data, - which is an important capability when implementing stateful operations. The Kafka Streams DSL, for example, automatically creates + which is an important capability when implementing stateful operations. The Kafka Streams DSL, for example, automatically creates and manages such state stores when you are calling stateful operators such as join() or aggregate(), or when you are windowing a stream.

diff --git a/docs/streams/developer-guide/dsl-api.html b/docs/streams/developer-guide/dsl-api.html index db4940fb27322..90e9ad5d95246 100644 --- a/docs/streams/developer-guide/dsl-api.html +++ b/docs/streams/developer-guide/dsl-api.html @@ -3738,7 +3738,7 @@

KTable-KTable Foreign-Key
-

Testing a Streams application

 +

Testing a Streams application

Kafka Streams comes with a test-utils module to help you test your application here.
diff --git a/docs/streams/developer-guide/running-app.html b/docs/streams/developer-guide/running-app.html index 4cf883ed6b621..2f4e2c02c37c0 100644 --- a/docs/streams/developer-guide/running-app.html +++ b/docs/streams/developer-guide/running-app.html @@ -51,7 +51,7 @@

Running Streams Applications

You can run Java applications that use the Kafka Streams library without any additional configuration or requirements. Kafka Streams also provides the ability to receive notification of the various states of the application. The ability to monitor the runtime - status is discussed in the monitoring guide.

+ status is discussed in the monitoring guide.

Table of Contents

- Upgrading from any older version to {{fullDotVersion}} is possible: you will need to do two rolling bounces, where during the first rolling bounce phase you set the config upgrade.from="older version" + Upgrading from any older version to {{fullDotVersion}} is possible: if upgrading from 2.3 or below, you will need to do two rolling bounces, where during the first rolling bounce phase you set the config upgrade.from="older version" (possible values are "0.10.0" - "2.3") and during the second you remove it. This is required to safely upgrade to the new cooperative rebalancing protocol of the embedded consumer. Note that you will remain using the old eager rebalancing protocol if you skip or delay the second rolling bounce, but you can safely switch over to cooperative at any time once the entire group is on 2.4+ by removing the config value and bouncing. For more details please refer to KIP-429: @@ -100,7 +100,7 @@

Streams API We add a new cogroup() operator (via KIP-150>) that allows to aggregate multiple streams in a single operation. Cogrouped streams can also be windowed before they are aggregated. - We refer to the developer guide for more details. + Please refer to the developer guide for more details.

We added a new KStream.toTable() API to translate an input event stream into a changelog stream as per @@ -711,7 +711,7 @@

Streams API If you are monitoring on task level or processor-node / state store level Streams metrics, please note that the metrics sensor name and hierarchy was changed: The task ids, store names and processor names are no longer in the sensor metrics names, but instead are added as tags of the sensors to achieve consistent metrics hierarchy. As a result you may need to make corresponding code changes on your metrics reporting and monitoring tools when upgrading to 1.0.0. - Detailed metrics sensor can be found in the Streams Monitoring section. + Detailed metrics sensor can be found in the Streams Monitoring section.