[
https://issues.apache.org/jira/browse/CASSANDRA-17166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493468#comment-17493468
]
David Capwell commented on CASSANDRA-17166:
-------------------------------------------
bq. 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].
Good point, ill poke others to see how they feel. I prefer -Dcassandra.[Config
name] but totally understand your point, and we currently do
-Dcassandra.[Config name] for non-config settings, so could cause an overlap
(not checked)
> 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]
