Skip to main content

Administrating MarkLogic Server

Terms Used in This Section

  • A Partition is a set of forests sharing the same name prefix and same partition definition. Typically forests in a partition share the same type of storage and configuration such as updates allowed, availability, and enabled status. Partitions are based on forest naming conventions. A forest’s partition name prefix and the rest of the forest name are separated by a dash (-). For example, a forest named 2011-0001 belongs to the 2011 partition.

  • A Range Partition is a partition that is associated with a range of values. Documents with a partition key value that fall within the range specified for a partition are stored in that range partition.

  • A Query Partition is a partition that is associated with a query. Documents that are returned by the query specified for a query partition are stored in that query partition.

  • A Partition Key defines an element or attribute on which a range index, collection lexicon, or field is set and defines the context for the range set on the range partitions in the database. The partition key is a database-level setting.

  • A Default Partition is a partition with no defined range or query. Documents that have no partition key or a partition key value that does not fall into any of the partition ranges or queries are stored in the default partition.

  • A Super-database is a database containing other databases (sub-databases) so that they can be queried as if they were a single logical database.

  • A Sub-database is a database contained in a super-database.

  • Active Data is data that requires low-latency queries and updates. The “activeness” of a particular document is typically determined by its recency and thus changes over time.

  • Historical Data is less critical for the lowest-latency queries than “active” data, but still requires online access for queries. Historical data is not typically updated.

  • Archived Data is data that has aged beyond its useful life in the online storage tiers and is typically taken offline.

  • An Online partition or forest is available for queries and updates.

  • An Offline partition or forest is not available for queries, but is tracked by the cluster. The benefit of taking data offline is to spare the RAM, CPU, and network resources for the online data.

  • The Availability of a partition or forest refers to its online/offline status.

In this section: