natas_hw
/
cassandra
mirror of https://github.com/apache/cassandra
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify CQL literal handling of JSON in CQL3 docs

This commit is contained in:
Tyler Hobbs 2015-07-09 11:54:11 -05:00
parent af1c65843e
commit 136ffeda73
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/cql3/CQL.textile
View File

@ -2000,7 +2000,9 @@ Any columns which are ommitted from the @JSON@ map will be defaulted to a @NULL@
h3(#jsonEncoding). JSON Encoding of Cassandra Data Types
Where possible, Cassandra will represent and accept data types in their native @JSON@ representation. Cassandra will also accept string representations matching the CQL literal format for all data types. The following table describes the encodings that Cassandra will accept in @INSERT JSON@ values (and @fromJson()@ arguments) as well as the format Cassandra will use when returning data for @SELECT JSON@ statements (and @fromJson()@):
Where possible, Cassandra will represent and accept data types in their native @JSON@ representation. Cassandra will also accept string representations matching the CQL literal format for all single-field types. For example, floats, ints, UUIDs, and dates can be represented by CQL literal strings. However, compound types, such as collections, tuples, and user-defined types must be represented by native @JSON@ collections (maps and lists) or a JSON-encoded string representation of the collection.
The following table describes the encodings that Cassandra will accept in @INSERT JSON@ values (and @fromJson()@ arguments) as well as the format Cassandra will use when returning data for @SELECT JSON@ statements (and @fromJson()@):
|_. type |_. formats accepted |_. return format |_. notes|
|@ascii@ |string |string |Uses JSON's @\u@ character escape|