cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6833) Add json data type
Date Tue, 11 Mar 2014 23:51:45 GMT

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

Pavel Yaskevich commented on CASSANDRA-6833:
--------------------------------------------

+1 with [~iamaleksey], if users really want validation for JSON strings to be handled by Cassandra
they can just add JSONType to their project and use it (that's still supported). That way
at least it would be clear what it does, otherwise it would be the same as super columns,
I've seen couple of examples when people started prototyping with them and moved to production
unchanged just because it felt natural for the type of data that they were storing so no thought
was given to re-modeling until the every end before they hit the bottleneck.

> Add json data type
> ------------------
>
>                 Key: CASSANDRA-6833
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6833
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 2.0.7
>
>
> While recognizing that UDT (CASSANDRA-5590) is the Right Way to store hierarchical data
in C*, it can still be useful to store json blobs as text.  Adding a json type would allow
validating that data.  (And adding formatting support in cqlsh?)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message