[ 
https://issues.apache.org/jira/browse/CASSANDRA-19767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865262#comment-17865262
 ] 

Jackson Fleming edited comment on CASSANDRA-19767 at 7/12/24 5:51 AM:
----------------------------------------------------------------------

PRs

Trunk - [https://github.com/apache/cassandra/pull/3417]

5.0 - [https://github.com/apache/cassandra/pull/3418]

4.1 - TBC


was (Author: JIRAUSER294685):
PRs

Trunk - [https://github.com/apache/cassandra/pull/3417]

5.0 - https://github.com/apache/cassandra/pull/3418

> Fix storage_compatibility_mode documentation
> --------------------------------------------
>
>                 Key: CASSANDRA-19767
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19767
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Jackson Fleming
>            Assignee: Jackson Fleming
>            Priority: Normal
>         Attachments: image-2024-07-12-09-38-16-284.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The documentation for storage_compatibility_mode 
> ([https://cassandra.apache.org/doc/latest/cassandra/managing/configuration/cass_yaml_file.html#storage_compatibility_mode])
>  is very difficult to read. The below highlighted text seems incorrect.
> !image-2024-07-12-09-38-16-284.png|width=505,height=487!
>  
> It appears that the entry for the YAML option above it is causing entries to 
> get clobbered together (startup_checks)
>  
> This is actually a very useful and important feature for people upgrading to 
> Cassandra 5 to understand how to use properly - It would be good for it to be 
> easier to read, we should be encouraging use of the safest possible upgrade 
> path, which from my understanding would be:
> {{CASSANDRA_4 -> UPGRADING -> NONE}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to