L

lag limit

Database. A value that specifies the amount of time (in seconds) in which frames being written to the forest’s journal can differ from the frames being streamed to the backup journal. For example, if the lag limit is set to 30 seconds, the archived journal can lag behind a maximum of 30 seconds worth of transactions compared to the active journal. If the lag limit is exceeded, transactions are halted until the backup journal has caught up. The decision to set your lag limit time is determined by your Recovery Point Objective (RPO).

large binary document

MarkLogic. A binary document whose contents are managed by MarkLogic Server and whose size exceeds the large size threshold. For details, see Choosing a Binary Format in Load Content into MarkLogic Server.

Large Data Directory

MarkLogic. The per-forest area where the contents of large binary documents are stored.

large size threshold

MarkLogic. A database configuration setting defining the upper bound on the size of small binary documents. Binary documents larger than the threshold are automatically classified as large binary documents.

Last Stable Query Time (LSQT)

Bitemporal. An internal database timestamp used to track a point in time. A document with system start time before the LSQT point can be queried but not updated or ingested, and a document after this point can be updated/ingested but not queried. See bitemporal and temporal.

LDAP

Security. See Lightweight Directory Access Protocol.

lexicon

MarkLogic. A list of unique words or values, either throughout an entire database or within named elements, attributes, or fields. You can also define lexicons that allow quick access to the document and collection URIs in the database. Lexicons are usually backed by a range index. For more information see Querying Lexicons and Range Indexes and Range Indexes and Lexicons, also Browsing With Lexicons in Develop Search Applications.

Lightweight Directory Access Protocol (LDAP)

Security. An authentication protocol for accessing server resources over an internet or intranet network. An LDAP server provides a centralized user database where one password can be used to authenticate a user for access to multiple servers in the network. LDAP is supported on Active Directory on Windows Server 2008 and OpenLDAP 2.4 on Linux and other Unix platforms. See External Authentication (LDAP and Kerboros) in Understand MarkLogic Concepts.

linked data

Semantics. Linked data describes a method of sharing and querying data on the Web, building on Web technologies such as Hypertext Transfer Protocol (HTTP), Resource Description Framework Schema (RDFS) and Internationalized Resource Identifier (IRI)s, to share information in a way that can be read automatically by computers. Linked data is a term coined by Tim Berners-Lee for a web of data that can be processed by machines. See Linked Open Data and semantic web technologies. See also LinkedData.

Linked Open Data

Semantics. Linked Open Data refers to linked data freely available on the Web like DBPedia. This data can be accessed via REST, a SPARQL endpoint, or downloaded for local use in different formats.

load balancer

A load balancer usually spreads incoming requests across the E-nodes. An E-node processes the request and delegates out to the D-nodes for any subexpression of the request involving data retrieval or storage.

local reference

In a model descriptor, a reference to an entity type that can be fully resolved within that descriptor. For example, if a model defines Race and Runner entity types, and a Race entity type has a property that is an array of references to Runners, then those references are local references. See also external reference. For details, see Generating Test Entity Instances in Understand Entity Services.

Locking

Database. An update request must use read/write locks to maintain system integrity while making changes. This lock behavior is implicit and not under the control of the user. Read-locks block for write-locks and write-locks block for both read- and write-locks. An update has to obtain a read-lock before reading a document and a write-lock before changing (adding, deleting, modifying) a document. Lock acquisition is ordered, first-come first-served, and locks are released automatically at the end of the update request

Local Cluster

MarkLogic. The cluster of MarkLogic Server hosts at your current location. See cluster.

LSQT

Bitemporal. See Last Stable Query Time.