[SERVER-70983] Serialize the command responses for collStats correctly in a multitenant env Created: 31/Oct/22 Updated: 29/Oct/23 Resolved: 09/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | Hugh Tong (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-12-12 |
| Participants: |
| Description |
|
The collStats command does not have an IDL defined reply type, so we can use NamespaceStringUtil::serialize to serialize the namespace correctly in the response here and here (the second place special cases appending stats for a timeseries collection). Let's add tests to native_tenant_data_isolaton_basic_security_token.js that run collStats both on a standard collection and on a timeseries collection (an example of how to create a timeseries collection is here). We can use the "checkNsSerializedCorrectly()" function defined in the test to check the namespaces are serialized correctly. |
| Comments |
| Comment by Githook User [ 07/Dec/22 ] |
|
Author: {'name': 'Hugh Tong', 'email': 'hugh.tong@mongodb.com', 'username': 'cortrain'}Message: |