- Upgrading from any older version to 2.0.0 is possible: (1) you need to make sure to update you code and config accordingly, because there are some minor non-compatible API changes since older
- releases (the code changes are expected to be minimal, please see below for the details),
- (2) upgrading to 2.0.0 in the online mode requires two rolling bounces.
- For (2), in the first rolling bounce phase users need to set config upgrade.from="older version" (possible values are "0.10.0", "0.10.1", "0.10.2", "0.11.0", "1.0", and "1.1")
+ Upgrading from any older version to {{fullDotVersion}} is possible: (1) if you are upgrading from 2.0.x to {{fullDotVersion}} then a single rolling bounce is needed to swap in the new jar,
+ (2) if you are upgrading from older versions than 2.0.x in the online mode, you would need two rolling bounces where
+ the first rolling bounce phase you need to set config upgrade.from="older version" (possible values are "0.10.0", "0.10.1", "0.10.2", "0.11.0", "1.0", and "1.1")
(cf. KIP-268):
upgrade.from is set to the version from which it is being upgrade to new version 2.0.0upgrade.from is set to the version from which it is being upgrade.upgrade.mode upgrade.mode As an alternative, an offline upgrade is also possible. Upgrading from any versions as old as 0.10.0.x to 2.0.0 in offline mode require the following steps:
+As an alternative, an offline upgrade is also possible. Upgrading from any versions as old as 0.10.0.x to {{fullDotVersion}} in offline mode require the following steps:
@@ -65,10 +64,37 @@
accidentally: we still reuse the source topic as the changelog topic for restoring, but will also create a separate changelog topic to append the update records from source topic to. In the 2.0 release, we have fixed this issue and now users
can choose whether or not to reuse the source topic based on the StreamsConfig#TOPOLOGY_OPTIMIZATION: if you are upgrading from the old KStreamBuilder class and hence you need to change your code to use
the new StreamsBuilder, you should set this config value to StreamsConfig#OPTIMIZE to continue reusing the source topic; if you are upgrading from 1.0 or 1.1 where you are already using StreamsBuilder and hence have already
- created a separate changelog topic, you should set this config value to StreamsConfig#NO_OPTIMIZATION when upgrading to 2.0.0 in order to use that changelog topic for restoring the state store.
+ created a separate changelog topic, you should set this config value to StreamsConfig#NO_OPTIMIZATION when upgrading to {{fullDotVersion}} in order to use that changelog topic for restoring the state store.
More details about the new config StreamsConfig#TOPOLOGY_OPTIMIZATION can be found in KIP-295.
+ We updated TopologyDescription API to allow for better runtime checking.
+ Users are encouraged to use #topicSet() and #topicPattern() accordingly on TopologyDescription.Source nodes,
+ instead of using #topics(), which has since been deprecated. Similarly, use #topic() and #topicNameExtractor()
+ to get descriptions of TopologyDescription.Sink nodes. For more details, see
+ KIP-321.
+
+ We've added a new config named max.task.idle.ms to allow users specify how to handle out-of-order data within a task that may be processing multiple
+ topic-partitions (see Out-of-Order Handling section for more details).
+ The default value is set to 0, to favor minimized latency over synchronization between multiple input streams from topic-partitions.
+ If users would like to wait for longer time when some of the topic-partitions do not have data available to process and hence cannot determine its corresponding stream time,
+ they can override this config to a larger value.
+
+ We've added the missing SessionBytesStoreSupplier#retentionPeriod() to be consistent with the WindowBytesStoreSupplier which allows users to get the specified retention period for session-windowed stores.
+ We've also added the missing StoreBuilder#withCachingDisabled() to allow users to turn off caching for their customized stores.
+
+ We added a new serde for UUIDs (Serdes.UUIDSerde) that you can use via Serdes.UUID() (cf. KIP-206).
+
In 2.0.0 we have added a few new APIs on the ReadOnlyWindowStore interface (for details please read Streams API changes below).
If you have customized window store implementations that extends the ReadOnlyWindowStore interface you need to make code changes.
@@ -90,29 +116,6 @@
We have also removed some public APIs that are deprecated prior to 1.0.x in 2.0.0.
See below for a detailed list of removed APIs.
- We updated TopologyDescription API to allow for better runtime checking.
- Users are encouraged to use #topicSet() and #topicPattern() accordingly on TopologyDescription.Source nodes,
- instead of using #topics(), which has since been deprecated. Similarly, use #topic() and #topicNameExtractor()
- to get descriptions of TopologyDescription.Sink nodes. For more details, see
- KIP-321.
-
- We've added a new config named max.task.idle.ms to allow users specify how to handle out-of-order data within a task that may be processing multiple
- topic-partitions (see Out-of-Order Handling section for more details).
- The default value is set to 0, to favor minimized latency over synchronization between multiple input streams from topic-partitions.
- If users would like to wait for longer time when some of the topic-partitions do not have data available to process and hence cannot determine its corresponding stream time,
- they can override this config to a larger value.
-
- We added a new serde for UUIDs (Serdes.UUIDSerde) that you can use via Serdes.UUID() (cf. KIP-206).
-
We have removed the skippedDueToDeserializationError-rate and skippedDueToDeserializationError-total metrics.
Deserialization errors, and all other causes of record skipping, are now accounted for in the pre-existing metrics