|
27 | 27 |
|
28 | 28 | /**
|
29 | 29 | * @author Mark Vollmary
|
30 |
| - * |
31 | 30 | */
|
32 | 31 | public class ArangoSearchPropertiesEntity extends ViewEntity {
|
33 | 32 |
|
34 |
| - private final ArangoSearchProperties properties; |
| 33 | + private final ArangoSearchProperties properties; |
| 34 | + |
| 35 | + public ArangoSearchPropertiesEntity(final String id, final String name, final ViewType type, |
| 36 | + final ArangoSearchProperties properties) { |
| 37 | + super(id, name, type); |
| 38 | + this.properties = properties; |
| 39 | + } |
35 | 40 |
|
36 |
| - public ArangoSearchPropertiesEntity(final String id, final String name, final ViewType type, |
37 |
| - final ArangoSearchProperties properties) { |
38 |
| - super(id, name, type); |
39 |
| - this.properties = properties; |
40 |
| - } |
| 41 | + /** |
| 42 | + * @return Wait at least this many milliseconds between committing index data changes and making them visible to |
| 43 | + * queries (default: 60000, to disable use: 0). For the case where there are a lot of inserts/updates, a |
| 44 | + * lower value, until commit, will cause the index not to account for them and memory usage would continue |
| 45 | + * to grow. For the case where there are a few inserts/updates, a higher value will impact performance and |
| 46 | + * waste disk space for each commit call without any added benefits. |
| 47 | + */ |
| 48 | + public Long getConsolidationIntervalMsec() { |
| 49 | + return properties.getConsolidationIntervalMsec(); |
| 50 | + } |
41 | 51 |
|
42 |
| - /** |
43 |
| - * @return Wait at least this many milliseconds between committing index data changes and making them visible to |
44 |
| - * queries (default: 60000, to disable use: 0). For the case where there are a lot of inserts/updates, a |
45 |
| - * lower value, until commit, will cause the index not to account for them and memory usage would continue |
46 |
| - * to grow. For the case where there are a few inserts/updates, a higher value will impact performance and |
47 |
| - * waste disk space for each commit call without any added benefits. |
48 |
| - */ |
49 |
| - public Long getConsolidationIntervalMsec() { |
50 |
| - return properties.getConsolidationIntervalMsec(); |
51 |
| - } |
| 52 | + /** |
| 53 | + * @return Wait at least this many milliseconds between committing view data store changes and making documents |
| 54 | + * visible to queries (default: 1000, to disable use: 0). For the case where there are a lot of inserts/updates, a |
| 55 | + * lower value, until commit, will cause the index not to account for them and memory usage would continue to grow. |
| 56 | + * For the case where there are a few inserts/updates, a higher value will impact performance and waste disk space |
| 57 | + * for each commit call without any added benefits. Background: For data retrieval ArangoSearch views follow the |
| 58 | + * concept of “eventually-consistent”, i.e. eventually all the data in ArangoDB will be matched by corresponding |
| 59 | + * query expressions. The concept of ArangoSearch view “commit” operation is introduced to control the upper-bound |
| 60 | + * on the time until document addition/removals are actually reflected by corresponding query expressions. Once a |
| 61 | + * “commit” operation is complete all documents added/removed prior to the start of the “commit” operation will be |
| 62 | + * reflected by queries invoked in subsequent ArangoDB transactions, in-progress ArangoDB transactions will still |
| 63 | + * continue to return a repeatable-read state. |
| 64 | + */ |
| 65 | + public Long getCommitIntervalMsec() { |
| 66 | + return properties.getCommitIntervalMsec(); |
| 67 | + } |
52 | 68 |
|
53 |
| - /** |
54 |
| - * @return Wait at least this many commits between removing unused files in data directory (default: 10, to disable |
55 |
| - * use: 0). For the case where the consolidation policies merge segments often (i.e. a lot of |
56 |
| - * commit+consolidate), a lower value will cause a lot of disk space to be wasted. For the case where the |
57 |
| - * consolidation policies rarely merge segments (i.e. few inserts/deletes), a higher value will impact |
58 |
| - * performance without any added benefits. |
59 |
| - */ |
60 |
| - public Long getCleanupIntervalStep() { |
61 |
| - return properties.getCleanupIntervalStep(); |
62 |
| - } |
| 69 | + /** |
| 70 | + * @return Wait at least this many commits between removing unused files in data directory (default: 10, to disable |
| 71 | + * use: 0). For the case where the consolidation policies merge segments often (i.e. a lot of |
| 72 | + * commit+consolidate), a lower value will cause a lot of disk space to be wasted. For the case where the |
| 73 | + * consolidation policies rarely merge segments (i.e. few inserts/deletes), a higher value will impact |
| 74 | + * performance without any added benefits. |
| 75 | + */ |
| 76 | + public Long getCleanupIntervalStep() { |
| 77 | + return properties.getCleanupIntervalStep(); |
| 78 | + } |
63 | 79 |
|
64 |
| - public ConsolidationPolicy getConsolidationPolicy() { |
65 |
| - return properties.getConsolidationPolicy(); |
66 |
| - } |
| 80 | + public ConsolidationPolicy getConsolidationPolicy() { |
| 81 | + return properties.getConsolidationPolicy(); |
| 82 | + } |
67 | 83 |
|
68 |
| - /** |
69 |
| - * @return A list of linked collections |
70 |
| - */ |
71 |
| - public Collection<CollectionLink> getLinks() { |
72 |
| - return properties.getLinks(); |
73 |
| - } |
| 84 | + /** |
| 85 | + * @return A list of linked collections |
| 86 | + */ |
| 87 | + public Collection<CollectionLink> getLinks() { |
| 88 | + return properties.getLinks(); |
| 89 | + } |
74 | 90 |
|
| 91 | + /** |
| 92 | + * @return A list of primary sort objects |
| 93 | + */ |
| 94 | + public Collection<PrimarySort> getPrimarySort() { |
| 95 | + return properties.getPrimarySort(); |
| 96 | + } |
75 | 97 | }
|
0 commit comments