Powered by Zoomin Software. For more details please contactZoomin

Glossary

C

  • Last Updated: May 18, 2026
  • 7 minute read
    • MarkLogic Server
    • Version 12.0
    • Documentation

CA

See certificate authority.

cache

A memory-resident structure used to store frequently accessed data to improve performance during query execution.

cache partitions

MarkLogic. Along with setting each cache size, you can also set a cache partition count. Each cache defaults to one or two or sometimes four partitions, depending on your memory size. Increasing the count can improve cache concurrency at the cost of efficiency.

caching

MarkLogic. On database or group creation, MarkLogic assigns default cache sizes optimized for your hardware, using the assumption that the server will be acting as both E-node and D-node. You can improve performance in a clustered environment by optimizing each group's cache sizes. With an E-node group, you can increase the size of the caches related to request evaluation at the expense of those related to data management. For a D-node, you can do the opposite.

capabilities

MarkLogic. The permissions set on a document define access to capabilities for that document. Capabilities include read, insert, update, and execute. Each permission consists of a capability and a role. See permission.

CBD (Concise Bounded Definition)

Semantics. The Concise Bounded Definition (CBD) specification is used to describe one or more nodes in the RDF graph as a resource. This implementation does not provide any reified statements, and returns a maximum of 9999 triples. See sem:describe. For more about CBD in general, see the W3C specification: CBD - Concise Bounded Description.

CDH (Cloudera Distribution Hadoop)

Hadoop. Cloudera's Distribution Including Apache Hadoop, an open source data management platform based on Apache Hadoop.

CentOS

Linux. A community-supported, free and open source operating system based on Red Hat Enterprise Linux.

CEP

(Complex Event Processing)

MarkLogic. Complex event processing combines data from multiple sources in its tracking and analysis of streams of information about events, and uses that information to infer events or patterns that may suggest more complicated circumstances. The goal of complex event processing is to quickly identify and respond to meaningful events.

certificate authority (CA)

Security. A trusted third party that certifies the identity of entities, such as users, databases, administrators, clients, and servers. When an entity requests certification, the CA verifies its identity and grants a certificate, which is signed with the CA's private key. If the CA is trusted, then any certificate it issues is trusted unless it has been revoked.

certificate or public key certificate

Security. An electronic document that incorporates a digital signature to bind together a public key with identity information, such as the name of a person or an organization, address, and so on. The certificate can be used to verify that a public key belongs to an individual or organization.

certificate request

Security. A request data structure containing a subset of the information that will ultimately end up in the certificate. A certificate request is sent to a certificate authority for certification.

certificate signing request (CSR)

An encoded file containing website, service, organization, domain name, public key, and signature information sent to a certificate authority (CA), which creates an SSL or TLS certificate for the website. This certificate encrypts traffic to the website.

certificate template

Security. A MarkLogic construct that is used to generate certificate requests for the various hosts in a cluster. The template defines the name of the certificate, a description, and identity information about the owner of the certificate.

CF (Cloud Formation)

Cloud. The AWS Cloud Formation service for provisioning startup of AWS resources. For details, see Deploy MarkLogic on EC2 using CloudFormation in MarkLogic Server on Amazon Web Services (AWS) and AWS Cloud Formation. MarkLogic CloudFormation templates are available on MarkLogic on AWS.

cipher

Security. An algorithm for encrypting information so that it's only readable by someone with a key. A cipher can be either symmetric and asymmetric. Symmetric ciphers use the same key for both encryption and decryption. Asymmetric ciphers use a public and private key.

ciphersuite

Security (TLS 1.3). A set of cryptographic algorithms used to secure communication between a client and a server. [New in v12.0.0]

claim

Security. A piece of information asserted about a subject, often in the form of a key-value pair.

client

Client-server model software. The application that is requesting a resource from the resource server, often on the end user’s behalf.

CLOB (Character Large Object)

Database. Large text document.

Cloud Capable

Cloud. MarkLogic clusters can be deployed on Amazon Elastic Compute Cloud (EC2) as well as on Microsoft Azure Cloud. An EC2/Azure deployment of MarkLogic enables you to quickly get started with any sized cluster (or clusters) with a minimum upfront investment. You can then scale your clusters up or down, as your needs evolve.

cluster

MarkLogic. Multiple instances of MarkLogic Server configured to run as a cluster. The cluster has multiple machines (hosts), each running an instance of MarkLogic Server. Each host in a cluster is sometimes called a node.

cluster API token

