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

Ekaterina Dimitrova commented on CASSANDRA-17778:
-------------------------------------------------

Committed, thanks!

To https://github.com/apache/cassandra.git

   590de42a06..43036ecadd  cassandra-4.1 -> cassandra-4.1

   3f2e8d1883..b70e14e2ac  trunk -> trunk

> WEBSITE - Add CASSANDRA-15234 config page to Docs nav menu
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-17778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17778
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation/Website
>            Reporter: Erick Ramirez
>            Assignee: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 4.1.x, 4.x
>
>
> There is no way to navigate to the new configuration page for CASSANDRA-15234 
> ([Liberating cassandra.yaml Parameters' Names from Their 
> Units|https://cassandra.apache.org/doc/trunk/cassandra/new/configuration.html])
>  because it is not referenced anywhere.
> Unless someone has bookmarked the page, there is no way to find it on the 
> site.
> Other doc changes expected:
>  * Add a small table with supported units per type as currently we list only 
> the duration's ones and min units for old parameters. We list the supported 
> units only in NEWS.txt.
>  * Add info about the RuntimeExceptions we introduced in CASSANDRA-17725 for 
> a few deprecated JMX getters.
>  * Add a note for Cassandra developers - "Please ensure that any JMX 
> setters/getters update the Config class properties and not some local copies. 
> Settings Virtual Table reports the configuration loaded at any time from the 
> Config class."



--
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