[
https://issues.apache.org/jira/browse/CASSANDRA-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930948#comment-13930948
]
Aleksey Yeschenko commented on CASSANDRA-6833:
----------------------------------------------
bq. A timestamp is "just" a bigint by that reasoning. Should we not support
that extra layer of meaning either?
It's about messaging. Having a JSON type, even if it's really a blob with some
extra validation, sends a message that putting JSON blobs in cells if OK, where
in reality it's more often NOT OK. You might not see it that way, but users
will. We should not be encouraging it.
The risk of poisonous message vs. the extremely minor benefit of the type (blob
with validation) makes this issue a no-brainer won't fix, imo.
> 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)
