[SERVER-54954] Consider renaming and enforcing remove(Value) -> removeFirst(Value) in WindowFunctionStatement Created: 04/Mar/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qopt-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Optimization
|
||||
| Participants: | |||||
| Description |
|
Right now the interface supports removing documents anywhere in the window which is most likely incorrect and could lead to programming mistakes later. As part of this the data structure for the $push (and possibly others) window function could be changed to a queue. |
| Comments |
| Comment by Ted Tuckman [ 08/Mar/21 ] |
|
Definitively just a nice to have, just code cleanup to prevent possible mistakes. Would be fine to go at the end if we wind up with extra time. |
| Comment by Nicholas Zolnierz [ 05/Mar/21 ] |
|
ted.tuckman can you comment on the priority of this? Everything is slotted into sprints so would be good to figure out if this is actually required or more of a nice-to-have. |