mongoc_write_concern_get_wtag (3) - Linux Manuals

Pages related to mongoc_write_concern_get_wtag

• mongoc_write_concern_get_wtimeout (3) - Fetches the write timeout to use as part of the write concern. If the write has not completed before this timeout, an error will be returned.
• mongoc_write_concern_get_w (3) - Fetches the w parameter of the write concern.
• mongoc_write_concern_get_wmajority (3) - Fetches if the write should be written to a majority of nodes before indicating success.
• mongoc_write_concern_get_fsync (3) - Fetches if an fsync should be performed before returning success on a write operation.
• mongoc_write_concern_get_journal (3) - Fetches if the write should be journaled before indicating success.
• mongoc_write_concern_copy (3) - Performs a deep copy of write_concern.
• mongoc_write_concern_destroy (3) - Frees all resources associated with the write concern structure.
• mongoc_write_concern_new (3) - None
• mongoc_write_concern_set_fsync (3) - Sets if a fsync must be performed before indicating write success.
• mongoc_write_concern_set_journal (3) - Sets if the write must have been journaled before indicating success.
• mongoc_write_concern_set_w (3) - Sets the w value for the write concern. See mongoc_write_concern_t for more information on this setting.
• mongoc_write_concern_set_wmajority (3) - Sets if the write must have been propagated to a majority of nodes before indicating write success.
• mongoc_write_concern_set_wtag (3) - Sets the write tag that must be satistified for the write to indicate success. Write tags are preset write concerns configured on your MongoDB server. See mongoc_write_concern_t for more information on this setting.
• mongoc_write_concern_set_wtimeout (3) - Set the timeout in milliseconds that the server should wait before indicating that the write has failed. This is not the same as a socket timeout. A value of zero may be used to indicate no timeout.
• mongoc_write_concern_t (3) - Write Concern abstraction
• mongoc_bulk_operation_delete (3) - None