public class ArangoSearchCreateOptions extends Object
| Constructor and Description |
|---|
ArangoSearchCreateOptions() |
| Modifier and Type | Method and Description |
|---|---|
ArangoSearchCreateOptions |
cleanupIntervalStep(Long cleanupIntervalStep) |
ArangoSearchCreateOptions |
commitIntervalMsec(Long commitIntervalMsec) |
ArangoSearchCreateOptions |
consolidationIntervalMsec(Long consolidationIntervalMsec) |
ArangoSearchCreateOptions |
consolidationPolicy(ConsolidationPolicy consolidationPolicy) |
ArangoSearchCreateOptions |
link(CollectionLink... links) |
protected ArangoSearchCreateOptions |
name(String name) |
ArangoSearchCreateOptions |
optimizeTopK(String... optimizeTopK) |
ArangoSearchCreateOptions |
primaryKeyCache(Boolean primaryKeyCache) |
ArangoSearchCreateOptions |
primarySort(PrimarySort... primarySorts) |
ArangoSearchCreateOptions |
primarySortCache(Boolean primarySortCache) |
ArangoSearchCreateOptions |
primarySortCompression(ArangoSearchCompression primarySortCompression) |
ArangoSearchCreateOptions |
storedValues(StoredValue... storedValues) |
protected ArangoSearchCreateOptions name(String name)
public ArangoSearchCreateOptions consolidationIntervalMsec(Long consolidationIntervalMsec)
consolidationIntervalMsec - Wait at least this many milliseconds between committing index data changes and making them visible to
queries (default: 60000, to disable use: 0). For the case where there are a lot of inserts/updates, a
lower value, until commit, will cause the index not to account for them and memory usage would
continue to grow. For the case where there are a few inserts/updates, a higher value will impact
performance and waste disk space for each commit call without any added benefits.public ArangoSearchCreateOptions commitIntervalMsec(Long commitIntervalMsec)
commitIntervalMsec - Wait at least this many milliseconds between committing view data store changes and making documents visible to
queries (default: 1000, to disable use: 0). For the case where there are a lot of inserts/updates, a lower value,
until commit, will cause the index not to account for them and memory usage would continue to grow. For the case
where there are a few inserts/updates, a higher value will impact performance and waste disk space for each
commit call without any added benefits. Background: For data retrieval ArangoSearch views follow the concept of
“eventually-consistent”, i.e. eventually all the data in ArangoDB will be matched by corresponding query
expressions. The concept of ArangoSearch view “commit” operation is introduced to control the upper-bound on the
time until document addition/removals are actually reflected by corresponding query expressions. Once a “commit”
operation is complete all documents added/removed prior to the start of the “commit” operation will be reflected
by queries invoked in subsequent ArangoDB transactions, in-progress ArangoDB transactions will still continue to
return a repeatable-read state.public ArangoSearchCreateOptions cleanupIntervalStep(Long cleanupIntervalStep)
cleanupIntervalStep - Wait at least this many commits between removing unused files in data directory (default: 10, to
disable use: 0). For the case where the consolidation policies merge segments often (i.e. a lot of
commit+consolidate), a lower value will cause a lot of disk space to be wasted. For the case where the
consolidation policies rarely merge segments (i.e. few inserts/deletes), a higher value will impact
performance without any added benefits.public ArangoSearchCreateOptions consolidationPolicy(ConsolidationPolicy consolidationPolicy)
consolidationPolicy - public ArangoSearchCreateOptions link(CollectionLink... links)
links - A list of linked collectionspublic ArangoSearchCreateOptions primarySort(PrimarySort... primarySorts)
primarySorts - A list of linked collectionspublic ArangoSearchCreateOptions primarySortCompression(ArangoSearchCompression primarySortCompression)
primarySortCompression - Defines how to compress the primary sort datapublic ArangoSearchCreateOptions storedValues(StoredValue... storedValues)
public ArangoSearchCreateOptions optimizeTopK(String... optimizeTopK)
optimizeTopK - An array of strings defining sort expressions that you want to optimize.public ArangoSearchCreateOptions primarySortCache(Boolean primarySortCache)
primarySortCache - If you enable this option, then the primary sort columns are always cached in memory.
This can improve the performance of queries that utilize the primary sort order.
Otherwise, these values are memory-mapped and it is up to the operating system to load
them from disk into memory and to evict them from memory.public ArangoSearchCreateOptions primaryKeyCache(Boolean primaryKeyCache)
primaryKeyCache - If you enable this option, then the primary key columns are always cached in memory. This
can improve the performance of queries that return many documents. Otherwise, these values
are memory-mapped and it is up to the operating system to load them from disk into memory
and to evict them from memory.Copyright © 2016–2023 ArangoDB GmbH. All rights reserved.