Solutions

Stay on top of everything MarkLogic

Be the first to know! News, product information, and events delivered straight to your inbox.

Sign Me Up

Learn

Stay on top of everything MarkLogic

Be the first to know! News, product information, and events delivered straight to your inbox.

Sign Me Up

Community

Stay on top of everything MarkLogic

Be the first to know! News, product information, and events delivered straight to your inbox.

Sign Me Up

Company

Stay on top of everything MarkLogic

Be the first to know! News, product information, and events delivered straight to your inbox.

Sign Me Up

 
Knowledgebase:
Temporal documents with other MarkLogic features
08 February 2015 08:27 PM

Introduction

Interoperation of Temporal support with other MarkLogic features.

Features that support Temporal collections

MarkLogic’s Temporal feature is built-in to the server and is supported by many of MarkLogic’s power features: Search API, Semantics, Tiered Storage, and Flexibile Replication. Temporal queries can be written in either JSON or XQuery.

Collections

How are collections used to implement Temporal documents?

Temporality is defined on a protected collection, known as a temporal collection. When a document is inserted into a temporal collection, a URI collection is created for that document. Additionally, the latest version of each document will reside in a latest collection.

Why are collections used to group all revisions of a particular document vs storing it in the properties?

This was done to avoid unnecessary fragmentation, enhance performance, and make best use of existing infrastructure.

Does the Temporal implementation use the collection lexicon or just collections?

It uses only collections. The collection lexicon can be turned on and utilized for applications.

Won’t Temporal collections also be in the collection lexicon if the lexicon is enabled?

Yes.

See alsoTemporal, URI, and Latest Collections.

Timezones

The Temporal axes are based on standard MarkLogic dateTime range indexes.

All timezone information is handled in the standard way, as for any other dateTime range index in MarkLogic.

DLS (Library Services API)

Temporal and DLS are aimed at solving different sorts of problems, so do not replace each other. They will coexist.

Tiered Storage

Temporal documents can be leveraged with our Tiered Storage capabilities.

The typical use case is where companies will need to store years of historical information for various purposes regulations.

Compliance. Either internal or external auditing can occur (up to seven years based on Dodd-Frank Legislation). This data can be deployed on commodity hardware at lower cost, and can be remounted when needed.

Analytics. Many years of historical information can be cheaply stored on commodity hardware to allow data scientists to perform analysis for future patterns and backtesting against previous assumptions.

JSON/JavaScript

Temporal documents work with XML/XQuery as well as JSON/JavaScript.

Java/search/REST/Node API

Temporal is supported by all of our existing server-side APIs.

MLCP

You can specify a Temporal collection with the –temporal_collection option in MLCP.

Normal document management APIs (xdmp:*)

By default this is not allowed and an error will be returned.  Normally the temporal:* API should be used.  However, for more information, see also Managing and Updating Temporal Documents.

Triples

MarkLogic supports non-managed triples in a Temporal document.

(0 vote(s))
Helpful
Not helpful

Comments (0)