[jira] [Commented] (CASSANDRA-18819) Re-organize ordering of configuration properties in cassandra.yaml

["Michael Semb Wever (Jira)" <ji...@apache.org>]

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

Michael Semb Wever commented on CASSANDRA-18819:
------------------------------------------------

I think sometimes properties are intentionally hidden from cassandra.yaml , but I don't know if that now/still applies to those two.

This feels like a duplicate of (or it will be superseded by) CASSANDRA-17292.

> Re-organize ordering of configuration properties in cassandra.yaml
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-18819
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18819
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Stefan Miklosovic
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 5.x
>
>
> I was setting up a cluster from scratch and I was configuring cassandra.yaml, obviously. What I do not like about the current content of cassandra.yaml is that some of its sections are seemingly scattered across that file and if feels like out of place / order.
> For example, if one wants to configure encryption it is on line 1458 and 1516 respectively. Snitch is on line 1402. The whole file has 2100 lines. So in order to configure a snitch, which is very common scenario when setting up a node, if I do not know that the field I am going to edit is called "endpoint_snitch" so I can just jump to it, I need to scroll to the three quarters of the file to edit it.
> I think that the most commonly edited sections of the configuration file should be on the very top or somewhere around it so as I am editing that file from scratch I just go section by section and I do not jump around, I just edit that or I skip it and I configure what is next - ordered by the probability that a section is going to be configured differently from a default.
> I also noticed that these properties are missing in cassandra.yaml, we can add it there upon refactorisation of this.
> memtable conf
> dynamic_snitch



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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org