You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by mj...@apache.org on 2019/04/13 22:39:19 UTC

[kafka] branch 1.1 updated: KAFKA-8213 - Fix typo in Streams Dev Guide (#6574)

This is an automated email from the ASF dual-hosted git repository.

mjsax pushed a commit to branch 1.1
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/1.1 by this push:
     new aa3b04c  KAFKA-8213 - Fix typo in Streams Dev Guide (#6574)
aa3b04c is described below

commit aa3b04c11e8dcd523d2d9bd10731fa0402ad24b4
Author: Victoria Bialas <lo...@users.noreply.github.com>
AuthorDate: Sat Apr 13 15:35:47 2019 -0700

    KAFKA-8213 - Fix typo in Streams Dev Guide (#6574)
    
    Reviewers: Jim Galasyn <ji...@confluent.io>, Joel Hamill <jo...@confluent.io>, Matthias J. Sax <ma...@confluent.io>
---
 docs/streams/developer-guide/interactive-queries.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/streams/developer-guide/interactive-queries.html b/docs/streams/developer-guide/interactive-queries.html
index 9b64ddb..6108887 100644
--- a/docs/streams/developer-guide/interactive-queries.html
+++ b/docs/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&#8217;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&#8217;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">