[SERVER-82059] Inserting into a time-series collection does not replace top-level empty timestamp Created: 10/Oct/23 Updated: 20/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
According to our documentation, when inserting a document where a top-level field has an empty timestamp for its value, the server will replace that empty timestamp with the current timestamp value. However when inserting into a time-series collection we do not do this; it just stays as an empty timestamp. |
| Comments |
| Comment by Ashley Brown [ 13/Nov/23 ] |
|
Hey michael.gargiulo@mongodb.com, yes – if you want us to update the docs, please file a DOCSP! Thanks |