From cd16aa570874aa435c63fe06fe669a0e1cb9a013 Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Wed, 20 Mar 2024 11:10:33 +0100 Subject: [PATCH 1/7] Upgraded bundled OpenSSL --- .../3.12/release-notes/version-3.12/whats-new-in-3-12.md | 1 + .../content/4.0/release-notes/version-3.12/whats-new-in-3-12.md | 2 ++ 2 files changed, 3 insertions(+) diff --git a/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md b/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md index 6600ac6c8d..ed11206f64 100644 --- a/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md @@ -1205,3 +1205,4 @@ section above that includes a description of the added client tool options. For ArangoDB 3.12, the bundled version of rclone is 1.65.2. Check if your rclone configuration files require changes. +The bundled version of the OpenSSL library has been upgraded to 3.2.1. diff --git a/site/content/4.0/release-notes/version-3.12/whats-new-in-3-12.md b/site/content/4.0/release-notes/version-3.12/whats-new-in-3-12.md index 14569086fc..ed11206f64 100644 --- a/site/content/4.0/release-notes/version-3.12/whats-new-in-3-12.md +++ b/site/content/4.0/release-notes/version-3.12/whats-new-in-3-12.md @@ -1204,3 +1204,5 @@ section above that includes a description of the added client tool options. For ArangoDB 3.12, the bundled version of rclone is 1.65.2. Check if your rclone configuration files require changes. + +The bundled version of the OpenSSL library has been upgraded to 3.2.1. From f362784f552e262e0fd19ea3882c83636e82be50 Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Thu, 21 Mar 2024 10:21:39 +0100 Subject: [PATCH 2/7] collation Analyzer sorting change --- .../incompatible-changes-in-3-12.md | 18 ++++++++++++++++++ .../incompatible-changes-in-3-12.md | 18 ++++++++++++++++++ 2 files changed, 36 insertions(+) diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index ccdd740915..0cfffcbe88 100644 --- a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -170,6 +170,24 @@ onward and will be removed in a future version. You can use [Stream Transactions](../../develop/transactions/stream-transactions.md) instead in most cases, and in some cases AQL can be sufficient. +## Breaking changes to the `collation` Analyzer + +The [`collation` Analyzer](../../index-and-search/analyzers.md#collation) lets +you adhere to the alphabetic order of a language in range queries. For example, +using the Swedish locale (`sv`), `å` goes after `z` and not near `a`, which +can impact queries. + +Sorting by the output of the `collation` Analyzer like +`SORT TOKENS(, ` did not produce meaningful results in +previous versions. Sorting the letters `å`, `a`, `b`, `z` resulted in the order +`b` `a` `å` `z` using an English locale (`en`) and `b` `å` `a` `z` using a +Swedish locale (`sv`). + +In v3.12, this now sorts properly to `a` `å` `b` `z` (English) and +`a` `b` `z` `å` (Swedish). This change can make queries behave differently +compared to v3.11 and older, and inverted indexes and Views using +`collation` Analyzers need to be recreated to ensure that they work correctly. + ## Control character escaping in audit log The audit log feature of the Enterprise Edition previously logged query strings diff --git a/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md index ccdd740915..0cfffcbe88 100644 --- a/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -170,6 +170,24 @@ onward and will be removed in a future version. You can use [Stream Transactions](../../develop/transactions/stream-transactions.md) instead in most cases, and in some cases AQL can be sufficient. +## Breaking changes to the `collation` Analyzer + +The [`collation` Analyzer](../../index-and-search/analyzers.md#collation) lets +you adhere to the alphabetic order of a language in range queries. For example, +using the Swedish locale (`sv`), `å` goes after `z` and not near `a`, which +can impact queries. + +Sorting by the output of the `collation` Analyzer like +`SORT TOKENS(, ` did not produce meaningful results in +previous versions. Sorting the letters `å`, `a`, `b`, `z` resulted in the order +`b` `a` `å` `z` using an English locale (`en`) and `b` `å` `a` `z` using a +Swedish locale (`sv`). + +In v3.12, this now sorts properly to `a` `å` `b` `z` (English) and +`a` `b` `z` `å` (Swedish). This change can make queries behave differently +compared to v3.11 and older, and inverted indexes and Views using +`collation` Analyzers need to be recreated to ensure that they work correctly. + ## Control character escaping in audit log The audit log feature of the Enterprise Edition previously logged query strings From f98878b2872bda193d311918963cc4754e4b2fe2 Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Thu, 21 Mar 2024 12:29:03 +0100 Subject: [PATCH 3/7] Known issue: inverted indexes do not report building progress --- .../3.10/release-notes/version-3.10/known-issues-in-3-10.md | 1 + .../3.11/release-notes/version-3.10/known-issues-in-3-10.md | 1 + .../3.11/release-notes/version-3.11/known-issues-in-3-11.md | 1 + .../3.12/release-notes/version-3.10/known-issues-in-3-10.md | 1 + .../3.12/release-notes/version-3.11/known-issues-in-3-11.md | 1 + .../3.12/release-notes/version-3.12/known-issues-in-3-12.md | 1 + .../4.0/release-notes/version-3.10/known-issues-in-3-10.md | 1 + .../4.0/release-notes/version-3.11/known-issues-in-3-11.md | 1 + .../4.0/release-notes/version-3.12/known-issues-in-3-12.md | 1 + .../content/4.0/release-notes/version-4.0/known-issues-in-4-0.md | 1 + 10 files changed, 10 insertions(+) diff --git a/site/content/3.10/release-notes/version-3.10/known-issues-in-3-10.md b/site/content/3.10/release-notes/version-3.10/known-issues-in-3-10.md index c0a1dac4a2..286fba8a2b 100644 --- a/site/content/3.10/release-notes/version-3.10/known-issues-in-3-10.md +++ b/site/content/3.10/release-notes/version-3.10/known-issues-in-3-10.md @@ -68,3 +68,4 @@ Note that this page does not list all open issues. | **Date Added:** 2023-02-17
**Component:** ArangoDB Starter
**Deployment Mode:** All
**Description:** When using a Windows build with `netgo`, the `localhost` cannot be resolved.
**Affected Versions:** 3.9.8, 3.10.3
**Fixed in Versions:** 3.9.9, 3.10.4
**Reference:** [GT-330](https://arangodb.atlassian.net/browse/GT-330) (internal) | | **Date Added:** 2023-06-07
**Component:** ArangoSync
**Deployment Mode:** All
**Description:** In ArangoSync v2.18.0, synchronization may be interrupted with errors like "CloneDirectMQToken failed" due to network disturbances.
**Affected Versions:** 3.9.11, 3.10.7
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2023-06-16
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If more than a certain threshold of queries on the same Coordinator get into the shutdown networking code at the same time, all of them lock up and the Coordinator does not longer process requests.
**Affected Versions:** 3.9.x. 3.10.x
**Fixed in Versions:** 3.9.12, 3.10.8
**Reference:** [BTS-1486](https://arangodb.atlassian.net/browse/BTS-1486) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/3.11/release-notes/version-3.10/known-issues-in-3-10.md b/site/content/3.11/release-notes/version-3.10/known-issues-in-3-10.md index c0a1dac4a2..286fba8a2b 100644 --- a/site/content/3.11/release-notes/version-3.10/known-issues-in-3-10.md +++ b/site/content/3.11/release-notes/version-3.10/known-issues-in-3-10.md @@ -68,3 +68,4 @@ Note that this page does not list all open issues. | **Date Added:** 2023-02-17
**Component:** ArangoDB Starter
**Deployment Mode:** All
**Description:** When using a Windows build with `netgo`, the `localhost` cannot be resolved.
**Affected Versions:** 3.9.8, 3.10.3
**Fixed in Versions:** 3.9.9, 3.10.4
**Reference:** [GT-330](https://arangodb.atlassian.net/browse/GT-330) (internal) | | **Date Added:** 2023-06-07
**Component:** ArangoSync
**Deployment Mode:** All
**Description:** In ArangoSync v2.18.0, synchronization may be interrupted with errors like "CloneDirectMQToken failed" due to network disturbances.
**Affected Versions:** 3.9.11, 3.10.7
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2023-06-16
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If more than a certain threshold of queries on the same Coordinator get into the shutdown networking code at the same time, all of them lock up and the Coordinator does not longer process requests.
**Affected Versions:** 3.9.x. 3.10.x
**Fixed in Versions:** 3.9.12, 3.10.8
**Reference:** [BTS-1486](https://arangodb.atlassian.net/browse/BTS-1486) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/3.11/release-notes/version-3.11/known-issues-in-3-11.md b/site/content/3.11/release-notes/version-3.11/known-issues-in-3-11.md index 27c5ddbe45..8451eecb16 100644 --- a/site/content/3.11/release-notes/version-3.11/known-issues-in-3-11.md +++ b/site/content/3.11/release-notes/version-3.11/known-issues-in-3-11.md @@ -63,3 +63,4 @@ Note that this page does not list all open issues. | **Date Added:** 2023-05-25
**Component:** arangod
**Deployment Mode:** All
**Description:** When starting an async job by sending a request with the `x-arango-async: store` or `x-arango-async: keep` HTTP header **and** additionally sending the `accept-encoding: gzip` or `accept-encoding: deflate` HTTP header , the generated response may be compressed twice when fetching the async job's response later via the `/_api/job/` REST API.
**Affected Versions:** 3.11.0
**Fixed in Versions:** 3.11.1
**Reference:** [arangodb/arangodb#19103](https://github.com/arangodb/arangodb/pull/19103) | | **Date Added:** 2023-06-15
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** After an upgrade to 3.11.0 from an older version of ArangoDB with existing data, the following issue may occur after performing a HotBackup: `_pregel_queries` collections do not exist.
**Affected Versions:** 3.11.x
**Fixed in Versions:** -
**Reference:** [BTS-1462](https://arangodb.atlassian.net/browse/BTS-1462) (internal) | | **Date Added:** 2023-06-16
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If more than a certain threshold of queries on the same Coordinator get into the shutdown networking code at the same time, all of them lock up and the Coordinator does not longer process requests.
**Affected Versions:** 3.9.x. 3.10.x, 3.11.x
**Fixed in Versions:** 3.9.12, 3.10.8, 3.11.2
**Reference:** [BTS-1486](https://arangodb.atlassian.net/browse/BTS-1486) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13, 3.11.7
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/3.12/release-notes/version-3.10/known-issues-in-3-10.md b/site/content/3.12/release-notes/version-3.10/known-issues-in-3-10.md index c0a1dac4a2..286fba8a2b 100644 --- a/site/content/3.12/release-notes/version-3.10/known-issues-in-3-10.md +++ b/site/content/3.12/release-notes/version-3.10/known-issues-in-3-10.md @@ -68,3 +68,4 @@ Note that this page does not list all open issues. | **Date Added:** 2023-02-17
**Component:** ArangoDB Starter
**Deployment Mode:** All
**Description:** When using a Windows build with `netgo`, the `localhost` cannot be resolved.
**Affected Versions:** 3.9.8, 3.10.3
**Fixed in Versions:** 3.9.9, 3.10.4
**Reference:** [GT-330](https://arangodb.atlassian.net/browse/GT-330) (internal) | | **Date Added:** 2023-06-07
**Component:** ArangoSync
**Deployment Mode:** All
**Description:** In ArangoSync v2.18.0, synchronization may be interrupted with errors like "CloneDirectMQToken failed" due to network disturbances.
**Affected Versions:** 3.9.11, 3.10.7
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2023-06-16
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If more than a certain threshold of queries on the same Coordinator get into the shutdown networking code at the same time, all of them lock up and the Coordinator does not longer process requests.
**Affected Versions:** 3.9.x. 3.10.x
**Fixed in Versions:** 3.9.12, 3.10.8
**Reference:** [BTS-1486](https://arangodb.atlassian.net/browse/BTS-1486) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/3.12/release-notes/version-3.11/known-issues-in-3-11.md b/site/content/3.12/release-notes/version-3.11/known-issues-in-3-11.md index 27c5ddbe45..8451eecb16 100644 --- a/site/content/3.12/release-notes/version-3.11/known-issues-in-3-11.md +++ b/site/content/3.12/release-notes/version-3.11/known-issues-in-3-11.md @@ -63,3 +63,4 @@ Note that this page does not list all open issues. | **Date Added:** 2023-05-25
**Component:** arangod
**Deployment Mode:** All
**Description:** When starting an async job by sending a request with the `x-arango-async: store` or `x-arango-async: keep` HTTP header **and** additionally sending the `accept-encoding: gzip` or `accept-encoding: deflate` HTTP header , the generated response may be compressed twice when fetching the async job's response later via the `/_api/job/` REST API.
**Affected Versions:** 3.11.0
**Fixed in Versions:** 3.11.1
**Reference:** [arangodb/arangodb#19103](https://github.com/arangodb/arangodb/pull/19103) | | **Date Added:** 2023-06-15
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** After an upgrade to 3.11.0 from an older version of ArangoDB with existing data, the following issue may occur after performing a HotBackup: `_pregel_queries` collections do not exist.
**Affected Versions:** 3.11.x
**Fixed in Versions:** -
**Reference:** [BTS-1462](https://arangodb.atlassian.net/browse/BTS-1462) (internal) | | **Date Added:** 2023-06-16
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If more than a certain threshold of queries on the same Coordinator get into the shutdown networking code at the same time, all of them lock up and the Coordinator does not longer process requests.
**Affected Versions:** 3.9.x. 3.10.x, 3.11.x
**Fixed in Versions:** 3.9.12, 3.10.8, 3.11.2
**Reference:** [BTS-1486](https://arangodb.atlassian.net/browse/BTS-1486) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13, 3.11.7
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/3.12/release-notes/version-3.12/known-issues-in-3-12.md b/site/content/3.12/release-notes/version-3.12/known-issues-in-3-12.md index eadae745fe..84c5d89d30 100644 --- a/site/content/3.12/release-notes/version-3.12/known-issues-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/known-issues-in-3-12.md @@ -51,3 +51,4 @@ Note that this page does not list all open issues. | **Date Added:** 2019-04-03
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** Updating the properties of a collection in the cluster may return before the properties are updated consistently on all shards. This is especially visible when setting a schema for a collection with multiple shards, and then instantly starting to store non-conforming documents into the collection. These may be accepted until the properties change has been fully propagated to all shards.
**Affected Versions:** 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2021-04-07
**Component:** arangod
**Deployment Mode:** All
**Description:** The Batch API (HTTP endpoint `/_api/batch`) cannot be used in combination with Stream transactions to submit batched requests, because the required header `x-arango-trx-id` is not forwarded. It only processes `Content-Type` and `Content-Id`.
**Affected Versions:** 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** [arangodb/arangodb#13552](https://github.com/arangodb/arangodb/issues/13552) | | **Date Added:** 2022-09-29
**Component:** ArangoDB Starter
**Deployment Mode:** All
**Description:** The ArangoDB Starter may fail to pick a Docker container name from cgroups.
**Affected Versions:** 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** [GT-207](https://arangodb.atlassian.net/browse/GT-207) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13, 3.11.7, 3.12.x
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/4.0/release-notes/version-3.10/known-issues-in-3-10.md b/site/content/4.0/release-notes/version-3.10/known-issues-in-3-10.md index c0a1dac4a2..286fba8a2b 100644 --- a/site/content/4.0/release-notes/version-3.10/known-issues-in-3-10.md +++ b/site/content/4.0/release-notes/version-3.10/known-issues-in-3-10.md @@ -68,3 +68,4 @@ Note that this page does not list all open issues. | **Date Added:** 2023-02-17
**Component:** ArangoDB Starter
**Deployment Mode:** All
**Description:** When using a Windows build with `netgo`, the `localhost` cannot be resolved.
**Affected Versions:** 3.9.8, 3.10.3
**Fixed in Versions:** 3.9.9, 3.10.4
**Reference:** [GT-330](https://arangodb.atlassian.net/browse/GT-330) (internal) | | **Date Added:** 2023-06-07
**Component:** ArangoSync
**Deployment Mode:** All
**Description:** In ArangoSync v2.18.0, synchronization may be interrupted with errors like "CloneDirectMQToken failed" due to network disturbances.
**Affected Versions:** 3.9.11, 3.10.7
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2023-06-16
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If more than a certain threshold of queries on the same Coordinator get into the shutdown networking code at the same time, all of them lock up and the Coordinator does not longer process requests.
**Affected Versions:** 3.9.x. 3.10.x
**Fixed in Versions:** 3.9.12, 3.10.8
**Reference:** [BTS-1486](https://arangodb.atlassian.net/browse/BTS-1486) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/4.0/release-notes/version-3.11/known-issues-in-3-11.md b/site/content/4.0/release-notes/version-3.11/known-issues-in-3-11.md index 27c5ddbe45..8451eecb16 100644 --- a/site/content/4.0/release-notes/version-3.11/known-issues-in-3-11.md +++ b/site/content/4.0/release-notes/version-3.11/known-issues-in-3-11.md @@ -63,3 +63,4 @@ Note that this page does not list all open issues. | **Date Added:** 2023-05-25
**Component:** arangod
**Deployment Mode:** All
**Description:** When starting an async job by sending a request with the `x-arango-async: store` or `x-arango-async: keep` HTTP header **and** additionally sending the `accept-encoding: gzip` or `accept-encoding: deflate` HTTP header , the generated response may be compressed twice when fetching the async job's response later via the `/_api/job/` REST API.
**Affected Versions:** 3.11.0
**Fixed in Versions:** 3.11.1
**Reference:** [arangodb/arangodb#19103](https://github.com/arangodb/arangodb/pull/19103) | | **Date Added:** 2023-06-15
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** After an upgrade to 3.11.0 from an older version of ArangoDB with existing data, the following issue may occur after performing a HotBackup: `_pregel_queries` collections do not exist.
**Affected Versions:** 3.11.x
**Fixed in Versions:** -
**Reference:** [BTS-1462](https://arangodb.atlassian.net/browse/BTS-1462) (internal) | | **Date Added:** 2023-06-16
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If more than a certain threshold of queries on the same Coordinator get into the shutdown networking code at the same time, all of them lock up and the Coordinator does not longer process requests.
**Affected Versions:** 3.9.x. 3.10.x, 3.11.x
**Fixed in Versions:** 3.9.12, 3.10.8, 3.11.2
**Reference:** [BTS-1486](https://arangodb.atlassian.net/browse/BTS-1486) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13, 3.11.7
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/4.0/release-notes/version-3.12/known-issues-in-3-12.md b/site/content/4.0/release-notes/version-3.12/known-issues-in-3-12.md index eadae745fe..84c5d89d30 100644 --- a/site/content/4.0/release-notes/version-3.12/known-issues-in-3-12.md +++ b/site/content/4.0/release-notes/version-3.12/known-issues-in-3-12.md @@ -51,3 +51,4 @@ Note that this page does not list all open issues. | **Date Added:** 2019-04-03
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** Updating the properties of a collection in the cluster may return before the properties are updated consistently on all shards. This is especially visible when setting a schema for a collection with multiple shards, and then instantly starting to store non-conforming documents into the collection. These may be accepted until the properties change has been fully propagated to all shards.
**Affected Versions:** 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2021-04-07
**Component:** arangod
**Deployment Mode:** All
**Description:** The Batch API (HTTP endpoint `/_api/batch`) cannot be used in combination with Stream transactions to submit batched requests, because the required header `x-arango-trx-id` is not forwarded. It only processes `Content-Type` and `Content-Id`.
**Affected Versions:** 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** [arangodb/arangodb#13552](https://github.com/arangodb/arangodb/issues/13552) | | **Date Added:** 2022-09-29
**Component:** ArangoDB Starter
**Deployment Mode:** All
**Description:** The ArangoDB Starter may fail to pick a Docker container name from cgroups.
**Affected Versions:** 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** [GT-207](https://arangodb.atlassian.net/browse/GT-207) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13, 3.11.7, 3.12.x
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | diff --git a/site/content/4.0/release-notes/version-4.0/known-issues-in-4-0.md b/site/content/4.0/release-notes/version-4.0/known-issues-in-4-0.md index 3d02ff18d1..e9fae2009c 100644 --- a/site/content/4.0/release-notes/version-4.0/known-issues-in-4-0.md +++ b/site/content/4.0/release-notes/version-4.0/known-issues-in-4-0.md @@ -51,3 +51,4 @@ Note that this page does not list all open issues. | **Date Added:** 2019-04-03
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** Updating the properties of a collection in the cluster may return before the properties are updated consistently on all shards. This is especially visible when setting a schema for a collection with multiple shards, and then instantly starting to store non-conforming documents into the collection. These may be accepted until the properties change has been fully propagated to all shards.
**Affected Versions:** 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x, 4.0.x
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2021-04-07
**Component:** arangod
**Deployment Mode:** All
**Description:** The Batch API (HTTP endpoint `/_api/batch`) cannot be used in combination with Stream transactions to submit batched requests, because the required header `x-arango-trx-id` is not forwarded. It only processes `Content-Type` and `Content-Id`.
**Affected Versions:** 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x, 4.0.x
**Fixed in Versions:** -
**Reference:** [arangodb/arangodb#13552](https://github.com/arangodb/arangodb/issues/13552) | | **Date Added:** 2022-09-29
**Component:** ArangoDB Starter
**Deployment Mode:** All
**Description:** The ArangoDB Starter may fail to pick a Docker container name from cgroups.
**Affected Versions:** 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x, 4.0.x
**Fixed in Versions:** -
**Reference:** [GT-207](https://arangodb.atlassian.net/browse/GT-207) (internal) | +| **Date Added:** 2024-03-21
**Component:** arangod
**Deployment Mode:** All
**Description:** When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=&withHidden=true` don't return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed.
**Affected Versions:** 3.10.13, 3.11.17, 3.12.x, 4.0.x
**Fixed in Versions:** -
**Reference:** [BTS-1788](https://arangodb.atlassian.net/browse/BTS-1788) (internal) | From fb2dd9568b5450cc04398cc322143f7a27129aac Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Thu, 21 Mar 2024 12:55:40 +0100 Subject: [PATCH 4/7] Correct collation Analyzer breaking change --- .../incompatible-changes-in-3-12.md | 29 ++++++++++--------- .../incompatible-changes-in-3-12.md | 29 ++++++++++--------- 2 files changed, 32 insertions(+), 26 deletions(-) diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index 0cfffcbe88..271026680a 100644 --- a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -174,19 +174,22 @@ instead in most cases, and in some cases AQL can be sufficient. The [`collation` Analyzer](../../index-and-search/analyzers.md#collation) lets you adhere to the alphabetic order of a language in range queries. For example, -using the Swedish locale (`sv`), `å` goes after `z` and not near `a`, which -can impact queries. - -Sorting by the output of the `collation` Analyzer like -`SORT TOKENS(, ` did not produce meaningful results in -previous versions. Sorting the letters `å`, `a`, `b`, `z` resulted in the order -`b` `a` `å` `z` using an English locale (`en`) and `b` `å` `a` `z` using a -Swedish locale (`sv`). - -In v3.12, this now sorts properly to `a` `å` `b` `z` (English) and -`a` `b` `z` `å` (Swedish). This change can make queries behave differently -compared to v3.11 and older, and inverted indexes and Views using -`collation` Analyzers need to be recreated to ensure that they work correctly. +using a Swedish locale (`sv`), the sorting order is `å` after `z`, whereas using +an English locale (`en`), `å` is preceded by `a`. This impacts queries with +`SEARCH` expressions like `doc.text < "c"`, excluding `å` when using the Swedish +locale. + +ArangoDB 3.12 bundles an upgraded version of the ICU library. It is used for +Unicode character handling including text sorting. Because of changes in ICU, +data produced by the `collation` Analyzer in previous versions is not compatible +with ArangoDB v3.12. You need to **recreate inverted indexes and Views that use +`collation` Analyzers** to ensure that they work correctly. Otherwise, +range queries involving the `collation` Analyzers and indexes created in v3.11 +or older versions may behave in unpredicted ways. + +Note that sorting by the output of the `collation` Analyzer like +`SORT TOKENS(, ` is still not a supported feature and +doesn't produce meaningful results. ## Control character escaping in audit log diff --git a/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md index 0cfffcbe88..271026680a 100644 --- a/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -174,19 +174,22 @@ instead in most cases, and in some cases AQL can be sufficient. The [`collation` Analyzer](../../index-and-search/analyzers.md#collation) lets you adhere to the alphabetic order of a language in range queries. For example, -using the Swedish locale (`sv`), `å` goes after `z` and not near `a`, which -can impact queries. - -Sorting by the output of the `collation` Analyzer like -`SORT TOKENS(, ` did not produce meaningful results in -previous versions. Sorting the letters `å`, `a`, `b`, `z` resulted in the order -`b` `a` `å` `z` using an English locale (`en`) and `b` `å` `a` `z` using a -Swedish locale (`sv`). - -In v3.12, this now sorts properly to `a` `å` `b` `z` (English) and -`a` `b` `z` `å` (Swedish). This change can make queries behave differently -compared to v3.11 and older, and inverted indexes and Views using -`collation` Analyzers need to be recreated to ensure that they work correctly. +using a Swedish locale (`sv`), the sorting order is `å` after `z`, whereas using +an English locale (`en`), `å` is preceded by `a`. This impacts queries with +`SEARCH` expressions like `doc.text < "c"`, excluding `å` when using the Swedish +locale. + +ArangoDB 3.12 bundles an upgraded version of the ICU library. It is used for +Unicode character handling including text sorting. Because of changes in ICU, +data produced by the `collation` Analyzer in previous versions is not compatible +with ArangoDB v3.12. You need to **recreate inverted indexes and Views that use +`collation` Analyzers** to ensure that they work correctly. Otherwise, +range queries involving the `collation` Analyzers and indexes created in v3.11 +or older versions may behave in unpredicted ways. + +Note that sorting by the output of the `collation` Analyzer like +`SORT TOKENS(, ` is still not a supported feature and +doesn't produce meaningful results. ## Control character escaping in audit log From 75ca28d5cbd72d120c24fc94f0e8277aecdfec9e Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Thu, 21 Mar 2024 12:59:42 +0100 Subject: [PATCH 5/7] README: Should always use a release version branch From 3.12 onward, there is no 3.12 version branch but only release branches 3.12.0 etc., but for 3.10 and 3.11, we should also use the release branch to avoid discrepancies between the release build and the version branch HEAD --- CIRCLECI.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CIRCLECI.md b/CIRCLECI.md index 1f2d356cb0..13b44ac15a 100644 --- a/CIRCLECI.md +++ b/CIRCLECI.md @@ -172,7 +172,7 @@ steps below. | string | `workflow` | `release` | | string | `release-type` | `arangodb` | | string | `docs-version` | `3.11` (the docs version folder) | -| string | `arangodb-branch` | `3.11` (the arangodb/arangodb branch to compile) | +| string | `arangodb-branch` | `3.11.4` (the arangodb/arangodb branch to compile) | | string | `arangodb-version` | `3.11.4` (updates the `versions.yaml` file) | The ArangoDB release workflow includes the following jobs: From f2c176374cf9c393f35ed810e3c7813c2f9aee27 Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Thu, 21 Mar 2024 13:08:03 +0100 Subject: [PATCH 6/7] Define what hidden indexes are --- site/content/3.10/develop/http-api/indexes/_index.md | 3 ++- .../index-and-search/indexing/working-with-indexes/_index.md | 3 ++- site/content/3.11/develop/http-api/indexes/_index.md | 3 ++- .../index-and-search/indexing/working-with-indexes/_index.md | 3 ++- site/content/3.12/develop/http-api/indexes/_index.md | 3 ++- .../index-and-search/indexing/working-with-indexes/_index.md | 3 ++- site/content/4.0/develop/http-api/indexes/_index.md | 3 ++- .../index-and-search/indexing/working-with-indexes/_index.md | 3 ++- 8 files changed, 16 insertions(+), 8 deletions(-) diff --git a/site/content/3.10/develop/http-api/indexes/_index.md b/site/content/3.10/develop/http-api/indexes/_index.md index 581079526c..fd68c4db81 100644 --- a/site/content/3.10/develop/http-api/indexes/_index.md +++ b/site/content/3.10/develop/http-api/indexes/_index.md @@ -54,7 +54,8 @@ paths: in: query required: false description: | - Whether to include hidden indexes in the result. + Whether to include hidden indexes in the result. Internal indexes + and ones that are currently built in the background are hidden. schema: type: boolean responses: diff --git a/site/content/3.10/index-and-search/indexing/working-with-indexes/_index.md b/site/content/3.10/index-and-search/indexing/working-with-indexes/_index.md index f9da2e7de1..e7377d2338 100644 --- a/site/content/3.10/index-and-search/indexing/working-with-indexes/_index.md +++ b/site/content/3.10/index-and-search/indexing/working-with-indexes/_index.md @@ -62,7 +62,8 @@ You can set the following parameters: - `withStats` (boolean, _optional_): whether to include index figures and estimates in the result. Default: `false` - `withHidden` (boolean, _optional_): whether to include hidden indexes in the - result. Default: `false` + result. Internal indexes and ones that are currently built in the background + are hidden. Default: `false` The `indexes()` method is an alias for `getIndexes()`. diff --git a/site/content/3.11/develop/http-api/indexes/_index.md b/site/content/3.11/develop/http-api/indexes/_index.md index 581079526c..fd68c4db81 100644 --- a/site/content/3.11/develop/http-api/indexes/_index.md +++ b/site/content/3.11/develop/http-api/indexes/_index.md @@ -54,7 +54,8 @@ paths: in: query required: false description: | - Whether to include hidden indexes in the result. + Whether to include hidden indexes in the result. Internal indexes + and ones that are currently built in the background are hidden. schema: type: boolean responses: diff --git a/site/content/3.11/index-and-search/indexing/working-with-indexes/_index.md b/site/content/3.11/index-and-search/indexing/working-with-indexes/_index.md index 8ce8a1e5df..8bd2662523 100644 --- a/site/content/3.11/index-and-search/indexing/working-with-indexes/_index.md +++ b/site/content/3.11/index-and-search/indexing/working-with-indexes/_index.md @@ -62,7 +62,8 @@ You can set the following parameters: - `withStats` (boolean, _optional_): whether to include index figures and estimates in the result. Default: `false` - `withHidden` (boolean, _optional_): whether to include hidden indexes in the - result. Default: `false` + result. Internal indexes and ones that are currently built in the background + are hidden. Default: `false` The `indexes()` method is an alias for `getIndexes()`. diff --git a/site/content/3.12/develop/http-api/indexes/_index.md b/site/content/3.12/develop/http-api/indexes/_index.md index 581079526c..fd68c4db81 100644 --- a/site/content/3.12/develop/http-api/indexes/_index.md +++ b/site/content/3.12/develop/http-api/indexes/_index.md @@ -54,7 +54,8 @@ paths: in: query required: false description: | - Whether to include hidden indexes in the result. + Whether to include hidden indexes in the result. Internal indexes + and ones that are currently built in the background are hidden. schema: type: boolean responses: diff --git a/site/content/3.12/index-and-search/indexing/working-with-indexes/_index.md b/site/content/3.12/index-and-search/indexing/working-with-indexes/_index.md index 3831eaca00..5dce750fff 100644 --- a/site/content/3.12/index-and-search/indexing/working-with-indexes/_index.md +++ b/site/content/3.12/index-and-search/indexing/working-with-indexes/_index.md @@ -62,7 +62,8 @@ You can set the following parameters: - `withStats` (boolean, _optional_): whether to include index figures and estimates in the result. Default: `false` - `withHidden` (boolean, _optional_): whether to include hidden indexes in the - result. Default: `false` + result. Internal indexes and ones that are currently built in the background + are hidden. Default: `false` The `indexes()` method is an alias for `getIndexes()`. diff --git a/site/content/4.0/develop/http-api/indexes/_index.md b/site/content/4.0/develop/http-api/indexes/_index.md index 581079526c..fd68c4db81 100644 --- a/site/content/4.0/develop/http-api/indexes/_index.md +++ b/site/content/4.0/develop/http-api/indexes/_index.md @@ -54,7 +54,8 @@ paths: in: query required: false description: | - Whether to include hidden indexes in the result. + Whether to include hidden indexes in the result. Internal indexes + and ones that are currently built in the background are hidden. schema: type: boolean responses: diff --git a/site/content/4.0/index-and-search/indexing/working-with-indexes/_index.md b/site/content/4.0/index-and-search/indexing/working-with-indexes/_index.md index 3831eaca00..5dce750fff 100644 --- a/site/content/4.0/index-and-search/indexing/working-with-indexes/_index.md +++ b/site/content/4.0/index-and-search/indexing/working-with-indexes/_index.md @@ -62,7 +62,8 @@ You can set the following parameters: - `withStats` (boolean, _optional_): whether to include index figures and estimates in the result. Default: `false` - `withHidden` (boolean, _optional_): whether to include hidden indexes in the - result. Default: `false` + result. Internal indexes and ones that are currently built in the background + are hidden. Default: `false` The `indexes()` method is an alias for `getIndexes()`. From c3e04545cb82aa78e4cb7495a5b84d9bd4b36329 Mon Sep 17 00:00:00 2001 From: Simran Date: Thu, 21 Mar 2024 13:25:11 +0100 Subject: [PATCH 7/7] Apply suggestions from code review (typo fix) Co-authored-by: Valery Mironov <32071355+MBkkt@users.noreply.github.com> --- .../release-notes/version-3.12/incompatible-changes-in-3-12.md | 2 +- .../release-notes/version-3.12/incompatible-changes-in-3-12.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index 271026680a..b92182290d 100644 --- a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -188,7 +188,7 @@ range queries involving the `collation` Analyzers and indexes created in v3.11 or older versions may behave in unpredicted ways. Note that sorting by the output of the `collation` Analyzer like -`SORT TOKENS(, ` is still not a supported feature and +`SORT TOKENS(, )` is still not a supported feature and doesn't produce meaningful results. ## Control character escaping in audit log diff --git a/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md index 271026680a..b92182290d 100644 --- a/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -188,7 +188,7 @@ range queries involving the `collation` Analyzers and indexes created in v3.11 or older versions may behave in unpredicted ways. Note that sorting by the output of the `collation` Analyzer like -`SORT TOKENS(, ` is still not a supported feature and +`SORT TOKENS(, )` is still not a supported feature and doesn't produce meaningful results. ## Control character escaping in audit log