[SERVER-69128] Server-side document hashing Created: 24/Aug/22 Updated: 05/Dec/22 Resolved: 13/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Backlog - Query Execution |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
When verifying clusters for logical consistency as part of the verifier project, we can speed the process up by computing hashes server-side instead of transferring full documents over the network to the verifier process and computing the hashes there. Verification speed matters, as it's on the critical path for reducing downtime for MongoDB migrations. One potential option could be to introduce a new operator in the aggregation pipeline. |
| Comments |
| Comment by Ana Meza [ 13/Sep/22 ] |
|
Closing as duplicate of SERVER-30359 Note: We previously introduced a new $toHashedIndexKey expression via |
| Comment by Alexander Komyagin [ 24/Aug/22 ] |