A security credential used to authenticate and authorize certain MarkLogic Server operations within a MarkLogic Server cluster. The token ensures that only authorized users and applications can perform administrative tasks and access cluster resources. It is issued by a MarkLogic Server user with the corresponding privilege. A dynamic host token is an example of a cluster API token. [New in v12.0.0].

collection

MarkLogic. A collection is a group of documents that enable queries to efficiently target subsets of content within MarkLogic Server. Collections are described as part of the W3C XQuery specification, but their implementation is undefined. MarkLogic has chosen to emphasize collections as a powerful and high-performance mechanism for selecting sets of documents against which queries can be processed. See Collections in Develop Search Applications for more information about collections.

collection - protected

Database. Protected collections enable you to control who can add documents to a collection. A protected collection does not affect access to documents in the collection. Use document permissions to control document access. You can convert a protected collection to an unprotected collection, and vice versa.

collection - unprotected

Database. An unprotected collection is created implicitly when inserting or updating a document and specifying a collection URI that has not previously been used. An unprotected collection is not stored in the security database. You can convert a protected collection to an unprotected collection, and vice versa.

collection lexicon

MarkLogic. A lexicon that contains all the collection URIs in a database. See Browsing With Lexicons in Develop Search Applications.

column

MarkLogic. A SQL view has a name and a range index reference that identifies a particular document element or attribute. The range index for each column must be created before creating the view.

combined query

Search. A query format that enables you to combine different query types and a set of query options into a single bundle. A combined query can include any combination of a string, structured, or cts:query, a QBE, and query options. Combined query is only supported by the REST, Java, and Node.js Client APIs. See Specifying Dynamic Query Options with Combined Query in Develop Using the REST API, or the appropriate client application language developer’s guide.

commit

Database. To end a transaction and make the changes made by the transaction visible in the database. Single-statement transactions are automatically committed upon successful completion of the statement. Multi-statement transactions are explicitly committed, but the commit only occurs if and when the calling statement successfully completes.

communication between clusters

MarkLogic. Database replication uses inter-cluster communication. Communication between clusters uses the XDQP protocol. Before you can configure database replication, each cluster in the replication scheme must be aware of the configuration of the other clusters. This is accomplished by coupling the local cluster to the foreign cluster.

compartments

Security. Compartment security allows you to specify more complex security rules on documents. A compartment is a name associated with a role. You specify that a role is part of a compartment by adding the compartment name to each role in the compartment. When a role is compartmented, the compartment name is used as an additional check when determining a user's authority to access or create documents in a database.

configuration management

The MarkLogic Server Configuration Manager allows you to export and import the configuration settings for MarkLogic Server resources. A resource is a MarkLogic Server object, such as a database, forest, App Server, group or host.

constraint

MarkLogic. A constraint is a name/value pair used to filter search results. A constraint can be used in a search UI to create the facets as part of faceted navigation where every facet is a constraint on the search results. For a constraint to also function as a facet, you have to be able to retrieve all its values. If you search docs.marklogic.com for “xquery”, the results will break-down by category of documents that mention XQuery. The categories of documents are the constraints on the search results.

content source

MarkLogic. The database and App Server combination against which your query executes. Query Console automatically builds a list of available content sources for your MarkLogic Server and makes it available in the Content Source list.

coordinate system

Geospatial. A geospatial coordinate system is a set of mappings that map places on Earth to a set of numbers. The vertical axis is represented by a latitude coordinate, and the horizontal axis is represented by a longitude coordinate, and together they make up a coordinate system that is used to map places on the Earth. For more details, see Understanding Geodetic Coordinates in Develop Search Applications.

CPF (Content Processing Framework)

Content Processing Framework. The Content Processing Framework in MarkLogic Server supports multi-step processing as part of content processing applications. Each step in the process performs a particular task or set of tasks. Content processing is a way to programmatically add value to your content. See Overview of the Content Processing Framework in Content Processing Framework. See also pipeline, domain, and trigger.

Cross-Site Request Forgery (CSRF)

Security. A cyberattack that hijacks a user's existing authenticated session to bypass security checks and send commands to a trusted website, making it appear that it is the authorized user that is changing the password, transferring funds, purchasing expensive items, and so on.

CRUD (Create, Read, Update, and Delete)

Database. Defines the four basic attributes of persistent storage.

CSR

See Certificate Signing Request.

CSRF

See Cross-Site Request Forgery.

CTS (Core Text Services)

MarkLogic. Used in the core search functions.

curated data

MarkLogic. Data modeled, mapped, and displayed through the data curation process within the MarkLogic system.

CURIE (Compact URI Expression)

Semantics. A shortened version of a Uniform Resource Identifier (URI) signifying a specific resource.

TitleResults for “How to create a CRG?”Also Available inAlert