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

Jeremiah Jordan edited comment on CASSANDRA-17166 at 2/16/22, 7:29 PM:
-----------------------------------------------------------------------

This property support sounds great.  One nitpick, I would use something 
different than just: -Dcassandra.[Config name]. Maybe 
-Dcassandra.config.[Config Name] or -Dcassandra.settings.[Config Name] or 
-Dcassandraconfig.[Config Name].

Otherwise there could be confusion between config properties and non config 
properties.


was (Author: jjordan):
This property support sounds great.  One nitpick, I would use something 
different than just: -Dcassandra.[Config name]. Maybe 
-Dcassandra.config.[Config Name] or -Dcassandra.settings.[Config Name] or 
-Dcassandraconfig.[Config Name].

> Enhance SnakeYAML properties to be reusable outside of YAML parsing, support 
> camel case conversion to snake case, and add support to ignore properties
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17166
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17166
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Config
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 4.x
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> SnakeYaml is rather limited in the “object mapping” layer, which forces our 
> internal code to match specific patterns (all fields public and camel case); 
> we can remove this restriction by leveraging Jackson for property lookup, and 
> leaving the YAML handling to SnakeYAML



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to