- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Node Overview
- Viewing Node Information
- Adjusting Mongod Node Specification
- Adding Secondary Node
- Deleting Secondary Node
- Adding Read-Only Node
- Adjusting Shard Quantity
- Adjusting Mongos Node Specification
- Adding Mongos Node
- Enabling Mongos Access Address
- Promoting Secondary Node to Primary Node
- Restarting a Node
- Version Upgrade
- Network Configuration
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Disaster Recovery/Read-Only Instances
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Creating a DTS Migration Task
- Migration Overview
- Supported Capabilities
- User Guide
- Migration Operation Guide
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- Consistency Check After Migration
- Creating MongoDB Data Subscription
- Creating a DTS Migration Task
- Practical Tutorial
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
- What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- API Category
- Making API Requests
- Backup APIs
- Introduction
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- Product Performance
- FAQs
- Service Agreement
- Glossary
- Contact Us
- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Node Overview
- Viewing Node Information
- Adjusting Mongod Node Specification
- Adding Secondary Node
- Deleting Secondary Node
- Adding Read-Only Node
- Adjusting Shard Quantity
- Adjusting Mongos Node Specification
- Adding Mongos Node
- Enabling Mongos Access Address
- Promoting Secondary Node to Primary Node
- Restarting a Node
- Version Upgrade
- Network Configuration
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Disaster Recovery/Read-Only Instances
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Creating a DTS Migration Task
- Migration Overview
- Supported Capabilities
- User Guide
- Migration Operation Guide
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- Consistency Check After Migration
- Creating MongoDB Data Subscription
- Creating a DTS Migration Task
- Practical Tutorial
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
- What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- API Category
- Making API Requests
- Backup APIs
- Introduction
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- Product Performance
- FAQs
- Service Agreement
- Glossary
- Contact Us
This document lists the major features introduced in TencentDB for MongoDB version 6.0. For more detailed information, see the MongoDB 6.0 release-notes.
Time Series Collection Enhancements
MongoDB 6.0 introduces several improvements to time series collections, including enhancements to indexing, querying, and sorting, providing more powerful time series data processing capabilities.
First, MongoDB 6.0 introduces secondary indexes and compound indexes, significantly improving the read performance of time series collections. In previous versions, time series collections only supported basic single-key indexes, which could lead to performance bottlenecks when handling large amounts of data. By introducing secondary and compound indexes, developers can create more complex index structures based on actual needs, thereby enhancing query performance.
Second, MongoDB 6.0 introduces geo-indexing for spatiotemporal data, allowing developers to add geographic information to time series data. This enables more effective analysis of scenes involving distance and location.
In addition, MongoDB 6.0 optimizes query performance for time series data. In previous versions, querying the last data point in a time series collection required scanning the entire collection, which could result in high query latency. MongoDB 6.0 introduces an optimized last point query mechanism, allowing the system to directly locate the last data point in the collection without scanning the entire dataset.
Last, MongoDB 6.0 improves the sorting performance of time series data. By utilizing clustered indexes on time and metadata fields, along with secondary indexes, MongoDB 6.0 can perform sorting operations on time series data more efficiently. This allows developers to sort time series data as needed for better analysis and visualization.
In summary, the time series collection enhancements in MongoDB 6.0 provide developers with more powerful data processing capabilities, making it easier to build high-performance time series data applications.
Change Streams
The Change Streams feature allows business systems to capture real-time changes in the database, enabling the development of various event-driven applications or systems. By using Change Streams, developers can avoid the need for complex data synchronization middleware, simplifying architecture and improving reliability.
In MongoDB 6.0, Change Streams support viewing the pre-change status of documents, allowing developers to capture both the before and after status of a document. Additionally, Change Streams now support various DDL statements, including create, createIndexes, modify, and shardCollection, providing developers with more comprehensive monitoring of database changes.
In MongoDB 6.0, a new wallTime field has been added to change events. This field contains timestamp information and supports various conversion and display operators, including $toDate, $tsSeconds, and tsIncrement. For more information, see Change Events.
Aggregation
MongoDB 6.0 has further enhanced its aggregation capabilities, allowing users to process multiple documents more efficiently and return computed results. By combining multiple operators in the aggregation pipeline, users can build complex data processing pipelines to extract and analyze data. Below are some new features and optimizations in MongoDB 6.0’s aggregation functionality:
Sharded cluster instances now support
$lookup and $graphLookup, providing more powerful data processing and analysis capabilities. For more information, see $lookup (aggregation) and $graphLookup (aggregation).The
$lookup operator has been optimized for better JOIN support, making JOIN operations across multiple collections more efficient.The
$graphLookup operator has been optimized for better graph traversal support, making it more efficient when processing complex graph data structures.Query
In MongoDB 6.0, the query feature has been further enhanced with the introduction of several new operators, including
$maxN, $topN, $minN, $bottomN, $lastN and $sortArray. These operators allow developers to handle complex query requirements more efficiently. For more information, see Aggregation Pipeline Operators.
Yes
No
Was this page helpful?