mirror of https://gitee.com/bigwinds/arangodb
updated CHANGELOG
This commit is contained in:
jsteemann
parent
f1eae33b39
commit
08adb27afb
196
CHANGELOG
196
CHANGELOG
|
|
@ -1,6 +1,17 @@
|
|||
devel
|
||||
-----
|
||||
|
||||
* upgraded JEMalloc version to 5.1.0
|
||||
|
||||
* use `-std=c++14` for ArangoDB compilation
|
||||
|
||||
|
||||
v3.4.0-rc.1
|
||||
-----------
|
||||
|
||||
* Release Candidate for 3.4.0, please check the `ReleaseNotes/KnownIssues34.md`
|
||||
file for a list of known issues.
|
||||
|
||||
* upgraded bundled RocksDB version to 5.16.0
|
||||
|
||||
* upgraded bundled Snappy compression library to 1.1.7
|
||||
|
|
@ -522,12 +533,195 @@ devel
|
|||
* only load Plan and Current from agency when actually needed
|
||||
|
||||
|
||||
v3.3.13 (XXXX-XX-XX)
|
||||
v3.3.15 (XXXX-XX-XX)
|
||||
--------------------
|
||||
|
||||
* fixed issue #5941 if using breadth-first search in traversals uniqueness checks
|
||||
on path (vertices and edges) have not been applied. In SmartGraphs the checks
|
||||
have been executed properly.
|
||||
|
||||
* added more detailed progress output to arangorestore, showing the percentage of
|
||||
how much data is restored for bigger collections plus a set of overview statistics
|
||||
after each processed collection
|
||||
|
||||
* added option `--rocksdb.use-file-logging` to enable writing of RocksDB's own
|
||||
informational LOG files into RocksDB's database directory.
|
||||
|
||||
This option is turned off by default, but can be enabled for debugging RocksDB
|
||||
internals and performance.
|
||||
|
||||
* improved error messages when managing Foxx services
|
||||
|
||||
Install/replace/upgrade will now provide additional information when an error
|
||||
is encountered during setup. Errors encountered during a `require` call will
|
||||
also include information about the underlying cause in the error message.
|
||||
|
||||
* fixed some Foxx script names being displayed incorrectly in web UI and Foxx CLI
|
||||
|
||||
* added startup option `--query.optimizer-max-plans value`
|
||||
|
||||
This option allows limiting the number of query execution plans created by the
|
||||
AQL optimizer for any incoming queries. The default value is `128`.
|
||||
|
||||
By adjusting this value it can be controlled how many different query execution
|
||||
plans the AQL query optimizer will generate at most for any given AQL query.
|
||||
Normally the AQL query optimizer will generate a single execution plan per AQL query,
|
||||
but there are some cases in which it creates multiple competing plans. More plans
|
||||
can lead to better optimized queries, however, plan creation has its costs. The
|
||||
more plans are created and shipped through the optimization pipeline, the more time
|
||||
will be spent in the optimizer.
|
||||
|
||||
Lowering this option's value will make the optimizer stop creating additional plans
|
||||
when it has already created enough plans.
|
||||
|
||||
Note that this setting controls the default maximum number of plans to create. The
|
||||
value can still be adjusted on a per-query basis by setting the *maxNumberOfPlans*
|
||||
attribute when running a query.
|
||||
|
||||
This change also lowers the default maximum number of query plans from 192 to 128.
|
||||
|
||||
* bug fix: facilitate faster shutdown of coordinators and db servers
|
||||
|
||||
* upgraded arangodb starter version to 0.13.2
|
||||
|
||||
* cluster nodes should retry registering in agency until successful
|
||||
|
||||
* fixed some web ui action events related to Running Queries view and Slow
|
||||
Queries History view
|
||||
|
||||
* Create a default pacing algorithm for arangoimport to avoid TimeoutErrors
|
||||
on VMs with limited disk throughput
|
||||
|
||||
* backport PR 6150: establish unique function to indicate when
|
||||
application is terminating and therefore network retries should not occur
|
||||
|
||||
* backport PR #5201: eliminate race scenario where handlePlanChange
|
||||
could run infinite times after an execution exceeded 7.4 second time span
|
||||
|
||||
|
||||
v3.3.14 (2018-08-15)
|
||||
--------------------
|
||||
|
||||
* upgraded arangodb starter version to 0.13.1
|
||||
|
||||
* Foxx HTTP API errors now log stacktraces
|
||||
|
||||
* fixed issue #5736: Foxx HTTP API responds with 500 error when request body
|
||||
is too short
|
||||
|
||||
* fixed issue #5831: custom queries in the ui could not be loaded if the user
|
||||
only has read access to the _system database.
|
||||
|
||||
* fixed internal issue #2566: corrected web UI alignment of the nodes table
|
||||
|
||||
* fixed internal issue #2869: when attaching a follower with global applier to an
|
||||
authenticated leader already existing users have not been replicated, all users
|
||||
created/modified later are replicated.
|
||||
|
||||
* fixed internal issue #2865: dumping from an authenticated arangodb the users have
|
||||
not been included
|
||||
|
||||
* fixed issue #5943: misplaced database ui icon and wrong cursor type were used
|
||||
|
||||
* fixed issue #5354: updated the web UI JSON editor, improved usability
|
||||
|
||||
* fixed issue #5648: fixed error message when saving unsupported document types
|
||||
|
||||
* fixed issue #6076: Segmentation fault after AQL query
|
||||
|
||||
This also fixes issues #6131 and #6174
|
||||
|
||||
* fixed issue #5884: Subquery nodes are no longer created on DBServers
|
||||
|
||||
* fixed issue #6031: Broken LIMIT in nested list iterations
|
||||
|
||||
* fixed internal issue #2812: Cluster fails to create many indexes in parallel
|
||||
|
||||
* intermediate commits in the RocksDB engine are now only enabled in standalone AQL
|
||||
queries (not within a JS transaction), standalone truncate as well as for the
|
||||
"import" API
|
||||
|
||||
* Bug fix: race condition could request data from Agency registry that did not
|
||||
exist yet. This caused a throw that would end the Supervision thread.
|
||||
All registry query APIs no longer throw exceptions.
|
||||
|
||||
|
||||
v3.3.13 (2018-07-26)
|
||||
--------------------
|
||||
|
||||
* fixed internal issue #2567: the Web UI was showing the possibility to move a
|
||||
shard from a follower to the current leader
|
||||
|
||||
* fixed issue #5977: Unexpected execution plan when subquery contains COLLECT
|
||||
|
||||
* Bugfix: The AQL syntax variants `UPDATE/REPLACE k WITH d` now correctly take
|
||||
_rev from k instead of d (when ignoreRevs is false) and ignore d._rev.
|
||||
|
||||
* put an upper bound on the number of documents to be scanned when using
|
||||
`db.<collection>.any()` in the RocksDB storage engine
|
||||
|
||||
previous versions of ArangoDB did a scan of a random amount of documents in
|
||||
the collection, up to the total number of documents available. this produced
|
||||
a random selection with a good quality, but needed to scan half the number
|
||||
of documents in the collection on average.
|
||||
|
||||
The new version will only scan up to 500 documents, so it produces a less
|
||||
random result, but will be a lot faster especially for large collections.
|
||||
|
||||
The implementation of `any()` for the MMFiles engine remains unchanged. The
|
||||
MMFiles engine will pick a random document from the entire range of the
|
||||
in-memory primary index without performing scans.
|
||||
|
||||
* return an empty result set instead of an "out of memory" exception when
|
||||
querying the geo index with invalid (out of range) coordinates
|
||||
|
||||
* added load balancer support and user-restriction to cursor API.
|
||||
|
||||
If a cursor is accessed on a different coordinator than where it was created,
|
||||
the requests will be forwarded to the correct coordinator. If a cursor is
|
||||
accessed by a different user than the one who created it, the request will
|
||||
be denied.
|
||||
|
||||
* keep failed follower in followers list in Plan.
|
||||
|
||||
This increases the changes of a failed follower getting back into sync if the
|
||||
follower comes back after a short time. In this case the follower can try to
|
||||
get in sync again, which normally takes less time than seeding a completely
|
||||
new follower.
|
||||
|
||||
* fix assertion failure and undefined behavior in Unix domain socket connections,
|
||||
introduced by 3.3.12
|
||||
|
||||
* added configuration option `--rocksdb.sync-interval`
|
||||
|
||||
This option specifies interval (in milliseconds) that ArangoDB will use to
|
||||
automatically synchronize data in RocksDB's write-ahead log (WAL) files to
|
||||
disk. Automatic syncs will only be performed for not-yet synchronized data,
|
||||
and only for operations that have been executed without the *waitForSync*
|
||||
attribute.
|
||||
|
||||
Automatic synchronization is performed by a background thread. The default
|
||||
sync interval is 0, meaning the automatic background syncing is turned off.
|
||||
Background syncing in 3.3 is opt-in, whereas in ArangoDB 3.4 the default sync
|
||||
interval will be 100 milliseconds.
|
||||
|
||||
Note: this option is not supported on Windows platforms. Setting the sync
|
||||
interval to a value greater 0 will produce a startup warning.
|
||||
|
||||
* fixed graph creation sometimes failing with 'edge collection
|
||||
already used in edge def' when the edge definition contained multiple vertex
|
||||
collections, despite the edge definitions being identical
|
||||
|
||||
* inception could get caught in a trap, where agent configuration
|
||||
version and timeout multiplier lead to incapacitated agency
|
||||
|
||||
* fixed issue #5827: Batch request handling incompatible with .NET's default
|
||||
ContentType format
|
||||
|
||||
* fixed agency's log compaction for internal issue #2249
|
||||
|
||||
* inspector collects additionally disk data size and storage engine statistics
|
||||
|
||||
|
||||
v3.3.12 (2018-07-12)
|
||||
--------------------
|
||||
|
|
|
|||
Loading…
Reference in New Issue