[SERVER-13992] UpdateTicket should handle record moves Created: 19/May/14 Updated: 06/Dec/22 Resolved: 10/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently the collection only uses UpdateTicket for non-moving updates and had different logic for moving updates. The UpdateTicket already captures the before and after index changes, so it can be smarter than doing a from-scratch unindex/reindex. |
| Comments |
| Comment by Geert Bosch [ 27/Oct/14 ] |
|
I'm not sure if this is still relevant. I'll revisit after the release. |