Time Series Collection Limitations

Unsupported Features

The following features are not supported for time series collections:

• Atlas Search

• Change streams

• Client-Side Field Level Encryption

• Database Triggers

• GraphQL API (deprecated)

• Schema validation rules

• reIndex

• renameCollection

Atlas Device Sync support is limited to time series collections that use Atlas Data Ingest.

Aggregation $merge and $out

You cannot use the $merge aggregation stage to add data from another collection to a time series collection.

Deletes

Starting in MongoDB 5.1, you can perform limited delete operations on time series collections. MongoDB 7.0 removes most limitations from operations that are based on the delete command.

Time series deletes are not supported for multi-document transactions.

From MongoDB 5.1 to 6.3, delete commands must meet the following requirements:

• You can only match on metaField field values.

• Your delete command must not limit the number of documents to be deleted. Set justOne: false or use the deleteMany() method.

Starting in MongoDB 7.0, there is only one time series related limitation on these delete commands:

• delete

• deleteOne()

• deleteMany()

• Bulk.find.delete()

• Bulk.find.deleteOne()

You cannot use these commands with multi-document transactions. There are no other restrictions.

If a time series collection contains documents with timeField timestamps before 1970-01-01T00:00:00.000Z or after 2038-01-19T03:14:07.000Z, no documents are deleted from the collection by the TTL "time to live" feature.

For details on TTL deletes, see Expire Data from Collections by Setting TTL.

Updates

Starting in MongoDB 5.1, you can perform limited update operations.

Update commands must meet the following requirements:

• You can only match on the metaField field value.

• You can only modify the metaField field value.

• Your update document can only contain update operator expressions.

• Your update command must not limit the number of documents to be updated. Set multi: true or use the updateMany() method.

• Your update command must not set upsert: true.

In MongoDB 5.0, time series collections only support insert operations and read queries. Updates and manual delete operations result in an error.

To automatically delete old data, set up automatic removal (TTL).

To remove all documents from a collection, use the drop() method to drop the collection.

Time Series Secondary Indexes

MongoDB 6.0 and later features improved support for secondary indexes on time series collections. For a summary of these options, see Time Series Secondary Indexes in MongoDB 6.0 and Later.

Capped Collections

You cannot create a time series collection as a capped collection.

Modification of Collection Type

You can only set the collection type when you create a collection:

• An existing collection cannot be converted into a time series collection.

• A time series collection cannot be converted into a different collection type.

To move data from an existing collection to a time series collection, migrate data into a time series collection.

Modification of timeField and metaField

You can only set a collection's timeField and metaField parameters when you create the collection. You cannot modify these parameters later.

Granularity

db.runCommand({
   collMod: "timeseries",
   timeseries: { bucketMaxSpanSeconds: 3600, bucketRoundingSeconds: 3600 }
})

Sharding

Starting in MongoDB 5.1 (and 5.0.6), you can create sharded time series collections.

In versions earlier than MongoDB 5.0.6, you cannot shard time series collections.

Transactions

You cannot write to time series collections in transactions.

Views

• Time series collections are writable non-materialized views. Limitations for views apply to time series collections.

• You cannot create a view from a time series bucket collection namespace (namely, a collection prefixed with system.buckets).