Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

updated CHANGELOG

This commit is contained in:
jsteemann 2018-07-04 19:02:50 +02:00
parent 0001fbae92
commit 2d622bcd9e
2 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CHANGELOG
View File

@ -21,11 +21,13 @@ devel
in a cluster by pushing parts of the aggregation onto the DB servers and only
doing the total aggregation on the coordinator
* replace JavaScript functions FULLTEXT, NEAR, WITHIN with regular AQL via a
new optimizer rule.
* replace JavaScript functions FULLTEXT, NEAR, WITHIN and WITHIN_RECTANGLE with
regular AQL subqueries via a new optimizer rule "replace-function-with-index".
- The NEAR function now does not default to a limit of 100 documents any more.
- "fulltext-index-optimizer" optimizer rule has been removed.
* the existing "fulltext-index-optimizer" optimizer rule has been removed because its
duty is now handled by the "replace-function-with-index" rule.
* The `NEAR` AQL function now does not default to a limit of 100 documents any more.
* added option "--latency true" option to arangoimport. Lists microsecond latency
statistics on 10 second intervals.

5
Documentation/Books/AQL/ExecutionAndPerformance/Optimizer.md
View File

@ -423,8 +423,9 @@ The following optimizer rules may appear in the `rules` attribute of a plan:
e.g. `FOR x IN (FOR y IN collection FILTER y.value >= 5 RETURN y.test) RETURN x.a`
would become `FOR tmp IN collection FILTER tmp.value >= 5 LET x = tmp.test RETURN x.a`
* `geo-index-optimizer`: will appear when a geo index is utilized.
* `replace-function-with-index`: will appear when a function like FULLTEXT is replaced
with an index.
* `replace-function-with-index`: will appear when a deprecated index function such as
`FULLTEXT`, `NEAR`, `WITHIN` or `WITHIN_RECTANGLE` is replaced with a regular
subquery.
* `remove-sort-rand`: will appear when a *SORT RAND()* expression is removed by
moving the random iteration into an *EnumerateCollectionNode*. This optimizer rule
is specific for the MMFiles storage engine.