This is an automated email from the ASF dual-hosted git repository.
mck 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 b072ce0a2 Update Apache-Cassandra-4.1-New-SSTable-Identifiers.adoc
b072ce0a2 is described below
commit b072ce0a2d50a6e4a443f98a80f98c4af953a123
Author: Tibor Répási <r...@users.noreply.github.com>
AuthorDate: Wed Dec 14 13:05:01 2022 +0100
Update Apache-Cassandra-4.1-New-SSTable-Identifiers.adoc
Parameter name was changed with CASSANDRA-17738
patch by Tibor Répási; reviewed by Mick Semb Wever for CASSANDRA-18117
---
.../ROOT/pages/blog/Apache-Cassandra-4.1-New-SSTable-Identifiers.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-New-SSTable-Identifiers.adoc
b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-New-SSTable-Identifiers.adoc
index ec9a57fea..669243922 100644
---
a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-New-SSTable-Identifiers.adoc
+++
b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-New-SSTable-Identifiers.adoc
@@ -132,8 +132,8 @@ From those names, we can see that the first component of
all the identifiers is
=== Migration
-The globally unique identifier feature is enabled by switching the
`enable_uuid_sstable_identifiers` flag to `true` in cassandra.yaml. It is
disabled by default because once a node starts with this feature enabled, each
newly stored SSTable will have an identifier created using the new mechanism.
As a result, this makes downgrading process more difficult because globally
unique identifiers are not readable by Apache Cassandra before 4.1.
Consequently, all the SSTable files would have to [...]
+The globally unique identifier feature is enabled by switching the
`uuid_sstable_identifiers_enabled` flag to `true` in cassandra.yaml. It is
disabled by default because once a node starts with this feature enabled, each
newly stored SSTable will have an identifier created using the new mechanism.
As a result, this makes downgrading process more difficult because globally
unique identifiers are not readable by Apache Cassandra before 4.1.
Consequently, all the SSTable files would have to [...]
Note that setting the flag to `true` does not make Cassandra immediately
rename the existing SSTables according to the new scheme. It only affects newly
stored SSTables. Existing SSTables are eventually removed during the regular
compaction process.
-Support for globally unique SSTable identifiers was implemented in
https://issues.apache.org/jira/browse/CASSANDRA-17048[CASSANDRA-17048^] and is
part of the Apache Cassandra 4.1 release. We expect it will eliminate some
problems with manual backups as each SSTable created, for any table, on any
node will have a globally unique identifier.
\ No newline at end of file
+Support for globally unique SSTable identifiers was implemented in
https://issues.apache.org/jira/browse/CASSANDRA-17048[CASSANDRA-17048^] and is
part of the Apache Cassandra 4.1 release. We expect it will eliminate some
problems with manual backups as each SSTable created, for any table, on any
node will have a globally unique identifier.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
