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

xushiyan pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hudi.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 2967ddf6d23e chore: disable trailing slash and fix content (#17614)
2967ddf6d23e is described below

commit 2967ddf6d23eb25c0b8b28aeb9155a2fee826a2b
Author: Shiyan Xu <[email protected]>
AuthorDate: Tue Dec 16 20:16:53 2025 -0600

    chore: disable trailing slash and fix content (#17614)
---
 website/blog/2025-12-16-maximizing-throughput-nbcc.md | 4 ++--
 website/docusaurus.config.js                          | 1 +
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/website/blog/2025-12-16-maximizing-throughput-nbcc.md 
b/website/blog/2025-12-16-maximizing-throughput-nbcc.md
index 8ed3b5879874..29480c0b6455 100644
--- a/website/blog/2025-12-16-maximizing-throughput-nbcc.md
+++ b/website/blog/2025-12-16-maximizing-throughput-nbcc.md
@@ -31,7 +31,7 @@ NBCC avoids conflicts by design: let every writer append 
updates to Hudi’s log
 
 
![p2-nbcc-overview](/assets/images/blog/2025-12-16-maximizing-throughput-nbcc/p2-nbcc-overview.png)
 
-Both OCC and NBCC require locking—OCC during commit validation, NBCC during 
timestamp generation. The key difference is how long the lock is held, and what 
happens after. OCC holds the lock while validating: for concurrent commits, it 
compares the sets of written files to detect conflicts—so validation time grows 
with both transaction size and concurrent writer count. If validation detects a 
conflict, the losing writers discard their completed work and retry. NBCC's 
lock duration is a ne [...]
+Both OCC and NBCC require locking—OCC during commit validation, NBCC during 
timestamp generation. The key difference is how long the lock is held, and what 
happens after. OCC holds the lock while validating: for concurrent commits, it 
compares the sets of written files to detect conflicts—so validation time grows 
with both transaction size. If validation detects a conflict, the losing 
writers discard their completed work and retry. NBCC's lock duration is a 
negligible constant (a configu [...]
 
 |                | OCC                                             | NBCC      
                                  |
 
|:---------------|:------------------------------------------------|:--------------------------------------------|
@@ -39,7 +39,7 @@ Both OCC and NBCC require locking—OCC during commit 
validation, NBCC during ti
 | Lock duration  | Scales with the number of written files to validate | 
Constant (brief clock skew duration)        |
 | Resource waste | High                                            | Nearly 
none                                 |
 
-Hudi supports both OCC and NBCC for multi-writer scenarios. Hudi also offers 
[early conflict 
detection](https://hudi.apache.org/docs/concurrency_control/#early-conflict-detection)
 for OCC, which can reduce wasted work by failing faster. However, OCC's 
validation lock duration still exceeds NBCC's timestamp generation time, and 
retries still occur after conflicts are detected—both impacting overall write 
throughput.
+Hudi supports both OCC and NBCC for multi-writer scenarios. Hudi also offers 
[early conflict 
detection](https://hudi.apache.org/docs/concurrency_control#early-conflict-detection)
 for OCC, which can reduce wasted work by failing faster. However, OCC's 
validation lock duration still exceeds NBCC's timestamp generation time, and 
retries still occur after conflicts are detected—both impacting overall write 
throughput.
 
 ## How NBCC Works Under the Hood
 
diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js
index abce898dd34c..b07f7012620b 100644
--- a/website/docusaurus.config.js
+++ b/website/docusaurus.config.js
@@ -15,6 +15,7 @@ module.exports = {
     "Hudi brings transactions, record-level updates/deletes and change streams 
to data lakes!",
   url: "https://hudi.apache.org";,
   baseUrl: "/",
+  trailingSlash: false,
   onBrokenLinks: "throw",
   markdown: {
     hooks: {

Reply via email to