[
https://issues.apache.org/jira/browse/CASSANDRA-20827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014063#comment-18014063
]
guo Maxwell edited comment on CASSANDRA-20827 at 8/15/25 8:03 AM:
------------------------------------------------------------------
{quote}
By the way, maybe as an interesting consequence of putting JSONs there, is that
it will look like this on select json
cassandra@cqlsh> select json * from system_views.settings where name =
'seed_provider.parameters';
[json]
---------------------------------------------------------------------------------
{"name": "seed_provider.parameters", "value": "{\"seeds\":\"127.0.0.1:7000\"}"}
(1 rows)
{quote}
This may be the point , if not json specified, then use the old output format
no compatibility issues, and is keyword json is used, then we can get what we
need.
But this naming " json " may need to be reconsidered
was (Author: maxwellguo):
{quote}
By the way, maybe as an interesting consequence of putting JSONs there, is that
it will look like this on select json
cassandra@cqlsh> select json * from system_views.settings where name =
'seed_provider.parameters';
[json]
---------------------------------------------------------------------------------
{"name": "seed_provider.parameters", "value": "{\"seeds\":\"127.0.0.1:7000\"}"}
(1 rows)
{quote}
This may be the point , if not json specified, then use the old output format
no compatibility issues, and is keyword json is used, then we can get what we
need.
> Represent complex settings as JSON on system_views.settings table
> -----------------------------------------------------------------
>
> Key: CASSANDRA-20827
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20827
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Paulo Motta
> Assignee: Marko Tsymbaliuk
> Priority: Normal
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Complex configuration (maps/sets/lists) are represented as
> Collections.toString() on {{system.settings}} virtual table:
> {code:java}
> cqlsh> select * from system_views.settings where name='seed_provider' ;
> name | value
> ------+-------
> (0 rows)
> cqlsh> select * from system_views.settings where
> name='seed_provider.parameters' ;
> name | value
> --------------------------+------------------------
> seed_provider.parameters | {seeds=127.0.0.1:7000}
> {code}
> While this is fine for human consumption, it's not ideal for programmatic
> access, since it requires custom parsing.
> This ticket is to add ability of representing complex types as JSON on
> {{system.settings}} and potentially making it default in trunk, so the above
> would return:
> {code:java}
> cqlsh> select * from system_views.settings where name='seed_provider' ;
> name | value
> ------+-------
> (0 rows)
> cqlsh> select * from system_views.settings where
> name='seed_provider.parameters' ;
> name | value
> --------------------------+------------------------
> seed_provider.parameters | {"seeds": "127.0.0.1:7000"}{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
