This is an automated email from the ASF dual-hosted git repository.
mimaison 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 b8c5173 MINOR: Remove redundant apostrophe in doc (#325)
b8c5173 is described below
commit b8c51735f122a494c9307d8a5a6e3739b709bc78
Author: Luke Chen <[email protected]>
AuthorDate: Thu Jan 28 20:56:57 2021 +0800
MINOR: Remove redundant apostrophe in doc (#325)
Reviewers: Mickael Maison <[email protected]>
---
0110/generated/consumer_config.html | 2 +-
10/generated/consumer_config.html | 2 +-
11/generated/consumer_config.html | 2 +-
20/generated/consumer_config.html | 2 +-
21/generated/consumer_config.html | 2 +-
22/generated/consumer_config.html | 2 +-
23/generated/consumer_config.html | 2 +-
24/generated/consumer_config.html | 2 +-
25/generated/consumer_config.html | 2 +-
26/generated/consumer_config.html | 2 +-
27/generated/consumer_config.html | 2 +-
11 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/0110/generated/consumer_config.html
b/0110/generated/consumer_config.html
index 6a7fa2a..3f30122 100644
--- a/0110/generated/consumer_config.html
+++ b/0110/generated/consumer_config.html
@@ -44,7 +44,7 @@
<tr>
<td>fetch.max.bytes</td><td>The maximum amount of data the server should
return for a fetch request. Records are fetched in batches by the consumer, and
if the first record batch in the first non-empty partition of the fetch is
larger than this value, the record batch will still be returned to ensure that
the consumer can make progress. As such, this is not a absolute maximum. The
maximum record batch size accepted by the broker is defined via
<code>message.max.bytes</code> (broker confi [...]
<tr>
-<td>isolation.level</td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset order. [...]
+<td>isolation.level</td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset order. H [...]
<tr>
<td>max.poll.interval.ms</td><td>The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member.
</td><td>int</td><td>300000</td><td>[1,...]</td><td>medium</td></tr>
<tr>
diff --git a/10/generated/consumer_config.html
b/10/generated/consumer_config.html
index b5b63f8..ab0b5c9 100644
--- a/10/generated/consumer_config.html
+++ b/10/generated/consumer_config.html
@@ -44,7 +44,7 @@
<tr>
<td>fetch.max.bytes</td><td>The maximum amount of data the server should
return for a fetch request. Records are fetched in batches by the consumer, and
if the first record batch in the first non-empty partition of the fetch is
larger than this value, the record batch will still be returned to ensure that
the consumer can make progress. As such, this is not a absolute maximum. The
maximum record batch size accepted by the broker is defined via
<code>message.max.bytes</code> (broker confi [...]
<tr>
-<td>isolation.level</td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset order. [...]
+<td>isolation.level</td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset order. H [...]
<tr>
<td>max.poll.interval.ms</td><td>The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member.
</td><td>int</td><td>300000</td><td>[1,...]</td><td>medium</td></tr>
<tr>
diff --git a/11/generated/consumer_config.html
b/11/generated/consumer_config.html
index 2336d8a..9048c54 100644
--- a/11/generated/consumer_config.html
+++ b/11/generated/consumer_config.html
@@ -44,7 +44,7 @@
<tr>
<td>fetch.max.bytes</td></td><td>The maximum amount of data the server should
return for a fetch request. Records are fetched in batches by the consumer, and
if the first record batch in the first non-empty partition of the fetch is
larger than this value, the record batch will still be returned to ensure that
the consumer can make progress. As such, this is not a absolute maximum. The
maximum record batch size accepted by the broker is defined via
<code>message.max.bytes</code> (broker [...]
<tr>
-<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset or [...]
+<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset ord [...]
<tr>
<td>max.poll.interval.ms</td></td><td>The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member.
</td></td><td>int</td></td><td>300000</td></td><td>[1,...]</td></td><td>mediu
[...]
<tr>
diff --git a/20/generated/consumer_config.html
b/20/generated/consumer_config.html
index 41e095a..b7b8de1 100644
--- a/20/generated/consumer_config.html
+++ b/20/generated/consumer_config.html
@@ -46,7 +46,7 @@
<tr>
<td>fetch.max.bytes</td></td><td>The maximum amount of data the server should
return for a fetch request. Records are fetched in batches by the consumer, and
if the first record batch in the first non-empty partition of the fetch is
larger than this value, the record batch will still be returned to ensure that
the consumer can make progress. As such, this is not a absolute maximum. The
maximum record batch size accepted by the broker is defined via
<code>message.max.bytes</code> (broker [...]
<tr>
-<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset or [...]
+<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset ord [...]
<tr>
<td>max.poll.interval.ms</td></td><td>The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member.
</td></td><td>int</td></td><td>300000</td></td><td>[1,...]</td></td><td>mediu
[...]
<tr>
diff --git a/21/generated/consumer_config.html
b/21/generated/consumer_config.html
index 64b3059..87af541 100644
--- a/21/generated/consumer_config.html
+++ b/21/generated/consumer_config.html
@@ -48,7 +48,7 @@
<tr>
<td>fetch.max.bytes</td></td><td>The maximum amount of data the server should
return for a fetch request. Records are fetched in batches by the consumer, and
if the first record batch in the first non-empty partition of the fetch is
larger than this value, the record batch will still be returned to ensure that
the consumer can make progress. As such, this is not a absolute maximum. The
maximum record batch size accepted by the broker is defined via
<code>message.max.bytes</code> (broker [...]
<tr>
-<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset or [...]
+<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset ord [...]
<tr>
<td>max.poll.interval.ms</td></td><td>The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member.
</td></td><td>int</td></td><td>300000</td></td><td>[1,...]</td></td><td>mediu
[...]
<tr>
diff --git a/22/generated/consumer_config.html
b/22/generated/consumer_config.html
index 2850678..c71b311 100644
--- a/22/generated/consumer_config.html
+++ b/22/generated/consumer_config.html
@@ -48,7 +48,7 @@
<tr>
<td>fetch.max.bytes</td></td><td>The maximum amount of data the server should
return for a fetch request. Records are fetched in batches by the consumer, and
if the first record batch in the first non-empty partition of the fetch is
larger than this value, the record batch will still be returned to ensure that
the consumer can make progress. As such, this is not a absolute maximum. The
maximum record batch size accepted by the broker is defined via
<code>message.max.bytes</code> (broker [...]
<tr>
-<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset or [...]
+<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset ord [...]
<tr>
<td>max.poll.interval.ms</td></td><td>The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member.
</td></td><td>int</td></td><td>300000</td></td><td>[1,...]</td></td><td>mediu
[...]
<tr>
diff --git a/23/generated/consumer_config.html
b/23/generated/consumer_config.html
index 0231356..4d23c47 100644
--- a/23/generated/consumer_config.html
+++ b/23/generated/consumer_config.html
@@ -52,7 +52,7 @@
<tr>
<td>group.instance.id</td></td><td>A unique identifier of the consumer
instance provided by end user. Only non-empty strings are permitted. If set,
the consumer is treated as a static member, which means that only one instance
with this ID is allowed in the consumer group at any time. This can be used in
combination with a larger session timeout to avoid group rebalances caused by
transient unavailability (e.g. process restarts). If not set, the consumer will
join the group as a dynamic [...]
<tr>
-<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset or [...]
+<td>isolation.level</td></td><td><p>Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.</p>
<p>Messages will always be returned in offset ord [...]
<tr>
<td>max.poll.interval.ms</td></td><td>The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member.
</td></td><td>int</td></td><td>300000</td></td><td>[1,...]</td></td><td>mediu
[...]
<tr>
diff --git a/24/generated/consumer_config.html
b/24/generated/consumer_config.html
index 7eda8be..79709ca 100644
--- a/24/generated/consumer_config.html
+++ b/24/generated/consumer_config.html
@@ -21,7 +21,7 @@
<li><b>exclude.internal.topics</b>: Whether internal topics matching a
subscribed pattern should be excluded from the subscription. It is always
possible to explicitly subscribe to an internal topic.<br/><ul
class="horizontal-list"><li><b>Type</b>: boolean</li><li><b>Default</b>:
true</li><li><b>Valid Values</b>: </li><li><b>Importance</b>:
medium</li></ul></li>
<li><b>fetch.max.bytes</b>: The maximum amount of data the server should
return for a fetch request. Records are fetched in batches by the consumer, and
if the first record batch in the first non-empty partition of the fetch is
larger than this value, the record batch will still be returned to ensure that
the consumer can make progress. As such, this is not a absolute maximum. The
maximum record batch size accepted by the broker is defined via
<code>message.max.bytes</code> (broker confi [...]
<li><b>group.instance.id</b>: A unique identifier of the consumer instance
provided by the end user. Only non-empty strings are permitted. If set, the
consumer is treated as a static member, which means that only one instance with
this ID is allowed in the consumer group at any time. This can be used in
combination with a larger session timeout to avoid group rebalances caused by
transient unavailability (e.g. process restarts). If not set, the consumer will
join the group as a dynamic m [...]
-<li><b>isolation.level</b>: Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code>' (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.
<p>Messages will always be returned in offset order. Hence, [...]
+<li><b>isolation.level</b>: Controls how to read messages written
transactionally. If set to <code>read_committed</code>, consumer.poll() will
only return transactional messages which have been committed. If set to
<code>read_uncommitted</code> (the default), consumer.poll() will return all
messages, even transactional messages which have been aborted.
Non-transactional messages will be returned unconditionally in either mode.
<p>Messages will always be returned in offset order. Hence, i [...]
<li><b>max.poll.interval.ms</b>: The maximum delay between invocations of
poll() when using consumer group management. This places an upper bound on the
amount of time that the consumer can be idle before fetching more records. If
poll() is not called before expiration of this timeout, then the consumer is
considered failed and the group will rebalance in order to reassign the
partitions to another member. For consumers using a non-null
<code>group.instance.id</code> which reach this tim [...]
<li><b>max.poll.records</b>: The maximum number of records returned in a
single call to poll().<br/><ul class="horizontal-list"><li><b>Type</b>:
int</li><li><b>Default</b>: 500</li><li><b>Valid Values</b>:
[1,...]</li><li><b>Importance</b>: medium</li></ul></li>
<li><b>partition.assignment.strategy</b>: A list of class names or class
types, ordered by preference, of supported assignors responsible for the
partition assignment strategy that the client will use to distribute partition
ownership amongst consumer instances when group management is used.
Implementing the
<code>org.apache.kafka.clients.consumer.ConsumerPartitionAssignor</code>
interface allows you to plug in a custom assignment strategy.<br/><ul
class="horizontal-list"><li><b>Type</b> [...]
diff --git a/25/generated/consumer_config.html
b/25/generated/consumer_config.html
index 0977ec7..e2c2fac 100644
--- a/25/generated/consumer_config.html
+++ b/25/generated/consumer_config.html
@@ -290,7 +290,7 @@
<a class="anchor-link" id="isolation.level"></a>
<a href="#isolation.level">isolation.level</a>
</h4>
-<p>Controls how to read messages written transactionally. If set to
<code>read_committed</code>, consumer.poll() will only return transactional
messages which have been committed. If set to <code>read_uncommitted</code>'
(the default), consumer.poll() will return all messages, even transactional
messages which have been aborted. Non-transactional messages will be returned
unconditionally in either mode. <p>Messages will always be returned in offset
order. Hence, in <code>read_committed< [...]
+<p>Controls how to read messages written transactionally. If set to
<code>read_committed</code>, consumer.poll() will only return transactional
messages which have been committed. If set to <code>read_uncommitted</code>
(the default), consumer.poll() will return all messages, even transactional
messages which have been aborted. Non-transactional messages will be returned
unconditionally in either mode. <p>Messages will always be returned in offset
order. Hence, in <code>read_committed</ [...]
<table class="data-table"><tbody>
<tr><th>Type:</th><td>string</td></tr>
<tr><th>Default:</th><td>read_uncommitted</td></tr>
diff --git a/26/generated/consumer_config.html
b/26/generated/consumer_config.html
index 2ef6030..91596f6 100644
--- a/26/generated/consumer_config.html
+++ b/26/generated/consumer_config.html
@@ -221,7 +221,7 @@
</li>
<li>
<h4><a id="isolation.level" href="#isolation.level">isolation.level</a></h4>
-<p>Controls how to read messages written transactionally. If set to
<code>read_committed</code>, consumer.poll() will only return transactional
messages which have been committed. If set to <code>read_uncommitted</code>'
(the default), consumer.poll() will return all messages, even transactional
messages which have been aborted. Non-transactional messages will be returned
unconditionally in either mode. <p>Messages will always be returned in offset
order. Hence, in <code>read_committed< [...]
+<p>Controls how to read messages written transactionally. If set to
<code>read_committed</code>, consumer.poll() will only return transactional
messages which have been committed. If set to <code>read_uncommitted</code>
(the default), consumer.poll() will return all messages, even transactional
messages which have been aborted. Non-transactional messages will be returned
unconditionally in either mode. <p>Messages will always be returned in offset
order. Hence, in <code>read_committed</ [...]
<table><tbody>
<tr><th>Type:</th><td>string</td></tr>
<tr><th>Default:</th><td>read_uncommitted</td></tr>
diff --git a/27/generated/consumer_config.html
b/27/generated/consumer_config.html
index 6217408..ec42949 100644
--- a/27/generated/consumer_config.html
+++ b/27/generated/consumer_config.html
@@ -251,7 +251,7 @@
</li>
<li>
<h4><a id="isolation.level"></a><a id="consumerconfigs_isolation.level"
href="#consumerconfigs_isolation.level">isolation.level</a></h4>
-<p>Controls how to read messages written transactionally. If set to
<code>read_committed</code>, consumer.poll() will only return transactional
messages which have been committed. If set to <code>read_uncommitted</code>'
(the default), consumer.poll() will return all messages, even transactional
messages which have been aborted. Non-transactional messages will be returned
unconditionally in either mode. <p>Messages will always be returned in offset
order. Hence, in <code>read_committed< [...]
+<p>Controls how to read messages written transactionally. If set to
<code>read_committed</code>, consumer.poll() will only return transactional
messages which have been committed. If set to <code>read_uncommitted</code>
(the default), consumer.poll() will return all messages, even transactional
messages which have been aborted. Non-transactional messages will be returned
unconditionally in either mode. <p>Messages will always be returned in offset
order. Hence, in <code>read_committed</ [...]
<table><tbody>
<tr><th>Type:</th><td>string</td></tr>
<tr><th>Default:</th><td>read_uncommitted</td></tr>
