[SERVER-38036] Turn on hybrid builds for background, unique indexes Created: 08/Nov/18 Updated: 29/Oct/23 Resolved: 13/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Storage NYC 2018-12-03, Storage NYC 2018-12-17 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||
| Linked BF Score: | 13 | ||||||||||||||||||||||||
| Description |
|
Loop the DuplicateKeyTracker into the hybrid index build process and have background, unique indexes use the hybrid index build code. |
| Comments |
| Comment by Githook User [ 13/Dec/18 ] |
|
Author: {'username': 'louiswilliams', 'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams'}Message: |
| Comment by Githook User [ 07/Dec/18 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: Revert " This reverts commit 621f411f07f110992eb6a09ba44a5cc0b4af8a3e. |
| Comment by Githook User [ 06/Dec/18 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |
| Comment by Daniel Gottlieb (Inactive) [ 08/Nov/18 ] |
|
I marked this as dependent on using the external sorter, but that was more of a guess for ease of implementation than a logical requirement. Specifically, the duplicate key tracker needs to track dups going into the index. The mechanism for discovering dupes in the table-scan portion may be different for sorted keys coming out of the external sorter than it would be for inserting unordered keys into the index table. Inserting from the side-table into the index will likely need logic to discover duplicate keys in an unordered scenario, so the concern may be unfounded. |