[SERVER-81185] bulkWrite base command size estimation should account for timeseries collections Created: 19/Sep/23 Updated: 29/Oct/23 Resolved: 22/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2023-10-02 |
| Participants: |
| Description |
|
When bulkWrite sends out child batches that contain operations against timeseries collections, it may convert timeseries view namespace to timeseries bucket namespace and attach the isTimeseriesCollection field. Therefore, when we calculate the base size estimate, we should take into account the increased size for the namespace translation and the additional field. |
| Comments |
| Comment by Githook User [ 22/Sep/23 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |