Skip to content

Commit e96eda5

Browse files
committed
Fix attribute name in ArangoSearch description
1 parent 4c19000 commit e96eda5

File tree

4 files changed

+12
-12
lines changed

4 files changed

+12
-12
lines changed

site/content/3.10/index-and-search/arangosearch/performance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -198,12 +198,12 @@ To define more than one attribute to sort by, use multiple sub-objects in the
198198
{{< /tabs >}}
199199

200200
The optimization can be applied to queries which sort by both fields as
201-
defined (`SORT doc.date DESC, doc.name`), but also if they sort in descending
201+
defined (`SORT doc.date DESC, doc.text`), but also if they sort in descending
202202
order by the `date` attribute only (`SORT doc.date DESC`). Queries which sort
203-
by `text` alone (`SORT doc.name`) are not eligible, because the index is sorted
203+
by `text` alone (`SORT doc.text`) are not eligible, because the index is sorted
204204
by `date` first. This is similar to persistent indexes, but inverted sorting
205205
directions are not covered by the View index
206-
(e.g. `SORT doc.date, doc.name DESC`).
206+
(e.g. `SORT doc.date, doc.text DESC`).
207207

208208
You can disable the **primary sort compression** on View or index creation to
209209
trade space for speed. The primary sort data is LZ4-compressed by default (`"lz4"`).

site/content/3.11/index-and-search/arangosearch/performance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -198,12 +198,12 @@ To define more than one attribute to sort by, use multiple sub-objects in the
198198
{{< /tabs >}}
199199

200200
The optimization can be applied to queries which sort by both fields as
201-
defined (`SORT doc.date DESC, doc.name`), but also if they sort in descending
201+
defined (`SORT doc.date DESC, doc.text`), but also if they sort in descending
202202
order by the `date` attribute only (`SORT doc.date DESC`). Queries which sort
203-
by `text` alone (`SORT doc.name`) are not eligible, because the index is sorted
203+
by `text` alone (`SORT doc.text`) are not eligible, because the index is sorted
204204
by `date` first. This is similar to persistent indexes, but inverted sorting
205205
directions are not covered by the View index
206-
(e.g. `SORT doc.date, doc.name DESC`).
206+
(e.g. `SORT doc.date, doc.text DESC`).
207207

208208
You can disable the **primary sort compression** on View or index creation to
209209
trade space for speed. The primary sort data is LZ4-compressed by default (`"lz4"`).

site/content/3.12/index-and-search/arangosearch/performance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -198,12 +198,12 @@ To define more than one attribute to sort by, use multiple sub-objects in the
198198
{{< /tabs >}}
199199

200200
The optimization can be applied to queries which sort by both fields as
201-
defined (`SORT doc.date DESC, doc.name`), but also if they sort in descending
201+
defined (`SORT doc.date DESC, doc.text`), but also if they sort in descending
202202
order by the `date` attribute only (`SORT doc.date DESC`). Queries which sort
203-
by `text` alone (`SORT doc.name`) are not eligible, because the index is sorted
203+
by `text` alone (`SORT doc.text`) are not eligible, because the index is sorted
204204
by `date` first. This is similar to persistent indexes, but inverted sorting
205205
directions are not covered by the View index
206-
(e.g. `SORT doc.date, doc.name DESC`).
206+
(e.g. `SORT doc.date, doc.text DESC`).
207207

208208
You can disable the **primary sort compression** on View or index creation to
209209
trade space for speed. The primary sort data is LZ4-compressed by default (`"lz4"`).

site/content/3.13/index-and-search/arangosearch/performance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -198,12 +198,12 @@ To define more than one attribute to sort by, use multiple sub-objects in the
198198
{{< /tabs >}}
199199

200200
The optimization can be applied to queries which sort by both fields as
201-
defined (`SORT doc.date DESC, doc.name`), but also if they sort in descending
201+
defined (`SORT doc.date DESC, doc.text`), but also if they sort in descending
202202
order by the `date` attribute only (`SORT doc.date DESC`). Queries which sort
203-
by `text` alone (`SORT doc.name`) are not eligible, because the index is sorted
203+
by `text` alone (`SORT doc.text`) are not eligible, because the index is sorted
204204
by `date` first. This is similar to persistent indexes, but inverted sorting
205205
directions are not covered by the View index
206-
(e.g. `SORT doc.date, doc.name DESC`).
206+
(e.g. `SORT doc.date, doc.text DESC`).
207207

208208
You can disable the **primary sort compression** on View or index creation to
209209
trade space for speed. The primary sort data is LZ4-compressed by default (`"lz4"`).

0 commit comments

Comments
 (0)