[SERVER-10041] Rename "snapshot" to "deduplicate" Created: 27/Jun/13 Updated: 06/Dec/22 Resolved: 05/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
A "snapshot query" sounds like it operates in an isolated transaction, when in fact it simply omits duplicate documents from the results. I propose renaming "snapshot" to something more descriptive. If "deduplicate" seems long, we could use "dedup": there's precedent in createIndex's "dropDups" flag. "unique" is another possibility. "snapshot" can be gently deprecated. |
| Comments |
| Comment by Asya Kamsky [ 05/Dec/17 ] |
|
Since old snapshot option is going away ( |
| Comment by Dwight Merriman [ 20/Feb/14 ] |
|
$snapshot also assures you don't miss any documents that existed at both the start and end of your query i believe. so not-having-duplicates isn't the only thing it does. what is really needed is a revision of the storage engine so that this modifier is not needed at all. |