Observable for aggregate

The client-side automatic encryption settings. In-use encryption enables an application to specify what fields in a collection must be encrypted, and the driver automatically encrypts commands sent to MongoDB and decrypts responses.

Automatic encryption is an enterprise only feature that only applies to operations on a collection. Automatic encryption is not supported for operations on a database or view and will result in error. To bypass automatic encryption, set bypassAutoEncryption=true in AutoEncryptionSettings.

Explicit encryption/decryption and automatic decryption is a community feature, enabled with the new com.mongodb.client.vault.ClientEncryption type.

A MongoClient configured with bypassAutoEncryption=true will still automatically decrypt.

If automatic encryption fails on an operation, use a MongoClient configured with bypassAutoEncryption=true and use ClientEncryption#encrypt to manually encrypt values.

Enabling client side encryption reduces the maximum document and message size (using a maxBsonObjectSize of 2MiB and maxMessageSizeBytes of 6MB) and may have a negative performance impact.

Automatic encryption requires the authenticated user to have the listCollections privilege action.

Supplying an encryptedFieldsMap provides more security than relying on an encryptedFields obtained from the server. It protects against a malicious server advertising false encryptedFields.

Observable for change streams.

Note: The ChangeStreamDocument class will not be applicable for all change stream outputs. If using custom pipelines that radically change the result, the ChangeStreamObservable#withDocumentClass method should be used to provide an alternative document format.

The client-side settings for data key creation and explicit encryption.

Explicit encryption/decryption is a community feature, enabled with the new com.mongodb.client.vault.ClientEncryption type, for which this is the settings.

A Client Session

Extends the Java ClientSession and adds helpers for committing and aborting transactions.

Automatically imported into the org.mongodb.scala namespace

The implicit ClientSession with Scala helpers

Options for creating ClientSessions

Represents the commit quorum specifies how many data-bearing members of a replica set, including the primary, must complete the index builds successfully before the primary marks the indexes as ready.

Observable for distinct

An immutable Document implementation.

A strictly typed Map[String, BsonValue] like structure that traverses the elements in insertion order. Unlike native scala maps there is no variance in the value type and it always has to be a BsonValue.

Observable interface for Find.

Observable for listing collection names.

Observable interface for ListCollections

Observable interface for ListDatabases.

Observable interface for ListIndexes.

Observable interface for ListSearchIndexes.

An exception indicating that a failure occurred when running a $changeStream.

A client-side representation of a MongoDB cluster. Instances can represent either a standalone MongoDB instance, a replica set, or a sharded cluster. Instance of this class are responsible for maintaining an up-to-date state of the cluster, and possibly cache resources related to this, including background threads for monitoring, and connection pools.

Instance of this class server as factories for MongoDatabase instances.

The MongoCollection representation.

Options for creating MongoCompressor

An exception that may happen usually as a result of another thread clearing a connection pool. Such clearing usually itself happens as a result of an exception.

The MongoDatabase representation.

The MongoDriverInformation class allows driver and library authors to add extra information about their library. This information is then available in the MongoD/MongoS logs.

The following metadata can be included when creating a MongoClient.

• The driver name. Eg: mongo-scala-driver
• The driver version. Eg: 1.2.0
• Extra platform information. Eg: Scala 2.11

Note: Library authors are responsible for accepting MongoDriverInformation from external libraries using their library. Also all the meta data is limited to 512 bytes and any excess data will be truncated.

An exception indicating that the server is a member of a replica set but is in recovery mode, and therefore refused to execute the operation. This can happen when a server is starting up and trying to join the replica set.

An exception indicating that the server is a member of a replica set but is not the primary, and therefore refused to execute either a write operation or a read operation that required a primary. This can happen during a replica set election.

An exception thrown by methods that may automatically create data encryption keys where needed based on the encryptedFields configuration.

An exception indicating a failure to apply the write concern to the requested write operation

A Observable represents a MongoDB operation and implements the Publisher interface.

As such it is a provider of a potentially unbounded number of sequenced elements, publishing them according to the demand received from its Observer(s).

Extends the Publisher interface and adds helpers to make Observables composable and simple to Subscribe to.

Special parameterizations:

• Observable[Unit] must emit exactly one item by signalling Observer.onNext if it terminates successfully by signalling Observer.onComplete.
• Observable[Void] cannot emit an item. It is not exposed by the driver API because it is not convenient to work with in Scala.

Implicit conversion support for Publishers, Observables and Subscriptions

Automatically imported into the org.mongodb.scala namespace

An Observable that emits

• exactly one item, if the wrapped Publisher does not signal an error, even if the represented stream is empty;
• no items if the wrapped Publisher signals an error.

A Scala based wrapper of the Subscriber interface which provides a mechanism for receiving push-based notifications.

Will receive a call to Observer.onSubscribe(subscription: Subscription) on subscription to the Observable.

Default implementations of this trait are greedy and will call Subscription.request with Long.MaxValue so that all results are requested. Custom implementations of the onSubscribe method can be used to control "back-pressure" and ensure that only demand that the Observer is capable of handling is requested.

After signaling demand:

- Zero or more invocations of Observer.onNext up to the maximum number defined by Subscription.request - Single invocation of Observer.onError or Observer.onComplete which signals a terminal state after which no further events will be sent.

Controls the level of isolation for reads.

The readConcern option allows clients to choose a level of isolation for their reads.

A SingleObservable represents an Observable that emits one or no items.

A Subscription represents a one-to-one lifecycle of a Observer subscribing to an Observable.

Instances can only be used once by a single Observer.

It is used to both signal desire for data and to allow for unsubscribing.

Options for transactions

The result of a successful write operation. If the write was unacknowledged, then wasAcknowledged will return false and all other methods with throw MongoUnacknowledgedWriteException.

Represents the details of a write error , e.g. a duplicate key error

Observable for map reduce.