Interface for a metadata index.
A description of the metadata state for a partition of a scale-out index.
Interface provides access to the left and right separator keys for an index partition.
Base class for
Encapsulate the reason why an index partition was created and the synchronous overflow counter of the data service on which the index partition was created as of that action.
Metadata required to locate a
An immutable object providing metadata about a local index partition, including the partition identifier, the left and right separator keys defining the half-open key range of the index partition, and optionally defining the
A metadata index for the partitions of a distributed index.
The extension semantics for the
An immutable object that may be used to locate an index partition.
Metadata for a single
Aggregates test suites into increasing dependency order.
Typesafe enumeration of reasons why an index partition was created.
This package provides a metadata index and range partitioned indices managed by that metadata index. Each index partition is a fused view of one or more resources. Those resources include a mutable BTree hosted on a Journal and read-only index segments. Reads are against the fused view. Writes are against the mutable BTree.
Periodically the mutable BTree, or the journal on which it resides, will fill up and a merge task will generate a read-only index segment. When a full merge (aka compacting merge) is applied, the result is a single index segment containing all data for the index partition. Depending on the history policy, some historical data versions and delete markers may be purged from the view meaning that some historical commit states will no longer be readable.
Index partitions are created by a split operation and merged by a join operation. These operations create new index partitions having different separator keys. Split and join operations are not effective until the metadata index has been updated.
Copyright © 2006–2016 SYSTAP, LLC DBA Blazegraph. All rights reserved.