[SERVER-80160] Retryable timeseries insert doesn't return retriedStmtIds / opTime Created: 16/Aug/23 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-subteam3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
PM-2210 introduced retriedStmtIds in write command responses to report the retried statements of a retryable write. But there is a discrepancy between batched inserts to regular collections and batched inserts to timeseries collections. Batched timeseries inserts don't return retriedStmtIds. I don't think this is a bug yet but it could be problematic for future development (e.g. global index? PM-2015?) when we need to make use of retriedStmtIds of internal transactions. Note that the opTime field is missing as well. |