TencentDB for MongoDB
- Release Notes and Announcements
- Product Introduction
- Features
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Network Configuration
- Backup and Rollback
- Data Rollback
- Data Security
- SSL Authentication
- Database Management
- Disaster Recovery/Read-Only Instances
- Parameter Configuration
- Data Migration Guide
- Creating a DTS Migration Task
- Fix for Verification Failure
- Consistency Check After Migration
- Practical Tutorial
- Ops and Development Guide
- Troubleshooting
- API Documentation
- Making API Requests
- Backup APIs
- Instance APIs
- Account APIs
- Task APIs
- Other APIs
- Instance Connection
- Product Performance
- Service Agreement
Command Support in Sharded Cluster v3.2
Last updated: 2024-01-15 14:49:55
Sharding Strategy
Ranged-based sharding is supported.
The shardkey is indexed compound fields.
Sharding is required for all data sets in a shard instance. It is recommended to store non-sharded data in a separate replica set instance.
Authentication Mechanism
MongoDB is fully compatible with SCRAM-SHA-1 and MONGODB-CR.
Supported Sharded Cluster Commands
Category | Command | Subcommand | Supported |
Basic CRUD commands | find | filter | Yes |
| | sort | Yes |
| | projection | Yes |
| | hint | Yes |
| | skip | Yes |
| | limit | Yes |
| | batchSize | Yes |
| | singleBatch | Yes |
| | comment | Yes |
| | maxScan | Yes |
| | maxTimeMS | No |
| | readConcern | Yes |
| | max | Yes |
| | min | Yes |
| | returnKey | Yes |
| | showRecordId | Yes |
| | snapshot | No |
| | tailable | No |
| | oplogReplay | No |
| | noCursorTimeout | Yes |
| | awaitData | No |
| | allowPartialResults | No |
| insert | The `shardkey` field is required and must be the same for batch INSERT operations | Yes |
| update | The updated field cannot be `shardkey` | Yes |
| delete | - | Yes |
| findandmodify | - | Yes |
| count | - | Yes |
| distinct | The `shardkey` field is required | Yes |
| aggregate | - | Yes |
| group | - | No |
| mapReduce | - | No |
| getmore | - | Yes |
| getLastError | - | No |
| getPrevError | - | No |
| resetError | - | No |
| eval | - | No |
| geoNear | - | No |
| geoSearch | - | No |
| parallelCollectionScan | - | No |
Diagnostic commands | collStats | - | Yes |
| dbstats | - | Yes |
| explain | - | Yes |
| listDatabases | - | Yes |
| serverStatus | - | No |
| top | - | No |
Sharding commands | enableSharding | - | Yes |
| shardCollection | - | Yes |
Management commands | listCollections | - | Yes |
| dropDatabase | - | Yes |
| drop | - | Yes |
| creareIndexes | - | Yes |
| listIndexes | - | Yes |
| dropIndexes | - | Yes |
| logout | - | Yes |
| renameCollection | - | No |
| copydb | - | No |
| create | - | No |
| clone | - | No |
| cloneCollection | - | No |
| cloneCollectionAsCapped | - | No |
| convetToCapped | - | No |
| filemd5 | - | No |
| fsync | - | No |
| clean | - | No |
| connPoolSync | - | No |
| connectionStatus | - | No |
| compact | - | No |
| collMod | - | No |
| reIndex | - | No |
| setParameter | - | No |
| getParameter | - | No |
| repairDatabase | - | No |
| repairCursor | - | No |
| touch | - | No |
| shutdown | - | No |
| logrotate | - | No |
| killop | - | No |
User management commands | - | - | No |
Role management commands | - | - | No |
Replica set commands | - | - | No |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No