[SERVER-62534] Make merging logic in async results merger modular Created: 11/Jan/22 Updated: 06/Dec/22 Resolved: 03/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Joe Kanaan | Assignee: | Backlog - Query Optimization |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Sprint: | QO 2022-02-07, QO 2022-02-21 |
| Participants: |
| Comments |
| Comment by James Wahlin [ 03/Mar/22 ] |
|
Closing as won't do as we don't expect that this work would be scheduled in the near future. We can consider reopening the next time we work on the AsyncResultMerger if we think this would be beneficial. |
| Comment by David Storch [ 25/Feb/22 ] |
|
Okie doke, I marked it for re-triage. I would argue that we should close this ticket as "Won't Do". |
| Comment by Jess Balint [ 22/Feb/22 ] |
|
Yep. We were just discussing this today. We can move it to the backlog for triage and remove from the PM-2333 epic. |
| Comment by David Storch [ 22/Feb/22 ] |
|
My understanding was that this ticket was going to be closed as "Won't Do" or at least returned to the backlog given the design we've chosen for this project. Is that right jess.balint? |