restructure

arangodb · Simran-B · Oct 12, 2021 · Aug 3, 2021 · Aug 3, 2021 · Aug 3, 2021
commit fee86c29eec40ec4a25959724e0d7013074ed17d
diff --git a/3.9/release-notes-api-changes39.md b/3.9/release-notes-api-changes39.md
@@ -9,6 +9,53 @@ This document summarizes the HTTP API changes and other API changes in ArangoDB
 The target audience for this document are developers who maintain drivers and
 integrations for ArangoDB 3.9.
 
+## HTTP RESTful API
+
+### GRAPH API (Gharial)
+
+The following changes affect the behavior of the RESTful graph APIs at
+endpoints starting with path `/_api/gharial/`:
+
+The options object now supports a new field: `satellites`, when creating a graph (POST).
+The value of satellites is optional. In case it is defined, it needs to be an array
+of collection names. Each defined collection name must be a string. This value is
+only valid in case of SmartGraphs (Enterprise-Only). In a community based graph it
+will be ignored.
+
+Using `satellites` during SmartGraph creation will result in a Hybrid Smart Graph.
+Using `satellites` during Disjoint SmartGraph creation will result in a Hybrid
+Disjoint SmartGraph.
+
+Hybrid (Disjoint) SmartGraphs are capable of having Satellite collections in their
+graph definitions. If a collection is found in `satellites` and they are also being
+used in the graph definition itself (e.g. EdgeDefinition), this collection will be
+created as a satellite collection. Hybrid (Disjoint) Smart Graphs are then capable
+of executing all type of graph queries between the regular SmartCollections and
+Satellite collections.
+
+The following changes affect the behavior of the RESTful graph APIs at
+endpoints starting with path `/_api/gharial/{graph}/edge`:
+
+Creating and modifying a new edge definition (POST / PUT):
+Added new optional options object. This was not available in previous ArangoDB
83A7
+versions. The options object currently can contain a field called `satellites`.
+The field must be an array and contain collection name(s) written down as strings.
+If an EdgeDefinition does contain a collection name, which is also defined in
+the satellites option entry, it will be created as a Satellite collection.
+Otherwise, it will be ignored. This option only takes effect using SmartGraphs.
+
+The following changes affect the behavior of the RESTful graph APIs at
+endpoints starting with path `/_api/gharial/{graph}/vertex`:
+
+Creating a new vertex collection (POST):
+Added new optional options object. This was not available in previous ArangoDB
+versions. The options object currently can contain a field called `satellites`.
+The field must be an array and contain collection name(s) written down as strings.
+If the vertex to add is also defined in the satellites option entry, it will be
+created as a Satellite collection. Otherwise, it will be ignored. This option
+only takes effect using SmartGraphs.
+
+
 ### Privilege changes
 
 ### Endpoint return value changes
@@ -107,3 +154,5 @@ The field must be an array and contain collection name(s) written down as string
 If the vertex to add is also defined in the satellites option entry, it will be
 created as a Satellite collection. Otherwise, it will be ignored. This option
 only takes effect using SmartGraphs.
+
+## JavaScript API