This is an automated email from the ASF dual-hosted git repository.
guozhang pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 925acc9 KAFKA-4831: add documentation for KIP-265 (#4686)
925acc9 is described below
commit 925acc9f47bb4265f4b033e75467643dbc9ccab9
Author: Guozhang Wang <[email protected]>
AuthorDate: Wed Mar 14 17:33:54 2018 -0700
KAFKA-4831: add documentation for KIP-265 (#4686)
Reviewers: Damian Guy <[email protected]>, Bill Bejeck
<[email protected]>
---
docs/streams/upgrade-guide.html | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/docs/streams/upgrade-guide.html b/docs/streams/upgrade-guide.html
index f5c16c0..46be969 100644
--- a/docs/streams/upgrade-guide.html
+++ b/docs/streams/upgrade-guide.html
@@ -79,7 +79,14 @@
For users who have customized window store implementations on the
above interface, they'd need to update their code to implement the newly added
method as well.
For more details, see <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-261%3A+Add+Single+Value+Fetch+in+Window+Stores";>KIP-261</a>.
</p>
-
+
+ <p>
+ We have added public <code>WindowedSerdes</code> to allow users to
read from / write to a topic storing windowed table changelogs directly.
+ In addition, in <code>StreamsConfig</code> we have also added
<code>default.windowed.key.serde.inner</code> and
<code>default.windowed.value.serde.inner</code>
+ to let users specify inner serdes if the default serde classes are
windowed serdes.
+ For more details, see <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-265%3A+Make+Windowed+Serde+to+public+APIs";>KIP-265</a>.
+ </p>
+
<h3><a id="streams_api_changes_110"
href="#streams_api_changes_110">Streams API changes in 1.1.0</a></h3>
<p>
We have added support for methods in <code>ReadOnlyWindowStore</code>
which allows for querying <code>WindowStore</code>s without the necessity of
providing keys.
--
To stop receiving notification emails like this one, please contact
[email protected].
