[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--------------------------------------
Description:
This ticket is to capture the work associated with fixing broken links on the
blog [Apache Cassandra 4.1: Configuration
Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
{quote}
For a full list of affected parameters, mapping of old to new names and
supported units and how things work in general, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
{quote}
h3. Backward Compatibility
We support backward compatibility. All properties which have changed names can
still be set with the old name. Wherever the value format was also changed from
numeric value to number + unit value, you can still use the old name + the old
numeric value format. For a full list of parameter changes/mapping of old to
new parameters and what to expect, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
The correct page to link is
https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
was:
This ticket is to capture the work associated with fixing broken links on the
blog [Apache Cassandra 4.1: Configuration
Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
{quote}
For a full list of affected parameters, mapping of old to new names and
supported units and how things work in general, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
{quote}
h3. Backward Compatibility
We support backward compatibility. All properties which have changed names can
still be set with the old name. Wherever the value format was also changed from
numeric value to number + unit value, you can still use the old name + the old
numeric value format. For a full list of parameter changes/mapping of old to
new parameters and what to expect, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
> Reporter: Diogenese Topper
> Assignee: Erick Ramirez
> Priority: Normal
> Labels: pull-request-available
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
