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

Stefan Miklosovic edited comment on CASSANDRA-20827 at 8/15/25 8:08 AM:
------------------------------------------------------------------------

Well ... while it looks _strange,_ this is actually the correct way to display 
that. We have a column of type {_}text{_}, which accidentally contains a String 
which is a valid JSON. And we want to select _JSON representation_ of a value 
of a _text_ column. We do not know in advance if the value of a column of type 
_text_ is a valid JSON or not. So the current output makes sense, whatever 
strange it might look like.

We might contemplate about simplifying it like you suggested if {{value}} 
column {_}would be of type JSON{_}. But it is not. It is of type {{text.}}


was (Author: smiklosovic):
Well ... while it looks _strange,_ this is actually the correct way to display 
that. We have a column of type {_}text{_}, which accidentally contains a String 
which is a valid JSON. And we want to select _JSON representation_ of a value 
of a _text_ column. We do not know in advance if the value of a column of type 
_text_ is a valid JSON or not. So the current output makes sense, whatever 
strange it might look like.

We might contemplate about simplifying it like you suggested if {{value}} 
column {_}would be of type JSON{_}. But it is not. It is of type type {{text.}}

> 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

Reply via email to