This is an automated email from the ASF dual-hosted git repository.
mjsax pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 90c3683 KAFKA-8213 DOCS (kafka-site) Fix typo in Streams Dev Guide
(#201)
90c3683 is described below
commit 90c3683f19314bdfe52cc5f0e9d78197b950891b
Author: Victoria Bialas <londoncall...@users.noreply.github.com>
AuthorDate: Sat Apr 13 15:33:59 2019 -0700
KAFKA-8213 DOCS (kafka-site) Fix typo in Streams Dev Guide (#201)
Reviewer: Matthias J. Sax <matth...@confluent.io>
---
10/streams/developer-guide/interactive-queries.html | 2 +-
11/streams/developer-guide/interactive-queries.html | 2 +-
20/streams/developer-guide/interactive-queries.html | 2 +-
21/streams/developer-guide/interactive-queries.html | 2 +-
22/streams/developer-guide/interactive-queries.html | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/10/streams/developer-guide/interactive-queries.html
b/10/streams/developer-guide/interactive-queries.html
index 3c3c20a..236e92a 100644
--- a/10/streams/developer-guide/interactive-queries.html
+++ b/10/streams/developer-guide/interactive-queries.html
@@ -59,7 +59,7 @@
<p>There are local and remote components to interactively querying the
state of your application.</p>
<dl class="docutils">
<dt>Local state</dt>
- <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t required calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the c [...]
+ <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t require calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the co [...]
<dt>Remote state</dt>
<dd><p class="first">To query the full state of your application,
you must connect the various fragments of the state, including:</p>
<ul class="simple">
diff --git a/11/streams/developer-guide/interactive-queries.html
b/11/streams/developer-guide/interactive-queries.html
index 4675d8a..310dd6f 100644
--- a/11/streams/developer-guide/interactive-queries.html
+++ b/11/streams/developer-guide/interactive-queries.html
@@ -59,7 +59,7 @@
<p>There are local and remote components to interactively querying the
state of your application.</p>
<dl class="docutils">
<dt>Local state</dt>
- <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t required calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the c [...]
+ <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t require calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the co [...]
<dt>Remote state</dt>
<dd><p class="first">To query the full state of your application,
you must connect the various fragments of the state, including:</p>
<ul class="simple">
diff --git a/20/streams/developer-guide/interactive-queries.html
b/20/streams/developer-guide/interactive-queries.html
index 051f87c..6c553a7 100644
--- a/20/streams/developer-guide/interactive-queries.html
+++ b/20/streams/developer-guide/interactive-queries.html
@@ -59,7 +59,7 @@
<p>There are local and remote components to interactively querying the
state of your application.</p>
<dl class="docutils">
<dt>Local state</dt>
- <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t required calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the c [...]
+ <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t require calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the co [...]
<dt>Remote state</dt>
<dd><p class="first">To query the full state of your application,
you must connect the various fragments of the state, including:</p>
<ul class="simple">
diff --git a/21/streams/developer-guide/interactive-queries.html
b/21/streams/developer-guide/interactive-queries.html
index 8d8143f..e590a52 100644
--- a/21/streams/developer-guide/interactive-queries.html
+++ b/21/streams/developer-guide/interactive-queries.html
@@ -59,7 +59,7 @@
<p>There are local and remote components to interactively querying the
state of your application.</p>
<dl class="docutils">
<dt>Local state</dt>
- <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t required calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the c [...]
+ <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t require calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the co [...]
<dt>Remote state</dt>
<dd><p class="first">To query the full state of your application,
you must connect the various fragments of the state, including:</p>
<ul class="simple">
diff --git a/22/streams/developer-guide/interactive-queries.html
b/22/streams/developer-guide/interactive-queries.html
index 8d8143f..e590a52 100644
--- a/22/streams/developer-guide/interactive-queries.html
+++ b/22/streams/developer-guide/interactive-queries.html
@@ -59,7 +59,7 @@
<p>There are local and remote components to interactively querying the
state of your application.</p>
<dl class="docutils">
<dt>Local state</dt>
- <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t required calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the c [...]
+ <dd>An application instance can query the locally managed portion
of the state and directly query its own local state stores. You can use the
corresponding local data in other parts of your application code, as long as it
doesn’t require calling the Kafka Streams API. Querying state stores is
always read-only to guarantee that the underlying state stores will never be
mutated out-of-band (e.g., you cannot add new entries). State stores should
only be mutated by the co [...]
<dt>Remote state</dt>
<dd><p class="first">To query the full state of your application,
you must connect the various fragments of the state, including:</p>
<ul class="simple">
