The collection remains (mostly) available during the index creation, see the section Creating Indexes in Background for more information.ĪrangoDB provides the following index types: Primary Indexįor each collection there will always be a primary index which is a hash index for the document keys ( _key attribute)of all documents in the collection. This “foreground” index creation can be undesirable, if you have to perform it on a live system without a dedicated maintenance window.įor potentially long running index creation operations the RocksDB storage-engine also supports creating indexes in “background”. The collection is notavailable while the index is being created. Using the system attribute _id in user-defined indexes is not possible, but indexing _key, _rev, _from, and _to is.Ĭreating new indexes is by default done under an exclusive collection lock. _id and _key are covered by a collection’s primary key, and _from and _toare covered by an edge collection’s edge index automatically. The system attributes _id, _key, _from and _to are automatically indexedby ArangoDB, without the user being required to create extra indexes for them.
WHILE IN ARANGODB HOW TO
Learn how to use different indexes efficiently by going through the ArangoDB Performance Course. fulltext index) whereas other index types allow indexing multiple attributes at the same time. Most user-defined indexes can be created by specifying the names of the index attributes.Some index types allow indexing just one attribute (e.g. User-defined indexes can be created on collection level. While ArangoDB automatically indexes some systemattributes, users are free to create extra indexes on non-system attributesof documents. Indexes allow fast access to documents, provided the indexed attribute(s)are used in a query.
0 kommentar(er)
