This is an automated email from the ASF dual-hosted git repository.
rxl pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 02d5eb3 Replace batchIndexAcknowledgeEnable to
acknowledgmentAtBatchIndexLevelEnabled (#10844)
02d5eb3 is described below
commit 02d5eb32fc2340e1d583923920f72b470f9f38dc
Author: xiaolong ran <[email protected]>
AuthorDate: Mon Jun 7 11:29:11 2021 +0800
Replace batchIndexAcknowledgeEnable to
acknowledgmentAtBatchIndexLevelEnabled (#10844)
Signed-off-by: xiaolongran <[email protected]>
Fixes #10821
### Motivation
As #10821 said, It seems that `batchIndexAcknowledgeEnable` and
`acknowledgmentAtBatchIndexLevelEnabled` are confused in the documentation.
### Modifications
Replace `batchIndexAcknowledgeEnable` to
`acknowledgmentAtBatchIndexLevelEnabled`
---
site2/docs/concepts-messaging.md | 2 +-
site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md | 2 +-
site2/website/versioned_docs/version-2.6.0/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.6.1/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.6.2/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.6.3/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.6.4/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.0/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.1/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.2/concepts-messaging.md | 2 +-
site2/website/versioned_docs/version-2.7.3/concepts-messaging.md | 2 +-
11 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/site2/docs/concepts-messaging.md b/site2/docs/concepts-messaging.md
index 32ea4f8..447a85e 100644
--- a/site2/docs/concepts-messaging.md
+++ b/site2/docs/concepts-messaging.md
@@ -91,7 +91,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
b/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
index c0d38ca..404123b 100644
--- a/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
+++ b/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
@@ -47,7 +47,7 @@ Previously, the broker only tracked the acknowledged state in
the batch message
This PIP adds support for acknowledging the local batch index of a batch. This
feature is not enabled by default. You can enable it in the `broker.conf` as
below.
```
-batchIndexAcknowledgeEnable=true
+acknowledgmentAtBatchIndexLevelEnabled=true
```
For more information about PIP-54, see
[here](https://github.com/apache/pulsar/wiki/PIP-54:-Support-acknowledgment-at-batch-index-level).
<br> For more information about implementation details, see
[PR-6052](https://github.com/apache/pulsar/pull/6052).
diff --git a/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
b/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
index e7aa3c5..6a6676d 100644
--- a/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.0/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all its messages are
acknowledged by th
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement may bring more
memory overheads. So, perform this operation with caution.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
may bring more memory overheads. So, perform this operation with caution.
## Consumers
diff --git a/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md
b/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md
index 41e91e2..fd41a08 100644
--- a/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.1/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md
b/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md
index 03b0757..1d3f470 100644
--- a/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.2/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md
b/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md
index 212b638..7052433 100644
--- a/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.3/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md
b/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md
index ad45b22..520ea2e 100644
--- a/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.6.4/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md
b/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md
index d4158c45..78c0f6f 100644
--- a/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.0/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md
b/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md
index b504cbc..8994644 100644
--- a/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.1/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md
b/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md
index f893e5f..97c19bb 100644
--- a/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.2/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
diff --git a/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md
b/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md
index 2b37ae1..03f3fbf 100644
--- a/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md
+++ b/site2/website/versioned_docs/version-2.7.3/concepts-messaging.md
@@ -58,7 +58,7 @@ In general, a batch is acknowledged when all of its messages
are acknowledged by
To avoid redelivering acknowledged messages in a batch to the consumer, Pulsar
introduces batch index acknowledgement since Pulsar 2.6.0. When batch index
acknowledgement is enabled, the consumer filters out the batch index that has
been acknowledged and sends the batch index acknowledgement request to the
broker. The broker maintains the batch index acknowledgement status and tracks
the acknowledgement status of each batch index to avoid dispatching
acknowledged messages to the consumer [...]
-By default, batch index acknowledgement is disabled
(`batchIndexAcknowledgeEnable=false`). You can enable batch index
acknowledgement by setting the `batchIndexAcknowledgeEnable` parameter to
`true` at the broker side. Enabling batch index acknowledgement results in more
memory overheads.
+By default, batch index acknowledgement is disabled
(`acknowledgmentAtBatchIndexLevelEnabled=false`). You can enable batch index
acknowledgement by setting the `acknowledgmentAtBatchIndexLevelEnabled`
parameter to `true` at the broker side. Enabling batch index acknowledgement
results in more memory overheads.
### Chunking
When you enable chunking, read the following instructions.
