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

michaelsembwever pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 72e8fc988 Fix the UCS glossary entry and remove datastax reference
72e8fc988 is described below

commit 72e8fc9883f5910ddfdbe3869316c9b81c0f136b
Author: [email protected] <[email protected]>
AuthorDate: Sat Oct 24 15:33:11 2026 +0530

    Fix the UCS glossary entry and remove datastax reference
---
 site-content/source/modules/ROOT/partials/normalization.adoc | 2 +-
 site-content/source/modules/ROOT/partials/ucs.adoc           | 8 +-------
 2 files changed, 2 insertions(+), 8 deletions(-)

diff --git a/site-content/source/modules/ROOT/partials/normalization.adoc 
b/site-content/source/modules/ROOT/partials/normalization.adoc
index fa1f9a8c0..0d644e25a 100644
--- a/site-content/source/modules/ROOT/partials/normalization.adoc
+++ b/site-content/source/modules/ROOT/partials/normalization.adoc
@@ -1,4 +1,4 @@
 = normalization
 
 Normalization refers to a series of steps used to eliminate redundancy and 
reduce the chances of data inconsistency in a database's schema.
-In DataStax Enterprise, this process is inefficient because joining data in 
multiple tables for queries requires accessing more nodes.
+In Apache Cassandra, joining data from multiple tables can require reading 
from more than one node
diff --git a/site-content/source/modules/ROOT/partials/ucs.adoc 
b/site-content/source/modules/ROOT/partials/ucs.adoc
index abccae051..b8a2425bf 100644
--- a/site-content/source/modules/ROOT/partials/ucs.adoc
+++ b/site-content/source/modules/ROOT/partials/ucs.adoc
@@ -1,11 +1,5 @@
 = UnifiedCompactionStrategy (UCS)
 
-This compaction strategy compacts SSTables based on a series of time windows.
-During the current time window, the SSTables are compacted into one or more 
SSTables.
-At the end of the current time window, all SSTables are compacted into a 
single larger SSTable.
-The compaction process repeats at the start of the next time window.
-Each TWCS time window contains data within a specified range and contains 
varying amounts of data.
-
-Covers the applications of levelled, tiered and time-windowed compaction 
strategies, including combinations of levelled and tiered in different levels 
of the compaction hierarchy.
+This compaction strategy covers the applications of levelled, tiered and 
time-windowed compaction strategies, including combinations of levelled and 
tiered in different levels of the compaction hierarchy.
 This compaction can work in modes similar to <<STCS>> (with w = T4 matching 
STCS's default threshold of 4), LCS (with w = L10 to match LCS's default fan 
factor of 10), and can also work well enough for time-series workloads when 
used with a large tiered fan factor (e.g. w = T20). 
 Read-heavy workloads, especially ones that cannot benefit from bloom filters 
or time order (i.e. wide partition non-time-series) are best served by levelled 
configurations. Write-heavy, time series or key-value workloads are best served 
by tiered ones.
\ No newline at end of file


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to