AcknowledgedValue returns true if a BSON RawValue for a write concern represents an acknowledged write concern.

AckWrite returns true if a write concern represents an acknowledged write Deprecated: Use [WriteConcern.Acknowledged] instead.

Custom returns a WriteConcern that requests acknowledgment that write operations have propagated to tagged members that satisfy the custom write concern defined in "settings.getLastErrorModes".

J requests acknowledgement from MongoDB that write operations are written to the journal.

Journaled returns a WriteConcern that requests acknowledgment that write operations have been written to the on-disk journal on MongoDB.

Majority returns a WriteConcern that requests acknowledgment that write operations have been durably committed to the calculated majority of the data-bearing voting members.

New constructs a new WriteConcern.

Unacknowledged returns a WriteConcern that requests no acknowledgment of write operations.

W requests acknowledgement that write operations propagate to the specified number of mongod instances.

W1 returns a WriteConcern that requests acknowledgment that write operations have been written to memory on one node (e.g.

WMajority requests acknowledgement that write operations propagate to the majority of mongod instances.

WTagSet requests acknowledgement that write operations propagate to the specified mongod instance.

WTimeout specifies a time limit for the write concern.

ErrEmptyWriteConcern indicates that a write concern has no fields set.

ErrInconsistent indicates that an inconsistent write concern was specified.

ErrNegativeW indicates that a negative integer `w` field was specified.

ErrNegativeWTimeout indicates that a negative WTimeout was specified.

A WriteConcern defines a MongoDB write concern, which describes the level of acknowledgment requested from MongoDB for write operations to a standalone mongod, to replica sets, or to sharded clusters.

Option is an option to provide when creating a WriteConcern.