[SERVER-43661] Remove the $currentDate update modifier Created: 26/Sep/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Query Language |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
Consider removing the $currentDate update modifier. This should occur no earlier than MongoDB 4.6 as this modifier is being deprecated for MongoDB 4.4 under SERVER-42007. |
| Comments |
| Comment by Charlie Swanson [ 12/May/21 ] |
|
Looks like we backed out of the deprecation due to concerns about the oplog entry size. I reopened SERVER-42007 to discuss whether we should reconsider deprecation now that we improved the oplog entry generation for pipeline-based updates. |
| Comment by Charlie Swanson [ 29/Apr/21 ] |
|
We should investigate whether $currentDate is accidentally included in API Version 1. Assigning to myself to figure that out. |
| Comment by David Storch [ 28/Apr/21 ] |
|
Flagging for re-triage. I doubt we will consider this for 5.0 at this stage in the game, but perhaps we would consider scheduling it after branching for 5.0? |