diff --git a/docs/streams/upgrade-guide.html b/docs/streams/upgrade-guide.html index 565bd0b263c..462824fdcb4 100644 --- a/docs/streams/upgrade-guide.html +++ b/docs/streams/upgrade-guide.html @@ -100,6 +100,7 @@ +

Streams API changes in 1.2.0

We have removed the skippedDueToDeserializationError-rate and skippedDueToDeserializationError-total metrics. @@ -156,7 +157,10 @@ The new class To allows you to send records to all or specific downstream processors by name and to set the timestamp for the output record. Forwarding based on child index is not supported in the new API any longer.

- +

+ KIP-284 changed the retention time for repartition topics by setting its default value to Long.MAX_VALUE. + Instead of relying on data retention Kafka Streams uses the new purge data API to delete consumed data from those topics and to keep used storage small now. +

Kafka Streams DSL for Scala is a new Kafka Streams client library available for developers authoring Kafka Streams applications in Scala. It wraps core Kafka Streams DSL types to make it easier to call when interoperating with Scala code. For example, it includes higher order functions as parameters for transformations avoiding the need anonymous classes in Java 7 or experimental SAM type conversions in Scala 2.11, automatic conversion between Java and Scala collection types, a way diff --git a/docs/upgrade.html b/docs/upgrade.html index 08cc892d24c..4fe7e20794e 100644 --- a/docs/upgrade.html +++ b/docs/upgrade.html @@ -75,6 +75,7 @@ updated to aggregate across different versions.

  • New Kafka Streams configuration parameter upgrade.from added that allows rolling bounce upgrade from older version.
  • +
  • KIP-284 changed the retention time for repartition topics by setting its default value to Long.MAX_VALUE.
  • New Protocol Versions
    @@ -87,7 +88,6 @@
  • See Streams API changes in 1.2.0 for more details.
  • -

    Upgrading from 0.8.x, 0.9.x, 0.10.0.x, 0.10.1.x, 0.10.2.x, 0.11.0.x or 1.0.x to 1.1.x

    Kafka 1.1.0 introduces wire protocol changes. By following the recommended rolling upgrade plan below, you guarantee no downtime during the upgrade. However, please review the notable changes in 1.1.0 before upgrading. @@ -132,6 +132,7 @@ Hot-swaping the jar-file only might not work. +