Knowledgebase: MarkLogic Server
JSON in versions 6, 7, and 8
11 February 2015 02:34 PM

Introduction

This article compares JSON support in MarkLogic Server versions 6, 7, and 8, and the upgrade path for JSON in the database.

How is native JSON different than the previous JSON support?

Previous versions of MarkLogic Server provided XQuery APIs that converted between JSON and XML. This translation is lossy in the general case meaning developers were forced to make compromises on either or both ends of the transformation. Even though the transformation was implemented in C++ it still added significant overhead to ingestion. All of these issues go away with JSON as a native document format. 

How do I upgrade my JSON façade data to native JSON?

For applications that use the previous JSON translation façade (for example: through the Java or REST Client APIs), MarkLogic 8 comes with sample migration scripts to convert JSON stored as XML into native JSON.

The migration script will upgrade a database’s content and configuration from the XML format that was used in MarkLogic 6 and 7 to represent data to native JSON, specifically converting documents in the http://marklogic.com/xdmp/json/basic namespace.
 
If you are using the MarkLogic 7 JSON support, you will also need to migrate your code to use the native JSON support. The resulting application code is expected to be more efficient, but it will require application developers to make minor code changes to your application.
 
See also:
 
Version 8 JSON incompatibilities
 
Documents Created as JSON With MarkLogic 7 REST API or MLCP Must Be Converted to Native JSON
(1 vote(s))
Helpful
Not helpful
Comments (0)