Merge branch 'main' of https://github.com/arangodb/docs into DOC-347

Author: Simran-B

3.10/analyzers.md

@@ -331,9 +331,9 @@ token, i.e. case conversion and accent removal.
 The *properties* allowed for this Analyzer are an object with the following
 attributes:
 
-- `locale` (string): a locale in the format `language[_COUNTRY]`
-  (square brackets denote optional parts), e.g. `"de"` or `"en_US"`. See the
-  [ICU Documentation](https://unicode-org.github.io/icu/userguide/locale/){:target="_blank"}
+- `locale` (string): a locale in the format `language[_COUNTRY][_VARIANT]`
+  (square brackets denote optional parts), e.g. `"de"`, `"en_US"`, or `"es__TRADITIONAL"`.
+  See the [ICU Documentation](https://unicode-org.github.io/icu/userguide/locale/){:target="_blank"}
   for details. The locale is forwarded to ICU without checks.
   An invalid locale does not prevent the creation of the Analyzer.
   Also see [Supported Languages](#supported-languages).
@@ -496,9 +496,9 @@ case conversion and accent removal.
 The *properties* allowed for this Analyzer are an object with the following
 attributes:
 
-- `locale` (string): a locale in the format `language[_COUNTRY]`
-  (square brackets denote optional parts), e.g. `"de"` or `"en_US"`. See the
-  [ICU Documentation](https://unicode-org.github.io/icu/userguide/locale/){:target="_blank"}
+- `locale` (string): a locale in the format `language[_COUNTRY][_VARIANT]`
+  (square brackets denote optional parts), e.g. `"de"`, `"en_US"`, or `"es__TRADITIONAL"`.
+  See the [ICU Documentation](https://unicode-org.github.io/icu/userguide/locale/){:target="_blank"}
   for details. The locale is forwarded to ICU without checks.
   An invalid locale does not prevent the creation of the Analyzer.
   Also see [Supported Languages](#supported-languages).
@@ -635,8 +635,8 @@ The *properties* allowed for this Analyzer are an object with the following
 attributes:
 
 - `locale` (string): a locale in the format
-  `language[_COUNTRY][_VARIANT][@keywords]` (square brackets denote optional
-  parts), e.g. `"de"`, `"en_US"`, or `fr@collation=phonebook`. See the
+  `language[_COUNTRY][_VARIANT][@keywords]` (square brackets denote optional parts),
+  e.g. `"de"`, `"en_US"`, `"es__TRADITIONAL"`, or `fr@collation=phonebook`. See the
   [ICU Documentation](https://unicode-org.github.io/icu/userguide/locale/){:target="_blank"}
   for details. The locale is forwarded to ICU without checks.
   An invalid locale does not prevent the creation of the Analyzer.
@@ -1267,6 +1267,39 @@ attributes:
   - `maxCells` (number, _optional_): maximum number of S2 cells (default: 20)
   - `minLevel` (number, _optional_): the least precise S2 level (default: 4)
   - `maxLevel` (number, _optional_): the most precise S2 level (default: 23)
+- `legacy` (boolean, _optional_):
+  This option controls how GeoJSON Polygons are interpreted (introduced in v3.10.5).
+  Also see [Legacy Polygons](indexing-geo.html#legacy-polygons) and
+  [GeoJSON interpretation](indexing-geo.html#geojson-interpretation).
+
+  - If `legacy` is `true`, the smaller of the two regions defined by a
+    linear ring is interpreted as the interior of the ring and a ring can at most
+    enclose half the Earth's surface.
+  - If `legacy` is `false`, the area to the left of the boundary ring's
+    path is considered to be the interior and a ring can enclose the entire
+    surface of the Earth.
+
+  The default is `false`.
+
+  {% hint 'warning' %}
+  If you use `geojson` Analyzers and upgrade from a version below 3.10 to a
+  version of 3.10 or higher, the interpretation of GeoJSON Polygons changes.
+
+  If you have polygons in your data that mean to refer to a relatively small
+  region but have the boundary running clockwise around the intended interior,
+  they are interpreted as intended prior to 3.10, but from 3.10 onward, they are
+  interpreted as "the other side" of the boundary.
+
+  Whether a clockwise boundary specifies the complement of the small region
+  intentionally or not cannot be determined automatically. Please test the new
+  behavior manually.
+
+  If you require the old behavior, upgrade to at least 3.10.5, drop your
+  `geojson` Analyzers, and create new ones with `legacy` set to `true`.
+  If these Analyzers are used in `arangosearch` Views, then they need to be
+  dropped as well before dropping the Analyzers, and recreated after creating
+  the new Analyzers.
+  {% endhint %}
 
 **Examples**
 

3.10/aql/examples-combining-graph-traversals.md

@@ -16,7 +16,7 @@ We use [the city graph](../graphs.html#the-city-graph) and its geo indexes:
 {% arangoshexample examplevar="examplevar" script="script" result="result" %}
     @startDocuBlockInline COMBINING_GRAPH_01_create_graph
     @EXAMPLE_ARANGOSH_OUTPUT{COMBINING_GRAPH_01_create_graph}
-    var examples = require("@arangodb/graph-examples/example-graph.js");
+    var examples = require("@arangodb/graph-examples/example-graph");
     var g = examples.loadGraph("routeplanner");
     ~examples.dropGraph("routeplanner");
     @END_EXAMPLE_ARANGOSH_OUTPUT
@@ -112,7 +112,7 @@ Finally, we clean up again:
 {% arangoshexample examplevar="examplevar" script="script" result="result" %}
     @startDocuBlockInline COMBINING_GRAPH_06_cleanup
     @EXAMPLE_ARANGOSH_OUTPUT{COMBINING_GRAPH_06_cleanup}
-    ~var examples = require("@arangodb/graph-examples/example-graph.js");
+    ~var examples = require("@arangodb/graph-examples/example-graph");
     ~var g = examples.loadGraph("routeplanner");
     examples.dropGraph("routeplanner");
     @END_EXAMPLE_ARANGOSH_OUTPUT