mongo-go-driver | The Official Golang driver for MongoDB

Your query covers all collections, however usually it should be per collection, i.e. per namespace. In earlier MongoDB release the documents where like this:

There's nothing wrong with your example, it works.

Please note that the expireAfterSeconds you specify is the duration after createdAt when the document expires, and that instant is the earliest time at which the document may be deleted, but there is no guarantee that the deletion will happen "immediately", exactly at that time.

Quoting from MongoDB docs: TTL indexes: Timing of the Delete Operation:

The TTL index does not guarantee that expired data will be deleted immediately upon expiration. There may be a delay between the time a document expires and the time that MongoDB removes the document from the database.

The background task that removes expired documents runs every 60 seconds. As a result, documents may remain in a collection during the period between the expiration of the document and the running of the background task.

Because the duration of the removal operation depends on the workload of your mongod instance, expired data may exist for some time beyond the 60 second period between runs of the background task.

As you can see, if a document expires, at worst case it may take 60 seconds for the background task to kick in and start removing expired documents, and if there are many (or the database is under heavy load), it may take some time to delete all expired documents.

you need to use the replica set option

The Database.Collection() method has "optional" options.CollectionOptions parameter which does have option to set the bsoncodec.Registry. If you acquire your collection using an options that's configured with a registry, that registry will be used with all operations performed with that collection.

Use it like this:

bson.M is a map, so if you use it, you have to write: bson.M{"_id": oid}. See missing type in composite literal go AND missing key in map literal go.

And bson.D is a slice of structs, so if you use it, you should write bson.D{{Key:"$set", Value: input}}. Omitting the field names is not a compiler error, it's just a go vet warning.

Now on to replacing. The replacement must be a document itself, without using $set (this is not updating but replacing). For reference see MongoDB's collection.replaceOne() and the driver's doc: Collection.ReplaceOne():

The replacement parameter must be a document that will be used to replace the selected document. It cannot be nil and cannot contain any update operators (https://docs.mongodb.com/manual/reference/operator/update/).

So do it like this:

If that works for you I see no issue with doing what you are suggesting. The Go driver is generally verbose to use.

Note that most drivers do not specify a timeout for each operation the way Go driver suggests using it.

You may consider setting socket timeout via the URI options, which can be done once for the entire program but isn't quite the same thing as a per-operation timeout.

Note also there are efforts under way to improve the per-operation timeout handling in drivers in general.

To authenticate with x.509, the username should be either the common name of the certificate or empty. You seem to be attempting some mix of password and x.509 authentication.

All required options can be provided in the URI. See How can I connect with X509 by putting all options in the connection string in node.js driver for mongodb?.

If you insist on specifying credentials not in a URI, reference driver documentation that describes how to do that for x509 credentials.

Use bson.M{"$in", userIDs} instead bson.D{{"$in", userIDs}} in filter and for update use bson.M{"$inc": bson.M{"unread": 1}} instead bson.D{{"$inc", bson.D{{"unread", 1}}}}

You have to use upsert - It will update if it is present else inserts.

Refer this