mirror of https://gitee.com/bigwinds/arangodb
update known issues
This commit is contained in:
parent
8441368954
commit
d5fa618677
|
@ -4,17 +4,8 @@ Known Issues
|
|||
The following known issues are present in this version of ArangoDB and will be fixed
|
||||
in follow-up releases:
|
||||
|
||||
Installer
|
||||
---------
|
||||
|
||||
* Rolling upgrades are not yet supported with the RC version of ArangoDB 3.4, when
|
||||
there are multiple instances of the same ArangoDB version running on the same host,
|
||||
and only some of them shall be upgraded, or they should be upgraded one after the
|
||||
other.
|
||||
|
||||
|
||||
Modify documents in cluster using AQL and an incorrect custom shard key
|
||||
-----------------------------------------------------------------------
|
||||
Modifing documents in cluster using AQL and an incorrect custom shard key
|
||||
-------------------------------------------------------------------------
|
||||
|
||||
* In a very uncommon edge case there is an issue with an optimization rule in the cluster.
|
||||
|
||||
|
|
|
@ -686,6 +686,9 @@ removed, so it cannot be use from Foxx applications anymore The module only
|
|||
provided the current version of the database, so any client-side invocations
|
||||
can easily be replaced by using the `db._version()` instead.
|
||||
|
||||
The `ShapedJson` JavaScript object prototype, a remainder from ArangoDB 2.8
|
||||
for encapsulating database documents, has been removed in ArangoDB 3.4.
|
||||
|
||||
|
||||
Miscellaneous changes
|
||||
---------------------
|
||||
|
|
Loading…
Reference in New Issue