ArangoDB v3.7 reached End of Life (EOL) and is no longer supported.
This documentation is outdated. Please see the most recent version here: Latest Docs
HTTP Interface for Indexes
This is an introduction to ArangoDB’s HTTP interface for indexes in general. There are special sections for various index types.
Indexes are used to allow fast access to documents. For each collection there is always the primary index which is a hash index for the
document key (_key attribute). This index cannot be dropped or changed.
edge collections will also have an automatically created edges index, which cannot be modified. This index provides quick access to documents via the
Most user-land indexes can be created by defining the names of the attributes which should be indexed. Some index types allow indexing just one attribute (e.g. fulltext index) whereas other index types allow indexing multiple attributes.
Using the system attribute
_id in user-defined indexes is not supported by any index type.
An index handle uniquely identifies an index in the database. It is a string and consists of a collection name and an index identifier separated by /. If the index is declared unique, then access to the indexed attributes should be fast. The performance degrades if the indexed attribute(s) contain(s) only very few distinct values.
A primary index is automatically created for each collections. It indexes the documents’ primary keys, which are stored in the
_key system attribute. The primary index is unique and can be used for queries on both the
There is no way to explicitly create or delete primary indexes.
An edge index is automatically created for edge collections. It contains connections between vertex documents and is invoked when the connecting edges of a vertex are queried. There is no way to explicitly create or delete edge indexes. The edge index is non-unique.
A hash index is an unsorted index that can be used to find individual documents by equality lookups.
A skiplist is a sorted index that can be used to find individual documents or ranges of documents.
A persistent index is a sorted index that can be used for finding individual documents or ranges of documents. In contrast to the other indexes, the contents of a persistent index are stored on disk and thus do not need to be rebuilt in memory from the documents when the collection is loaded.
TTL (time-to-live) index
The TTL index can be used for automatically removing expired documents from a collection. Documents which are expired are eventually removed by a background thread.
A fulltext index can be used to find words, or prefixes of words inside documents. A fulltext index can be set on one attribute only, and will index all words contained in documents that have a textual value in this attribute. Only words with a (specifiable) minimum length are indexed. Word tokenization is done using the word boundary analysis provided by libicu, which is taking into account the selected language provided at server start. Words are indexed in their lower-cased form. The index supports complete match queries (full words) and prefix queries.
Address of an Index
All indexes in ArangoDB have an unique handle. This index handle identifies an index and is managed by ArangoDB. All indexes are found under the URI
For example: Assume that the index handle is demo/63563528 then the URL of that index is: