Struct mongodb::Client

pub struct Client { /* private fields */ }

This is the main entry point for the API. A Client is used to connect to a MongoDB cluster. By default, it will monitor the topology of the cluster, keeping track of any changes, such as servers being added or removed.

Client uses std::sync::Arc internally, so it can safely be shared across threads or async tasks. For example:

let client = Client::with_uri_str("mongodb://example.com").await?;

for i in 0..5 {
    let client_ref = client.clone();

    tokio::task::spawn(async move {
        let collection = client_ref.database("items").collection::<Document>(&format!("coll{}", i));

        // Do something with the collection
    });
}

Notes on performance

Spawning many asynchronous tasks that use the driver concurrently like this is often the best way to achieve maximum performance, as the driver is designed to work well in such situations.

Additionally, using a custom Rust type that implements Serialize and Deserialize as the generic parameter of Collection instead of bson::Document can reduce the amount of time the driver and your application spends serializing and deserializing BSON, which can also lead to increased performance.

TCP Keepalive

TCP keepalive is enabled by default with tcp_keepalive_time set to 120 seconds. The driver does not set tcp_keepalive_intvl. See the MongoDB Diagnostics FAQ keepalive section for instructions on setting these values at the system level.

Clean shutdown

Because Rust has no async equivalent of Drop, values that require server-side cleanup when dropped spawn a new async task to perform that cleanup. This can cause two potential issues:

• Drop tasks pending or in progress when the async runtime shuts down may not complete, causing server-side resources to not be freed.
• Drop tasks may run at an arbitrary time even after no Client values exist, making it hard to reason about associated resources (e.g. event handlers).

To address these issues, we highly recommend you use Client::shutdown in the termination path of your application. This will ensure that outstanding resources have been cleaned up and terminate internal worker tasks before returning. Please note that shutdown will wait for all outstanding resource handles to be dropped, so they must either have been dropped before calling shutdown or in a concurrent task; see the documentation of shutdown for more details.

Implementations

impl Client

pub fn bulk_write( &self, models: impl IntoIterator<Item = impl Into<WriteModel>>, ) -> BulkWrite<'_, SummaryBulkWriteResult>

Executes the provided list of write operations.

This operation will retry once upon failure if the connection and encountered error support retryability. See the documentation here for more information on retryable writes.

await will return Result<SummaryBulkWriteResult or Result<VerboseBulkWriteResult if verbose_results is configured.

Bulk write is only available on MongoDB 8.0+.

impl Client

pub fn list_databases(&self) -> ListDatabases<'_>

Gets information about each database present in the cluster the Client is connected to.

await will return Result<Vec<DatabaseSpecification>>.

pub fn list_database_names(&self) -> ListDatabases<'_, ListNames>

Gets the names of the databases present in the cluster the Client is connected to.

await will return Result<Vec<String>>.

impl Client

pub fn warm_connection_pool(&self) -> WarmConnectionPool<'_>

Add connections to the connection pool up to min_pool_size. This is normally not needed - the connection pool will be filled in the background, and new connections created as needed up to max_pool_size. However, it can sometimes be preferable to pay the (larger) cost of creating new connections up-front so that individual operations execute as quickly as possible.

Note that topology changes require rebuilding the connection pool, so this method cannot guarantee that the pool will always be filled for the lifetime of the Client.

Does nothing if min_pool_size is unset or zero.

await will return ().

impl Client

pub fn start_session(&self) -> StartSession<'_>

Starts a new ClientSession.

await will return Result<ClientSession>.

impl Client

pub fn shutdown(self) -> Shutdown

Shut down this Client, terminating background thread workers and closing connections. Using this method is not required under most circumstances (resources will be cleaned up in the background when dropped) but can be needed when creating Clients in a loop or precise control of lifespan timing is required. This will wait for any live handles to server-side resources (see below) to be dropped and any associated server-side operations to finish.

IMPORTANT: Any live resource handles that are not dropped will cause this method to wait indefinitely. It’s strongly recommended to structure your usage to avoid this, e.g. by only using those types in shorter-lived scopes than the Client. If this is not possible, see immediate. For example:

async fn upload_data(bucket: &GridFsBucket) -> Result<()> {
  let stream = bucket.open_upload_stream("test").await?;
   // .. write to the stream ..
}

let client = Client::with_uri_str("mongodb://example.com").await?;
let bucket = client.database("test").gridfs_bucket(None);
upload_data(&bucket).await;
client.shutdown().await;
// Background cleanup work from `upload_data` is guaranteed to have run.

If the handle is used in the same scope as shutdown, explicit drop may be needed:

let client = Client::with_uri_str("mongodb://example.com").await?;
let bucket = client.database("test").gridfs_bucket(None);
let stream = bucket.open_upload_stream("test").await?;
// .. write to the stream ..
drop(stream);
client.shutdown().await;
// Background cleanup work for `stream` is guaranteed to have run.

Calling any methods on clones of this Client or derived handles after this will return errors.

Handles to server-side resources are Cursor, SessionCursor, Session, or GridFsUploadStream.

await will return ().

impl Client

pub fn watch(&self) -> Watch<'_>

Starts a new ChangeStream that receives events for all changes in the cluster. The stream does not observe changes from system collections or the “config”, “local” or “admin” databases. Note that this method (watch on a cluster) is only supported in MongoDB 4.0 or greater.

See the documentation here on change streams.

Change streams require either a “majority” read concern or no read concern. Anything else will cause a server error.

Note that using a $project stage to remove any of the _id operationType or ns fields will cause an error. The driver requires these fields to support resumability. For more information on resumability, see the documentation for ChangeStream

If the pipeline alters the structure of the returned events, the parsed type will need to be changed via ChangeStream::with_type.

await will return Result<ChangeStream<ChangeStreamEvent<Document>>> or Result<SessionChangeStream<ChangeStreamEvent<Document>>> if a ClientSession has been provided.

impl Client

pub async fn with_uri_str(uri: impl AsRef<str>) -> Result<Self>

Creates a new Client connected to the cluster specified by uri. uri must be a valid MongoDB connection string.

See the documentation on ClientOptions::parse for more details.

pub fn with_options(options: ClientOptions) -> Result<Self>

Creates a new Client connected to the cluster specified by options.

pub fn encrypted_builder( client_options: ClientOptions, key_vault_namespace: Namespace, kms_providers: impl IntoIterator<Item = (KmsProvider, Document, Option<TlsOptions>)>, ) -> Result<EncryptedClientBuilder>

Available on crate feature in-use-encryption-unstable only.

Return an EncryptedClientBuilder for constructing a Client with auto-encryption enabled.

let encrypted_client = Client::encrypted_builder(
    client_options,
    key_vault_namespace,
    [(KmsProvider::Local, doc! { "key": local_key }, None)],
)?
.key_vault_client(key_vault_client)
.build()
.await?;

pub fn selection_criteria(&self) -> Option<&SelectionCriteria>

Gets the default selection criteria the Client uses for operations..

pub fn read_concern(&self) -> Option<&ReadConcern>

Gets the default read concern the Client uses for operations.

pub fn write_concern(&self) -> Option<&WriteConcern>

Gets the default write concern the Client uses for operations.

pub fn database(&self, name: &str) -> Database

Gets a handle to a database specified by name in the cluster the Client is connected to. The Database options (e.g. read preference and write concern) will default to those of the Client.

This method does not send or receive anything across the wire to the database, so it can be used repeatedly without incurring any costs from I/O.

pub fn database_with_options( &self, name: &str, options: DatabaseOptions, ) -> Database

Gets a handle to a database specified by name in the cluster the Client is connected to. Operations done with this Database will use the options specified by options by default and will otherwise default to those of the Client.

This method does not send or receive anything across the wire to the database, so it can be used repeatedly without incurring any costs from I/O.

pub fn default_database(&self) -> Option<Database>

Gets a handle to the default database specified in the ClientOptions or MongoDB connection string used to construct this Client.

If no default database was specified, None will be returned.

Trait Implementations

impl Clone for Client

fn clone(&self) -> Client

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Client

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl From<Client> for Client

Available on crate feature sync only.

fn from(async_client: AsyncClient) -> Self

Converts to this type from the input type.