[SERVER-57287] "timeseries" is not a top-level field when running collStats on mongos Created: 28/May/21 Updated: 29/Oct/23 Resolved: 15/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc3, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Julia Ruddy (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | execution-product-sync, time-series | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||
| Sprint: | Execution Team 2021-06-14, Execution Team 2021-06-28 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When running db.runCommand( { collStats : "timeseries" } ) on a mongos for a time-series collection, the new timeseries field does not appear at the top-level. For replica sets and standalones, timeseries is a top-level field as shown below:
However, for a mongos the timeseries field is only available nested within the shards field. For example:
I would think the timeseries field would also be at the top-level similar to the ns, size, storageSize, totalIndexSize, totalSize, indexSizes etc fields. If this is expected behavior, however, feel free to close this ticket. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 17/Jun/21 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: (cherry picked from commit 91ce36557dc90c85544791a47f880509ada6469e) |
| Comment by Githook User [ 15/Jun/21 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 09/Jun/21 ] |
|
I've filed |
| Comment by Julia Ruddy (Inactive) [ 07/Jun/21 ] |
|
We implemented a workaround to check for the timeseries field on the nested shard document for now. If it is not straightforward, ok with me to move to PM-2188. |
| Comment by Daniel Gottlieb (Inactive) [ 01/Jun/21 ] |
|
Hi julia.ruddy, I've passed this to storage execution (they did the time series project) to see if this is intentional, although this might be more of a sharding clarification. I think historically sharding has had trouble ensuring all shards have a consistent definition for a collection and its indexes. For those circumstances, it's obviously beneficial to have a schema that can express those situations. |