mirror of https://gitee.com/bigwinds/arangodb
Feature/changelog for subquery splicing (#10396)
* Add a CHANGELOG entry for subquery splicing
This commit is contained in:
parent
e11e81e0b7
commit
2902ab9c23
17
CHANGELOG
17
CHANGELOG
|
@ -1,6 +1,23 @@
|
|||
devel
|
||||
-----
|
||||
|
||||
* Added a new subquery optimization called `splice-subqueries`.
|
||||
|
||||
This optimization splices the execution of subqueries inside the
|
||||
execution of their surrounding query. For subqueries with a fairly
|
||||
small number of returned documents this saves a significant amount of
|
||||
overhead initializing cursors.
|
||||
|
||||
This optimization is performed by the optimizer rule
|
||||
`splice-subqueries`, and currently only works on suitable
|
||||
subqueries; A subquery becomes unsuitable if it contains a LIMIT,
|
||||
REMOTE, GATHER or a COLLECT node where the operation is WITH COUNT INTO.
|
||||
A subquery also becomes unsuitable if it is contained in an
|
||||
(sub)query which contains unsuitable operations after the subquery.
|
||||
|
||||
The implementation of this feature required reworking the dataflow
|
||||
query execution.
|
||||
|
||||
* Fixed issue #10470: The WebUI now shows potential errors and details which occured using _api/import (e.g.
|
||||
unique constraint violated).
|
||||
|
||||
|
|
Loading…
Reference in New Issue