M

Manage App Server

MarkLogic. The App Server on the Monitor Host that is configured to handle monitor requests. The Manage App Server is bound to port 8002 and is the App Server used by the Monitoring Dashboard.

managed clusters

MarkLogic. A MarkLogic feature that works with AWS features to automatically create and provision the necessary AWS resources and provide MarkLogic with the information needed to manage your cluster. For details see The Managed Cluster feature in MarkLogic Server on Amazon Web Services (AWS).

managed triples

MarkLogic. Triples with a document root of sem:triples are “managed triples” in MarkLogic. Conceptually, managed triples are triples that are not embedded in any document. When you load and query triples as you would with a triple store - without reference to a document - you are generally working with managed triples. These triples can be updated using SPARQL Update. See unmanaged triples and triple.

map task

Hadoop. A task which contributes to the map step of a job. A map task transforms the data in an input split into a set of output key-value pairs which can be further processed by a reduce task. A map task has no dependence on or awareness of other map tasks in the same job, so all the map tasks can run in parallel.

mapper

Hadoop. Programmatically, a subclass of org.apache.hadoop.mapreduce.Mapper. The mapper transforms map input key-value pairs into map output key-value pairs that can be consumed by reduce tasks. An input pair can map to zero, one, or many output pairs.

MarketPlace

Cloud. The Amazon Web Services (AWS) service for publishing pay-per-use and free (no extra charge) public AMI's on amazon. For details, see The Amazon Marketplace.

marklogic.conf file

A file in the /etc directory of a machine with MarkLogic Server installed to which configuration items are added to customize a MarkLogic Server instance.

MarkLogic Content Pump (mlcp)

MarkLogic. A command line tool for getting data into and out of a MarkLogic Server database.

MarkLogic Data Hub

See Data Hub (DH).

MarkLogic Data Hub Service

MarkLogic Data Hub Service is a fully automated cloud service to integrate data from silos. Based on the MarkLogic Data Hub, the service enables agile teams to immediately start integrating and curating data for both operational and analytical use. Delivered as a cloud service, it provides on-demand capacity, auto-scaling, automated database operations, and proven enterprise data security. Unlike other cloud services, however, it’s cost-effective and predictable even as enterprise workloads fluctuate

MARKLOGIC_DYNAMIC_HOST_TOKEN

The variable within a dynamic host's marklogic.conf file that holds the dynamic host token. [New in v12.0.0]

MarkLogic JavaScript API (MLJS)

MarkLogic. A client-side API for using JavaScript with MarkLogic Server.

MarkLogic Server

MarkLogic. An enterprise grade, scaleable operational database management system designed from the ground up to make massive quantities of heterogenous data easily accessible through search. MarkLogic Server runs on commodity hardware, supports ACID transactions, semantics, and Java, JavaScript, XQuery, and REST APIs. See Overview of MarkLogic Server in Understand MarkLogic Concepts.

Master

Flexible Replication. The repository that gets updated by the applications. The master, in turn, replicates the updates to other repositories, each known as a Replica.

Master Cluster

MarkLogic. The cluster on which the replicated documents are updated by the applications; shorthand for the cluster that hosts a Master Database.

Master Copy

MarkLogic. The content being replicated. For any piece of replicated content there is a Master and at least one copy.

Master Database

MarkLogic. The database being replicated. In any database replication scheme there is a Master Database and at least one Replica Database.

Master Forest

MarkLogic. The forest being replicated. In any database replication scheme there is a Master Forest and at least one Replica Forest.

Metadata Database

MarkLogic. The database that stores and indexes all of the configuration data required to manage a cluster of one or more MarkLogic Servers. For Amazon Web Services (AWS), the SimpleDB service is used to implement the Metadata Database. For details, see Welcome to Amazon SimpleDB.

MIME type

Web. (Multipurpose Internet Mail Extension) A MIME type is a standard identifier used by email clients, web browsers, search engines, and other protocols to indicate the type of data that a file contains. In an HTTP request, a MIME type is referred to as Content-type. Due to their expanded use by other media, MIME types are referred to as Internet Media types.

mlcp

MarkLogic. See MarkLogic Content Pump.

MLJS

MarkLogic. See MarkLogic JavaScript API.

model

A model includes entity type definitions, entity property definitions, relationships between entity types, and facts about the model (as semantic triples). A model descriptor contributes the entity type and entity property definitions, and relationships between entities. MarkLogic generates a default set of facts from the descriptor, and you can add additional facts to the model. For details, see the Model Introduction in Understand Entity Services.

model descriptor

A definition of a set of entity types, their properties, and relationships. You use a descriptor to create a model and model-based application code and configuration artifacts. See also Entity Services, entity type, entity property, and entity relationship. For more details, see Model Descriptor Basics in Understand Entity Services.

module

MarkLogic. There are two types of modules in MarkLogic; main modules and library modules. A main module can be executed as an XQuery or JavaScript program, and must include a query body consisting of an XQuery or JavaScript expression (which in turn can contain other expressions, and so on). A library module has a namespace and is used to define functions. Library modules cannot be evaluated directly; they are imported, either from other library modules or from main modules with an import statement. See built-in.

Monitor Application

MarkLogic. This can be any application that requests and makes use of monitoring data, such as a Web browser, a plugin for an existing monitoring tool, or the Monitoring Dashboard described in Use the MarkLogic Server Monitoring Dashboard in Monitor MarkLogic Server.

Monitor Content

MarkLogic. The Extensible Markup Language (XML), Hypertext Markup Language (HTML), or JavaScript Object Notation (JSON) structure that represents the data returned by the Management API.

Monitor Host

MarkLogic. The host in a MarkLogic Server cluster that uses the Monitor API to respond to requests for monitoring content from the monitor application and returns monitoring information for objects in the cluster.

Monitoring Sample

MarkLogic. A bit of information captured during a refresh interval on a graph. For example, one of the candlesticks captured in the Query Execution graph is a single sample.

Monitoring Session

MarkLogic. The timeframe since the dashboard page was last refreshed. For example, if you navigate from the Query Execution page to the Rates and Loads page, you have ended the Query Execution session and started the Rates and Loads session.

multi-model database

MarkLogic. A multi-model database is designed to support multiple data models in their natural form against a single, integrated backend, and allow data access with a single API to query all the data in their native query language regardless of the data model. Document, graph, relational, and key-value models are examples of data models that may be supported by a multi-model database.

multi-statement transaction

Database. A transaction created in query or update transaction mode, consisting of one or more statements which commit or rollback together. Changes made by one statement in the transaction are visible to subsequent statements in the same transaction prior to commit. Multi-statement transactions must be explicitly committed by calling xdmp:commit.

multi-tenancy

Cloud. A mode of software operation where multiple independent instances of one or multiple applications operate in a shared environment. The instances (tenants) are logically isolated, but physically integrated. Multi-tenancy is an important feature of cloud computing.

Multi Version Concurrency Control (MVCC)

Database. A concurrency control method commonly used by database management systems to provide concurrent access to the database, and used in programming languages to implement transactional memory.

MVCC

Database. See Multi Version Concurrency Control.