DOC-614 | Adjustable writeConcern (#465)

* writeConcern adjustable together with distributeShardsLike

* Adjust descriptions, retrofitting 3.10 and 3.11 APIs

Author: Simran-B

site/content/3.10/develop/http-api/collections.md

@@ -288,8 +288,14 @@ paths:
                       in the cluster, a shard refuses to write. Writes to shards with enough
                       up-to-date copies succeed at the same time, however. The value of
                       `writeConcern` cannot be greater than `replicationFactor`.
+
+                      If `distributeShardsLike` is set, the `writeConcern`
+                      is that of the prototype collection.
                       For SatelliteCollections, the `writeConcern` is automatically controlled to
-                      equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                      equal the number of DB-Servers and has a value of `0`.
+                      Otherwise, the default value is controlled by the current database's
+                      default `writeConcern`, which uses the `--cluster.write-concern`
+                      startup option as default, which defaults to `1`. _(cluster only)_
                     type: integer
                   shardingStrategy:
                     description: |
@@ -306,7 +312,7 @@ paths:
                   distributeShardsLike:
                     description: |
                       The name of another collection. This collection uses the `replicationFactor`,
-                      `numberOfShards` and `shardingStrategy` properties of the other collection and
+                      `numberOfShards`, `shardingStrategy`, and `writeConcern` properties of the other collection and
                       the shards of this collection are distributed in the same way as the shards of
                       the other collection.
                     type: string
@@ -1180,13 +1186,19 @@ paths:
                     in the cluster, a shard refuses to write. Writes to shards with enough
                     up-to-date copies succeed at the same time, however. The value of
                     `writeConcern` cannot be greater than `replicationFactor`.
+
+                    If `distributeShardsLike` is set, the `writeConcern`
+                    is that of the prototype collection.
                     For SatelliteCollections, the `writeConcern` is automatically controlled to
-                    equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                    equal the number of DB-Servers and has a value of `0`.
+                    Otherwise, the default value is controlled by the current database's
+                    default `writeConcern`, which uses the `--cluster.write-concern`
+                    startup option as default, which defaults to `1`. _(cluster only)_
                   type: integer
                 shardingStrategy:
                   description: |
                     This attribute specifies the name of the sharding strategy to use for
-                    the collection. Since ArangoDB 3.4 there are different sharding strategies
+                    the collection. There are different sharding strategies
                     to select from when creating a new collection. The selected `shardingStrategy`
                     value remains fixed for the collection and cannot be changed afterwards.
                     This is important to make the collection keep its sharding settings and
@@ -1217,7 +1229,7 @@ paths:
                 distributeShardsLike:
                   description: |
                     The name of another collection. If this property is set in a cluster, the
-                    collection copies the `replicationFactor`, `numberOfShards` and `shardingStrategy`
+                    collection copies the `replicationFactor`, `numberOfShards`, `shardingStrategy`, and `writeConcern`
                     properties from the specified collection (referred to as the _prototype collection_)
                     and distributes the shards of this collection in the same way as the shards of
                     the other collection. In an Enterprise Edition cluster, this data co-location is
@@ -1435,8 +1447,14 @@ paths:
                       in the cluster, a shard refuses to write. Writes to shards with enough
                       up-to-date copies succeed at the same time, however. The value of
                       `writeConcern` cannot be greater than `replicationFactor`.
+
+                      If `distributeShardsLike` is set, the `writeConcern`
+                      is that of the prototype collection.
                       For SatelliteCollections, the `writeConcern` is automatically controlled to
-                      equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                      equal the number of DB-Servers and has a value of `0`.
+                      Otherwise, the default value is controlled by the current database's
+                      default `writeConcern`, which uses the `--cluster.write-concern`
+                      startup option as default, which defaults to `1`. _(cluster only)_
                     type: integer
                   shardingStrategy:
                     description: |
@@ -1453,7 +1471,7 @@ paths:
                   distributeShardsLike:
                     description: |
                       The name of another collection. This collection uses the `replicationFactor`,
-                      `numberOfShards` and `shardingStrategy` properties of the other collection and
+                      `numberOfShards`, `shardingStrategy`, and `writeConcern` properties of the other collection and
                       the shards of this collection are distributed in the same way as the shards of
                       the other collection.
                     type: string
@@ -2120,8 +2138,14 @@ paths:
                     in the cluster, a shard refuses to write. Writes to shards with enough
                     up-to-date copies succeed at the same time, however. The value of
                     `writeConcern` cannot be greater than `replicationFactor`.
+
+                    If `distributeShardsLike` is set, the `writeConcern`
+                    is that of the prototype collection.
                     For SatelliteCollections, the `writeConcern` is automatically controlled to
-                    equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                    equal the number of DB-Servers and has a value of `0`.
+                    Otherwise, the default value is controlled by the current database's
+                    default `writeConcern`, which uses the `--cluster.write-concern`
+                    startup option as default, which defaults to `1`. _(cluster only)_
                   type: integer
       responses:
         '400':

site/content/3.10/develop/http-api/databases.md

@@ -240,8 +240,13 @@ paths:
                         in the cluster, a shard refuses to write. Writes to shards with enough
                         up-to-date copies succeed at the same time, however. The value of
                         `writeConcern` cannot be greater than `replicationFactor`.
+
+                        If `distributeShardsLike` is set, the `writeConcern`
+                        is that of the prototype collection.
                         For SatelliteCollections, the `writeConcern` is automatically controlled to
-                        equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                        equal the number of DB-Servers and has a value of `0`.
+                        Otherwise, the default value is controlled by the `--cluster.write-concern`
+                        startup option, which defaults to `1`. _(cluster only)_
                       type: number
                 users:
                   description: |

site/content/3.10/develop/javascript-api/@arangodb/collection-object.md

@@ -266,7 +266,7 @@ In a cluster setup, the result also contains the following attributes:
 
 - `distributeShardsLike` (string):
   The name of another collection. This collection uses the `replicationFactor`,
-  `numberOfShards` and `shardingStrategy` properties of the other collection and
+  `numberOfShards`, `shardingStrategy`, `writeConcern` properties of the other collection and
   the shards of this collection are distributed in the same way as the shards of
   the other collection.
 

site/content/3.10/develop/javascript-api/@arangodb/db-object.md

@@ -392,7 +392,7 @@ error is thrown. For information about the naming constraints for collections, s
 
 - `distributeShardsLike` (string, _optional_, default: `""`):
   The name of another collection. If this property is set in a cluster, the
-  collection copies the `replicationFactor`, `numberOfShards` and `shardingStrategy`
+  collection copies the `replicationFactor`, `numberOfShards`, `shardingStrategy`, and `writeConcern`
   properties from the specified collection (referred to as the _prototype collection_)
   and distributes the shards of this collection in the same way as the shards of
   the other collection. In an Enterprise Edition cluster, this data co-location is

site/content/3.11/develop/http-api/collections.md

@@ -288,8 +288,14 @@ paths:
                       in the cluster, a shard refuses to write. Writes to shards with enough
                       up-to-date copies succeed at the same time, however. The value of
                       `writeConcern` cannot be greater than `replicationFactor`.
+
+                      If `distributeShardsLike` is set, the `writeConcern`
+                      is that of the prototype collection.
                       For SatelliteCollections, the `writeConcern` is automatically controlled to
-                      equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                      equal the number of DB-Servers and has a value of `0`.
+                      Otherwise, the default value is controlled by the current database's
+                      default `writeConcern`, which uses the `--cluster.write-concern`
+                      startup option as default, which defaults to `1`. _(cluster only)_
                     type: integer
                   shardingStrategy:
                     description: |
@@ -306,7 +312,7 @@ paths:
                   distributeShardsLike:
                     description: |
                       The name of another collection. This collection uses the `replicationFactor`,
-                      `numberOfShards` and `shardingStrategy` properties of the other collection and
+                      `numberOfShards`, `shardingStrategy`, and `writeConcern` properties of the other collection and
                       the shards of this collection are distributed in the same way as the shards of
                       the other collection.
                     type: string
@@ -1180,8 +1186,14 @@ paths:
                     in the cluster, a shard refuses to write. Writes to shards with enough
                     up-to-date copies succeed at the same time, however. The value of
                     `writeConcern` cannot be greater than `replicationFactor`.
+
+                    If `distributeShardsLike` is set, the `writeConcern`
+                    is that of the prototype collection.
                     For SatelliteCollections, the `writeConcern` is automatically controlled to
-                    equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                    equal the number of DB-Servers and has a value of `0`.
+                    Otherwise, the default value is controlled by the current database's
+                    default `writeConcern`, which uses the `--cluster.write-concern`
+                    startup option as default, which defaults to `1`. _(cluster only)_
                   type: integer
                 shardingStrategy:
                   description: |
@@ -1217,7 +1229,7 @@ paths:
                 distributeShardsLike:
                   description: |
                     The name of another collection. If this property is set in a cluster, the
-                    collection copies the `replicationFactor`, `numberOfShards` and `shardingStrategy`
+                    collection copies the `replicationFactor`, `numberOfShards`, `shardingStrategy`, and `writeConcern`
                     properties from the specified collection (referred to as the _prototype collection_)
                     and distributes the shards of this collection in the same way as the shards of
                     the other collection. In an Enterprise Edition cluster, this data co-location is
@@ -1435,8 +1447,14 @@ paths:
                       in the cluster, a shard refuses to write. Writes to shards with enough
                       up-to-date copies succeed at the same time, however. The value of
                       `writeConcern` cannot be greater than `replicationFactor`.
+
+                      If `distributeShardsLike` is set, the `writeConcern`
+                      is that of the prototype collection.
                       For SatelliteCollections, the `writeConcern` is automatically controlled to
-                      equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                      equal the number of DB-Servers and has a value of `0`.
+                      Otherwise, the default value is controlled by the current database's
+                      default `writeConcern`, which uses the `--cluster.write-concern`
+                      startup option as default, which defaults to `1`. _(cluster only)_
                     type: integer
                   shardingStrategy:
                     description: |
@@ -1453,7 +1471,7 @@ paths:
                   distributeShardsLike:
                     description: |
                       The name of another collection. This collection uses the `replicationFactor`,
-                      `numberOfShards` and `shardingStrategy` properties of the other collection and
+                      `numberOfShards`, `shardingStrategy`, and `writeConcern` properties of the other collection and
                       the shards of this collection are distributed in the same way as the shards of
                       the other collection.
                     type: string
@@ -2120,8 +2138,14 @@ paths:
                     in the cluster, a shard refuses to write. Writes to shards with enough
                     up-to-date copies succeed at the same time, however. The value of
                     `writeConcern` cannot be greater than `replicationFactor`.
+
+                    If `distributeShardsLike` is set, the `writeConcern`
+                    is that of the prototype collection.
                     For SatelliteCollections, the `writeConcern` is automatically controlled to
-                    equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                    equal the number of DB-Servers and has a value of `0`.
+                    Otherwise, the default value is controlled by the current database's
+                    default `writeConcern`, which uses the `--cluster.write-concern`
+                    startup option as default, which defaults to `1`. _(cluster only)_
                   type: integer
       responses:
         '400':

site/content/3.11/develop/http-api/databases.md

@@ -240,8 +240,13 @@ paths:
                         in the cluster, a shard refuses to write. Writes to shards with enough
                         up-to-date copies succeed at the same time, however. The value of
                         `writeConcern` cannot be greater than `replicationFactor`.
+
+                        If `distributeShardsLike` is set, the `writeConcern`
+                        is that of the prototype collection.
                         For SatelliteCollections, the `writeConcern` is automatically controlled to
-                        equal the number of DB-Servers and has a value of `0`. _(cluster only)_
+                        equal the number of DB-Servers and has a value of `0`.
+                        Otherwise, the default value is controlled by the `--cluster.write-concern`
+                        startup option, which defaults to `1`. _(cluster only)_
                       type: number
                 users:
                   description: |

site/content/3.11/develop/javascript-api/@arangodb/collection-object.md

@@ -266,7 +266,7 @@ In a cluster setup, the result also contains the following attributes:
 
 - `distributeShardsLike` (string):
   The name of another collection. This collection uses the `replicationFactor`,
-  `numberOfShards` and `shardingStrategy` properties of the other collection and
+  `numberOfShards`, `shardingStrategy`, `writeConcern` properties of the other collection and
   the shards of this collection are distributed in the same way as the shards of
   the other collection.
 

site/content/3.11/develop/javascript-api/@arangodb/db-object.md

@@ -392,7 +392,7 @@ error is thrown. For information about the naming constraints for collections, s
 
 - `distributeShardsLike` (string, _optional_, default: `""`):
   The name of another collection. If this property is set in a cluster, the
-  collection copies the `replicationFactor`, `numberOfShards` and `shardingStrategy`
+  collection copies the `replicationFactor`, `numberOfShards`, `shardingStrategy`, and `writeConcern`
   properties from the specified collection (referred to as the _prototype collection_)
   and distributes the shards of this collection in the same way as the shards of
   the other collection. In an Enterprise Edition cluster, this data co-location is