Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
2.1.1
-
Security Level: Public
-
None
Description
Couchbase always performs a JSON validation check before storing data. For applications that are always expecting to work with JSON data, it would be nice to expose the results of the check to the client in some way (return value indicates non-valid JSON), or configure the server to act on the results of the check (refuse to store non-valid JSON and send back a failure).
The following MB came up in the search for previous tickets, and seems to contain some of the same spirit as this request, although it appears to have been assigned to UI and closed by fixing an issue where the UI would allow the construction and saving of invalid JSON. This issue is about changing Couchbase Server behavior.
[EDIT]
Note that in 3.0 we already check to see if a value is JSON and set the datatype field appropriately before we insert the item into the hashtable. What we don't do yet is to allow non-json values to be rejected during this check.