This is an automated email from the ASF dual-hosted git repository.
shoothzj pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git
The following commit(s) were added to refs/heads/master by this push:
new 96c6dc0169 docs: add missing sentence beginning in protocol docs
(#4531)
96c6dc0169 is described below
commit 96c6dc01692208fcf1d4dfd8407b0407305e0144
Author: Philipp Dolif <[email protected]>
AuthorDate: Mon Dec 30 07:13:24 2024 +0100
docs: add missing sentence beginning in protocol docs (#4531)
---
site3/website/docs/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.10.0/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.11.1/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.12.1/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.13.0/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.14.8/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.15.5/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.16.6/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.17.1/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.5.1/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.6.2/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.7.3/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.8.2/development/protocol.md | 2 +-
site3/website/versioned_docs/version-4.9.2/development/protocol.md | 2 +-
14 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/site3/website/docs/development/protocol.md
b/site3/website/docs/development/protocol.md
index 327ec4c13a..4b9b0877b0 100644
--- a/site3/website/docs/development/protocol.md
+++ b/site3/website/docs/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.10.0/development/protocol.md
b/site3/website/versioned_docs/version-4.10.0/development/protocol.md
index b9d77f42b7..744783d679 100644
--- a/site3/website/versioned_docs/version-4.10.0/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.10.0/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.11.1/development/protocol.md
b/site3/website/versioned_docs/version-4.11.1/development/protocol.md
index 24e32cae4c..26fd9f4b60 100644
--- a/site3/website/versioned_docs/version-4.11.1/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.11.1/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.12.1/development/protocol.md
b/site3/website/versioned_docs/version-4.12.1/development/protocol.md
index fe25039acc..ad1d03ac2c 100644
--- a/site3/website/versioned_docs/version-4.12.1/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.12.1/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.13.0/development/protocol.md
b/site3/website/versioned_docs/version-4.13.0/development/protocol.md
index 327ec4c13a..4b9b0877b0 100644
--- a/site3/website/versioned_docs/version-4.13.0/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.13.0/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.14.8/development/protocol.md
b/site3/website/versioned_docs/version-4.14.8/development/protocol.md
index 327ec4c13a..4b9b0877b0 100644
--- a/site3/website/versioned_docs/version-4.14.8/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.14.8/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.15.5/development/protocol.md
b/site3/website/versioned_docs/version-4.15.5/development/protocol.md
index 327ec4c13a..4b9b0877b0 100644
--- a/site3/website/versioned_docs/version-4.15.5/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.15.5/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.16.6/development/protocol.md
b/site3/website/versioned_docs/version-4.16.6/development/protocol.md
index 327ec4c13a..4b9b0877b0 100644
--- a/site3/website/versioned_docs/version-4.16.6/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.16.6/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git
a/site3/website/versioned_docs/version-4.17.1/development/protocol.md
b/site3/website/versioned_docs/version-4.17.1/development/protocol.md
index 327ec4c13a..4b9b0877b0 100644
--- a/site3/website/versioned_docs/version-4.17.1/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.17.1/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git a/site3/website/versioned_docs/version-4.5.1/development/protocol.md
b/site3/website/versioned_docs/version-4.5.1/development/protocol.md
index fe25039acc..ad1d03ac2c 100644
--- a/site3/website/versioned_docs/version-4.5.1/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.5.1/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git a/site3/website/versioned_docs/version-4.6.2/development/protocol.md
b/site3/website/versioned_docs/version-4.6.2/development/protocol.md
index fe25039acc..ad1d03ac2c 100644
--- a/site3/website/versioned_docs/version-4.6.2/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.6.2/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git a/site3/website/versioned_docs/version-4.7.3/development/protocol.md
b/site3/website/versioned_docs/version-4.7.3/development/protocol.md
index fe25039acc..ad1d03ac2c 100644
--- a/site3/website/versioned_docs/version-4.7.3/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.7.3/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git a/site3/website/versioned_docs/version-4.8.2/development/protocol.md
b/site3/website/versioned_docs/version-4.8.2/development/protocol.md
index fe25039acc..ad1d03ac2c 100644
--- a/site3/website/versioned_docs/version-4.8.2/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.8.2/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
diff --git a/site3/website/versioned_docs/version-4.9.2/development/protocol.md
b/site3/website/versioned_docs/version-4.9.2/development/protocol.md
index 327ec4c13a..4b9b0877b0 100644
--- a/site3/website/versioned_docs/version-4.9.2/development/protocol.md
+++ b/site3/website/versioned_docs/version-4.9.2/development/protocol.md
@@ -82,7 +82,7 @@ Bookkeeper guarantees that:
## Writing to ledgers
-writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
+For a writer, ensuring that entry ids are sequential is trivial. A bookie
acknowledges a write once it has been persisted to disk and is therefore
durable. Once **Q<sub>a</sub>** bookies from the write quorum acknowledge the
write, the write is acknowledged to the client, but only if all entries with
lower entry ids in the ledger have already been acknowledged to the client.
The entry written contains the ledger id, the entry id, the last add confirmed
and the payload. The last add confirmed is the last entry which had been
acknowledged to the client when this entry was written. Sending this with the
entry speeds up recovery of the ledger in the case that the writer crashes.
