Merge branch 'main' of https://github.com/arangodb/docs-hugo into oem2

Author: Simran-B

.circleci/base_config.yml

@@ -168,7 +168,8 @@ commands:
       - run:
           name: Create archive of compiled instance
           command: |
-            wget -O build/bin/arangodb https://github.com/arangodb-helper/arangodb/releases/download/0.15.8/arangodb-linux-amd64
+            STARTER_VERSION=$(awk -F\" '/^STARTER_REV/ {print $2}' VERSIONS)
+            curl -L -o build/bin/arangodb "https://github.com/arangodb-helper/arangodb/releases/download/$STARTER_VERSION/arangodb-linux-amd64"
             chmod +x build/bin/arangodb
             tar -czf install.tar.gz build/ scripts/ js/ etc/ utils/ enterprise/
       - run:

.circleci/generate_config.py

@@ -144,7 +144,7 @@ def workflow_generate(config):
                     compileJob["compile-linux"]["build-image"] = "arangodb/build-alpine-x86_64:3.16-gcc11.2-openssl1.1.1s"
                 else:
                     compileJob["compile-linux"]["build-image"] = "arangodb/ubuntubuildarangodb-311:6" # clang-16
-            else: # build image for 3.12.6 and devel as of 2025-12-03
+            else: # build image for 3.12.7 and devel as of 2025-12-11
                 compileJob["compile-linux"]["build-image"] = "arangodb/ubuntubuildarangodb-devel:18" # clang-19
 
         print(f"compileJob = {compileJob}")
@@ -257,7 +257,7 @@ def workflow_release_arangodb(config):
             compileJob["compile-linux"]["build-image"] = "arangodb/build-alpine-x86_64:3.16-gcc11.2-openssl1.1.1s"
         else:
             compileJob["compile-linux"]["build-image"] = "arangodb/ubuntubuildarangodb-311:6" # clang-16
-    else: # build image for 3.12.6 and devel as of 2025-12-03
+    else: # build image for 3.12.7 and devel as of 2024-12-11
         compileJob["compile-linux"]["build-image"] = "arangodb/ubuntubuildarangodb-devel:18" # clang-19
 
     config["jobs"]["compile-linux"]["steps"].append({

site/content/ai-suite/release-notes.md

@@ -10,7 +10,7 @@ The AI Suite is available as a pre-release. To get exclusive early access,
 [get in touch](https://arango.ai/ai-preview/) with the Arango team.
 {{< /tip >}}
 
-## October 2024 (pre-release)
+## October 2025 (pre-release)
 
 This release introduces new features and enhancements to the AI Suite components.
 See also the [Arango Data Platform Release Notes](../data-platform/release-notes.md).
@@ -41,7 +41,7 @@ LLM-powered answers to general questions.
 You can generate AQL queries from natural language directly in the Query Editor using the
 [AQLizer](aqlizer.md) mode. More advanced features are available via the API.
 
-## July 2024 (pre-release)
+## July 2025 (pre-release)
 
 This release marks the initial internal launch of the AI Suite with the following
 components. For Data Platform features in this release, see

site/content/arangodb/3.12/develop/http-api/indexes/inverted.md

@@ -561,12 +561,14 @@ paths:
                         upon several possible configurable formulas as defined by their types.
                         The supported types are:
 
-                        - `"tier"`: consolidate based on segment byte size and live
+                        - `"tier"`: consolidate based on segment byte size skew and live
                           document count as dictated by the customization attributes.
                       type: string
                       default: tier
                     segmentsBytesFloor:
                       description: |
+                        This option is only available up to v3.12.6:
+
                         Defines the value (in bytes) to treat all smaller segments as equal for
                         consolidation selection.
                       type: integer
@@ -578,21 +580,86 @@ paths:
                       default: 8589934592
                     segmentsMax:
                       description: |
+                        This option is only available up to v3.12.6:
+
                         The maximum number of segments that are evaluated as candidates for
                         consolidation.
                       type: integer
                       default: 200
                     segmentsMin:
                       description: |
+                        This option is only available up to v3.12.6:
+
                         The minimum number of segments that are evaluated as candidates for
                         consolidation.
                       type: integer
                       default: 50
                     minScore:
                       description: |
+                        This option is only available up to v3.12.6:
+
                         Filter out consolidation candidates with a score less than this.
                       type: integer
                       default: 0
+                    maxSkewThreshold:
+                      description: |
+                        This option is available from v3.12.7 onward:
+
+                        The skew describes how much segment files vary in file size. It is a number
+                        between `0.0` and `1.0` and is calculated by dividing the largest file size
+                        of a set of segment files by the total size. For example, the skew of a
+                        200 MiB, 300 MiB, and 500 MiB segment file is `0.5` (`500 / 1000`).
+
+                        A large `maxSkewThreshold` value allows merging large segment files with
+                        smaller ones, consolidation occurs more frequently, and there are fewer
+                        segment files on disk at all times. While this may potentially improve the
+                        read performance and use fewer file descriptors, frequent consolidations
+                        cause a higher write load and thus a higher write amplification.
+                        
+                        On the other hand, a small threshold value triggers the consolidation only
+                        when there are a large number of segment files that don't vary in size a lot.
+                        Consolidation occurs less frequently, reducing the write amplification, but
+                        it can result in a greater number of segment files on disk.
+
+                        Multiple combinations of candidate segments are checked and the one with
+                        the lowest skew value is selected for consolidation. The selection process
+                        picks the greatest number of segments that together have the lowest skew value
+                        while ensuring that the size of the new consolidated segment remains under
+                        the configured `segmentsBytesMax`.
+                      type: number
+                      minimum: 0.0
+                      maximum: 1.0
+                      default: 0.4
+                    minDeletionRatio:
+                      description: |
+                        This option is available from v3.12.7 onward:
+
+                        The `minDeletionRatio` represents the minimum required deletion ratio
+                        in one or more segments to perform a cleanup of those segments.
+                        It is a number between `0.0` and `1.0`.
+
+                        The deletion ratio is the percentage of deleted documents across one or
+                        more segment files and is calculated by dividing the number of deleted
+                        documents by the total number of documents in a segment or a group of
+                        segments. For example, if there is a segment with 1000 documents of which
+                        300 are deleted and another segment with 1000 documents of which 700 are
+                        deleted, the deletion ratio is `0.5` (50%, calculated as `1000 / 2000`).
+
+                        The `minDeletionRatio` threshold must be carefully selected. A smaller
+                        value leads to earlier cleanup of deleted documents from segments and
+                        thus reclamation of disk space but it generates a higher write load.
+                        A very large value lowers the write amplification but at the same time
+                        the system can be left with a large number of segment files with a high
+                        percentage of deleted documents that occupy disk space unnecessarily.
+
+                        During cleanup, the segment files are first arranged in decreasing
+                        order of their individual deletion ratios. Then the largest subset of
+                        segments whose collective deletion ratio is greater than or equal to
+                        `minDeletionRatio` is picked.
+                      type: number
+                      minimum: 0.0
+                      maximum: 1.0
+                      default: 0.5
                 writebufferIdle:
                   description: |
                     Maximum number of writers (segments) cached in the pool

site/content/arangodb/3.12/develop/http-api/indexes/vector.md

@@ -65,6 +65,23 @@ paths:
                   maxItems: 1
                   items:
                     type: string
+                storedValues:
+                  description: |
+                    Store additional attributes in the index (introduced in v3.12.7).
+                    Unlike with other index types, this is not for covering projections
+                    with the index but for adding attributes that you filter on.
+                    This lets you make the lookup in the vector index more efficient
+                    because it avoids materializing documents twice, once for the
+                    filtering and once for the matches.
+
+                    The maximum number of attributes that you can use in `storedValues` is 32.
+                  type: array
+                  uniqueItems: true
+                  items:
+                    description: |
+                      A list of attribute paths. The `.` character denotes sub-attributes.
+                      type: string
+                    type: string
                 sparse:
                   description: |
                     Whether to create a sparse index that excludes documents with