Skip to content

Commit 8819b5a

Browse files
nerpaulaSimran-B
andauthored
Release notes: arangorestore override writeConcern option (#394)
* arangorestore override writeConcern * Review --------- Co-authored-by: Simran <[email protected]>
1 parent 5dac9a7 commit 8819b5a

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -575,6 +575,17 @@ _arangodump_ operations on the server:
575575
dump thread was blocked because it honored the server-side memory
576576
limit for dumps.
577577

578+
### arangorestore
579+
580+
The following startup option has been added that allows _arangorestore_ to override
581+
the `writeConcern` value specified in a database dump when creating new
582+
collections:
583+
584+
- `--write-concern`: Override the `writeConcern` value for collections.
585+
Can be specified multiple times, e.g. `--write-concern 2 --write-concern myCollection=3`
586+
to set the write concern for the collection called `myCollection` to 3 and
587+
for all other collections to 2.
588+
578589
### arangoimport
579590

580591
The default value for the `--type` startup option has been changed from `json`

0 commit comments

Comments
 (0)