What Is New in MongoDB 7.1
MongoDB 7.1 delivers a set of refinements and new capabilities focused on developer productivity and operational efficiency. This release builds on the foundation of 7.0, enhancing time series collections, querying, and security tooling.
| Category | Key Updates |
|---|---|
| New Features | Columnar Compression, Delete & Update for Sharded Time Series Collections |
| Query Enhancements | Vector Search GA, Compound Wildcard Indexes, $bitwise Operators |
| Operability | Initial Sync Progress Monitoring, Concurrent Index Builds on CSRS |
| Security | Queryable Encryption GA, New User Management Commands |
How does MongoDB 7.1 improve time series data handling?
The biggest upgrade for time series is the introduction of columnar compression. This feature applies automatic compression to time series collections, significantly reducing their storage footprint on disk.
You can now also perform delete and update operations directly on sharded time series collections. This removes a previous limitation, making time series data much more mutable and manageable in distributed environments.
What querying power does 7.1 add?
Vector Search has been promoted to General Availability (GA), making it production-ready for building AI-powered applications like semantic search and recommendations directly on your data.
Compound wildcard indexes allow a single index to support queries on multiple unknown fields, which is fantastic for schemas with variable data. New $bitwise operators ($bitAnd, $bitOr, etc.) let you perform bit-level operations within aggregation pipelines, unlocking new data processing patterns.
What operational improvements should I know about?
Initial sync progress is now visible, so you can monitor how much data has been copied when adding a new replica set member. This provides much-needed visibility into what was previously a black-box process.
For sharded clusters, concurrent index builds are now supported on Config Server Replica Sets (CSRS). This parallelizes building indexes on the config database, speeding up metadata operations.
How is security enhanced in this release?
Queryable Encryption is now GA. This technology allows you to run expressive queries on fully encrypted data, a major step forward for client-side security and data privacy.
New user management commands (createUser, dropUser, etc.) have been added for the security-focused Key Management Interoperability Protocol (KMIP), streamlining the configuration of this external key manager.
FAQ
Is Vector Search now safe for production use?
Yes, Vector Search has achieved General Availability (GA) status in MongoDB 7.1. This means it is fully supported for production deployments, offering stable APIs and performance for building AI applications.
Can I update or delete records in my sharded time series collections?
Absolutely. This was a key limitation in previous versions. MongoDB 7.1 introduces the ability to perform update and delete operations on sharded time series collections, making them much more flexible.
What is the benefit of columnar compression for time series?
Columnar compression automatically reduces the on-disk size of your time series collections. In practice, this translates to lower storage costs and potentially faster scan performance for analytics queries on large time-based datasets.
Do I need to change my code to use Queryable Encryption now that it's GA?
If you were using the preview, you should review the GA documentation for any final API changes. For new implementations, you can now build with the stable, production-ready Queryable Encryption APIs provided in the 7.1-compatible drivers.
How do the new $bitwise operators work?
The new $bitwise operators (like $bitAnd, $bitOr, $bitXor) allow you to perform bit-level comparison and manipulation on integer values directly within an aggregation pipeline stage, which is useful for working with data that uses bit flags or masks.