Correct typo in CASSANDRA-14092.txt

This commit is contained in:
Chen-Yuanmeng 2025-10-27 15:39:25 +08:00 committed by Patrick McFadin
parent 4f59364417
commit f402b5a895
1 changed files with 1 additions and 1 deletions

View File

@ -4,7 +4,7 @@ CASSANDRA-14092: MAXIMUM TTL EXPIRATION DATE
The maximum expiration timestamp that can be represented by the storage engine has been raised to The maximum expiration timestamp that can be represented by the storage engine has been raised to
2106-02-07T06:28:13+00:00 from the previous 2038-01-19T03:14:06+00:00, which means that INSERTS using 2106-02-07T06:28:13+00:00 from the previous 2038-01-19T03:14:06+00:00, which means that INSERTS using
TTL that would expire after this date are not currently supported. Notice that on previous versions <5.0 TTL that would expire after this date are not currently supported. Notice that on previous versions <5.0
or when 5.0 is ran in compatibility mode (<="oa" sstable formats) the limit stays at at 2038-01-19T03:14:06+00:00. or when 5.0 is run in compatibility mode (<="oa" sstable formats) the limit stays at 2038-01-19T03:14:06+00:00.
There is a new yaml property storage_compatibility_mode that determines the There is a new yaml property storage_compatibility_mode that determines the
Cassandra major version we want to stay compatible with. Its default is CASSANDRA_4, which means that Cassandra major version we want to stay compatible with. Its default is CASSANDRA_4, which means that