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 4f33a68ec434 chore(site): fix trailing slash setting (#17616)
4f33a68ec434 is described below
commit 4f33a68ec4341b41fdbaa393830847bba14ef48e
Author: Shiyan Xu <[email protected]>
AuthorDate: Tue Dec 16 20:36:21 2025 -0600
chore(site): fix trailing slash setting (#17616)
---
website/docs/concurrency_control.md | 4 ++--
website/docusaurus.config.js | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/website/docs/concurrency_control.md
b/website/docs/concurrency_control.md
index 541ae2d535c0..30a48c137a30 100644
--- a/website/docs/concurrency_control.md
+++ b/website/docs/concurrency_control.md
@@ -244,7 +244,7 @@ The `NON_BLOCKING_CONCURRENCY_CONTROL` offers the same set
of guarantees as ment
explicit locks for serializing the writes. Lock is only needed for writing the
commit metadata to the Hudi timeline. The
completion time for the commits reflects the serialization order and file
slicing is done based on completion time.
Multiple writers can operate on the table with non-blocking conflict
resolution. The writers can write into the same
-file group with the conflicts resolved automatically by the query reader and
the compactor. It works for compaction and ingestion, and we can see an example
of that with [Flink
writers](sql_dml#non-blocking-concurrency-control-experimental).
+file group with the conflicts resolved automatically by the query reader and
the compactor. It works for compaction and ingestion, and we can see an example
of that with [Flink
writers](../sql_dml#non-blocking-concurrency-control-experimental).
:::note
`NON_BLOCKING_CONCURRENCY_CONTROL` between ingestion writer and table service
writer is not yet supported for clustering. Please use
`OPTIMISTIC_CONCURRENCY_CONTROL` for clustering.
@@ -256,7 +256,7 @@ Multi writing using OCC allows multiple writers to
concurrently write and atomic
To improve the concurrency control, the [0.13.0
release](https://hudi.apache.org/releases/release-0.13.0#early-conflict-detection-for-multi-writer)
introduced a new feature, early conflict detection in OCC, to detect the
conflict during the data writing phase and abort the writing early on once a
conflict is detected, using Hudi's marker mechanism. Hudi can now stop a
conflicting writer much earlier because of the early conflict detection and
release computing resources necessary to clus [...]
-By default, this feature is turned off. To try this out, a user needs to set
`hoodie.write.concurrency.early.conflict.detection.enable` to true, when using
OCC for concurrency control (Refer
[configs](https://hudi.apache.org/docs/next/configurations#Write-Configurations-advanced-configs)
page for all relevant configs).
+By default, this feature is turned off. To try this out, a user needs to set
`hoodie.write.concurrency.early.conflict.detection.enable` to true, when using
OCC for concurrency control (Refer
[configs](configurations#Write-Configurations-advanced-configs) page for all
relevant configs).
:::note
Early conflict Detection in OCC is an **EXPERIMENTAL** feature
:::
diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js
index b07f7012620b..a0fcef3824e0 100644
--- a/website/docusaurus.config.js
+++ b/website/docusaurus.config.js
@@ -15,7 +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,
+ trailingSlash: true,
onBrokenLinks: "throw",
markdown: {
hooks: {
