This is an automated email from the ASF dual-hosted git repository.
bbejeck 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 abb988c fix typo in processor-api developer guide docs (#239)
abb988c is described below
commit abb988cd5600637240bb91ecf74faf5a4660c2fa
Author: Michael Gyarmathy <[email protected]>
AuthorDate: Thu Nov 14 16:16:18 2019 -0600
fix typo in processor-api developer guide docs (#239)
Downstream patch of apache/kafka#7689, as requested by @bbejeck
Reviewers: Bill Bejeck <[email protected]>
---
10/streams/developer-guide/processor-api.html | 2 +-
11/streams/developer-guide/processor-api.html | 2 +-
20/streams/developer-guide/processor-api.html | 2 +-
21/streams/developer-guide/processor-api.html | 2 +-
22/streams/developer-guide/processor-api.html | 2 +-
23/streams/developer-guide/processor-api.html | 2 +-
24/streams/developer-guide/processor-api.html | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/10/streams/developer-guide/processor-api.html
b/10/streams/developer-guide/processor-api.html
index 1e1df65..ecc48e2 100644
--- a/10/streams/developer-guide/processor-api.html
+++ b/10/streams/developer-guide/processor-api.html
@@ -172,7 +172,7 @@
<a class="reference internal"
href="#streams-developer-guide-state-store-custom"><span class="std
std-ref">implement your own custom store type</span></a>.
It’s common practice to leverage an existing store
type via the <code class="docutils literal"><span
class="pre">Stores</span></code> factory.</p>
<p>Note that, when using Kafka Streams, you normally
don’t create or instantiate state stores directly in your code.
- Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This buildeer is used by
+ Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This builder is used by
Kafka Streams as a factory to instantiate the actual state
stores locally in application instances when and where
needed.</p>
<p>The following store types are available out of the box.</p>
diff --git a/11/streams/developer-guide/processor-api.html
b/11/streams/developer-guide/processor-api.html
index 1e1df65..ecc48e2 100644
--- a/11/streams/developer-guide/processor-api.html
+++ b/11/streams/developer-guide/processor-api.html
@@ -172,7 +172,7 @@
<a class="reference internal"
href="#streams-developer-guide-state-store-custom"><span class="std
std-ref">implement your own custom store type</span></a>.
It’s common practice to leverage an existing store
type via the <code class="docutils literal"><span
class="pre">Stores</span></code> factory.</p>
<p>Note that, when using Kafka Streams, you normally
don’t create or instantiate state stores directly in your code.
- Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This buildeer is used by
+ Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This builder is used by
Kafka Streams as a factory to instantiate the actual state
stores locally in application instances when and where
needed.</p>
<p>The following store types are available out of the box.</p>
diff --git a/20/streams/developer-guide/processor-api.html
b/20/streams/developer-guide/processor-api.html
index 22630b9..ffe07d5 100644
--- a/20/streams/developer-guide/processor-api.html
+++ b/20/streams/developer-guide/processor-api.html
@@ -195,7 +195,7 @@
<a class="reference internal"
href="#streams-developer-guide-state-store-custom"><span class="std
std-ref">implement your own custom store type</span></a>.
It’s common practice to leverage an existing store
type via the <code class="docutils literal"><span
class="pre">Stores</span></code> factory.</p>
<p>Note that, when using Kafka Streams, you normally
don’t create or instantiate state stores directly in your code.
- Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This buildeer is used by
+ Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This builder is used by
Kafka Streams as a factory to instantiate the actual state
stores locally in application instances when and where
needed.</p>
<p>The following store types are available out of the box.</p>
diff --git a/21/streams/developer-guide/processor-api.html
b/21/streams/developer-guide/processor-api.html
index 119c85a..2983180 100644
--- a/21/streams/developer-guide/processor-api.html
+++ b/21/streams/developer-guide/processor-api.html
@@ -195,7 +195,7 @@
<a class="reference internal"
href="#streams-developer-guide-state-store-custom"><span class="std
std-ref">implement your own custom store type</span></a>.
It’s common practice to leverage an existing store
type via the <code class="docutils literal"><span
class="pre">Stores</span></code> factory.</p>
<p>Note that, when using Kafka Streams, you normally
don’t create or instantiate state stores directly in your code.
- Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This buildeer is used by
+ Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This builder is used by
Kafka Streams as a factory to instantiate the actual state
stores locally in application instances when and where
needed.</p>
<p>The following store types are available out of the box.</p>
diff --git a/22/streams/developer-guide/processor-api.html
b/22/streams/developer-guide/processor-api.html
index 119c85a..2983180 100644
--- a/22/streams/developer-guide/processor-api.html
+++ b/22/streams/developer-guide/processor-api.html
@@ -195,7 +195,7 @@
<a class="reference internal"
href="#streams-developer-guide-state-store-custom"><span class="std
std-ref">implement your own custom store type</span></a>.
It’s common practice to leverage an existing store
type via the <code class="docutils literal"><span
class="pre">Stores</span></code> factory.</p>
<p>Note that, when using Kafka Streams, you normally
don’t create or instantiate state stores directly in your code.
- Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This buildeer is used by
+ Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This builder is used by
Kafka Streams as a factory to instantiate the actual state
stores locally in application instances when and where
needed.</p>
<p>The following store types are available out of the box.</p>
diff --git a/23/streams/developer-guide/processor-api.html
b/23/streams/developer-guide/processor-api.html
index 31c11ed..0f9359d 100644
--- a/23/streams/developer-guide/processor-api.html
+++ b/23/streams/developer-guide/processor-api.html
@@ -195,7 +195,7 @@
<a class="reference internal"
href="#streams-developer-guide-state-store-custom"><span class="std
std-ref">implement your own custom store type</span></a>.
It’s common practice to leverage an existing store
type via the <code class="docutils literal"><span
class="pre">Stores</span></code> factory.</p>
<p>Note that, when using Kafka Streams, you normally
don’t create or instantiate state stores directly in your code.
- Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This buildeer is used by
+ Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This builder is used by
Kafka Streams as a factory to instantiate the actual state
stores locally in application instances when and where
needed.</p>
<p>The following store types are available out of the box.</p>
diff --git a/24/streams/developer-guide/processor-api.html
b/24/streams/developer-guide/processor-api.html
index ae33ebb..3295116 100644
--- a/24/streams/developer-guide/processor-api.html
+++ b/24/streams/developer-guide/processor-api.html
@@ -195,7 +195,7 @@
<a class="reference internal"
href="#streams-developer-guide-state-store-custom"><span class="std
std-ref">implement your own custom store type</span></a>.
It’s common practice to leverage an existing store
type via the <code class="docutils literal"><span
class="pre">Stores</span></code> factory.</p>
<p>Note that, when using Kafka Streams, you normally
don’t create or instantiate state stores directly in your code.
- Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This buildeer is used by
+ Rather, you define state stores indirectly by creating a
so-called <code class="docutils literal"><span
class="pre">StoreBuilder</span></code>. This builder is used by
Kafka Streams as a factory to instantiate the actual state
stores locally in application instances when and where
needed.</p>
<p>The following store types are available out of the box.</p>
