mirror of https://gitee.com/bigwinds/arangodb
* update known issues for 3.4 * more known issues
This commit is contained in:
parent
f9dd500132
commit
6ba81d7603
|
@ -31,7 +31,10 @@ ArangoSearch
|
|||
------------
|
||||
|
||||
* ArangoSearch index format in 3.4RC3 is incompatible to earlier issued release candidates
|
||||
* ArangoSearch index format in 3.4RC4 is incompatible to earlier issued release candidates
|
||||
* ArangoSearch ignores `_id` attribute even if `includeAllFields` is set to `true` (internal #445)
|
||||
* Using score functions (BM25/TFIDF) in ArangoDB expression is not supported (internal #316)
|
||||
* Using a loop variable in expressions within a corresponding SEARCH condition is not supported (internal #318)
|
||||
* RocksDB recovery fails sometimes after renaming a view (internal #469)
|
||||
* Score values evaluated by corresponding score functions (BM25/TFIDF) may differ in single-server and cluster with a collection having more than 1 shard (internal #508)
|
||||
* ArangoSearch index consolidation doesn't work during creation of a link on existing collection which may lead to massive file descriptors consumption (intenal #509)
|
||||
* Long-running DML transactions on collections (linked with ArangoSearch view) block "ArangoDB flush thread" making impossible to refresh data "visible" by a view (internal #510)
|
||||
|
|
Loading…
Reference in New Issue