T

task

Hadoop. An independent subcomponent of a job, performing either map or reduce processing. A task processes a subset of data on a single node of a Hadoop cluster.

task server

MarkLogic. The Task Server is an App Server that is used to process requests that have been spawned. Spawned requests can originate from the xdmp:spawn command or from a post-commit trigger action (for example, as the result of a document running through a pipeline in the Content Processing Framework).

TDE template

A Template Driven Extraction (TDE) template. Use Entity Services to generate a template that enables querying your entity instance data as rows or semantic triples. See also template driven extraction (TDE) and triple. For details, see Generating A TDE Template in Understand Entity Services.

telemetry

MarkLogic telemetry provides faster, more complete communication with MarkLogic Support to facilitate the resolution of issues. When telemetry is enabled, it collects, encrypts, and sends diagnostic and anonymized system-level information about a MarkLogic cluster to a secure MarkLogic destination. See Telemetry in Monitor MarkLogic Server.

TDE (Template Driven Extraction)

Template Driven Extraction (TDE) enables you to define a relational lens over your document data, so you can query parts of your data using SQL or the Optic API. Templates let you specify which parts of documents make up rows in a view. You can also use templates to define a semantic lens, specifying which values from a document make up triples in the triple index. See TDE (Template Driven Extraction) in Develop Server-Side Applications.

temporal

Bitemporal. Temporal refers to bitemporal documents and collections. See bitemporal, non-temporal, and Last Stable Query Time (LSQT).

term

MarkLogic. A term is anything stored in the Universal Index; for example words, stems, two-word phrases, value of a declared field, and so on. What terms that you have in your Universal Index depends on your index settings.

thesaural relationship

Semantics. A conceptual hierarchy built by terms that are interlinked with a few very generic relationships. A thesaurus is a hierarchical representation of a set of terms related by broader term, narrower term, synonym, and so on. See Simple Knowledge Organization System (SKOS).

Token Server URI

OAuth. OAuth server endpoint for obtaining access tokens.

tokenization

Search. The process of splitting a run of text into parts (tokens), without overlap or gaps. Each token is classified as a word, whitespace, or punctuation. For details, see Tokenization and Stemming in Develop Search Applications.

transaction

Database. A set of one or more statements which either all fail or all succeed. A transaction is either an update transaction or a query (read-only) transaction, depending on the transaction mode and the kind of statements in the transaction. A transaction is either a single-statement transaction or a multi-statement transaction, depending on the transaction mode at the time it is created.

transaction mode

Database. Controls the type and the commit semantics of newly created transactions. Mode is one of auto, query, or update. In the default mode, auto, all transactions are single-statement transaction. In query or update mode, all transactions are multi-statement transaction. To learn more about transaction mode, see Transaction Type in Develop Server-Side Applications.

transaction-aware

Flexible Replication. A configuration in which all updates that make up a transaction on the Master are applied as a single transaction on the Replica.

trees

XML. XML documents form a tree structure (a document tree), starting at the “root” (root element) with “branches” containing “leaves” (child elements and attributes). The last line of the document is a the closing tag for the root element. The root element is the parent of the all the other elements. So an XML document tree has a root, branches, and leaves.

trigger

MarkLogic. Triggers listen for certain events (document create, delete, update, or the database coming online) to occur, and then invoke an XQuery module to run after the event occurs. A trigger is used to as part of Content Processing Framework (CPF). See Overview of Triggers in Develop Server-Side Applications.

triple

Semantics. A triple is an instance of a data model representing a fact or relationship, made up Subject, Predicate, Object. Triples can be serialized different formats like Terse RDF Triple Language (Turtle) ,Notation 3 (N3), or RDF/XML. See managed triples and unmanaged triples, Resource Description Framework Schema (RDFS) and graph. See also inference.

triple index

Semantics. An index that indexes triples ingested into MarkLogic to facilitate the execution of SPARQL queries. Triples can be standalone (“managed”) or embedded in a document (“unmanaged”).

triple store

Semantics. See RDF Triple Store.

Turtle (Terse RDF Triple Language)

Semantics. A format for expressing data in the Resource Description Framework Schema (RDFS) data model with the syntax similar to SPARQL. RDF represents information as a triple consisting of Subject, Predicate, and Object. RDF/XML and Notation 3 (N3) are other serializations of RDF.