[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:
Related
is related to SERVER-1734 Rename "atomic" to "isolated" Closed
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 (SERVER-32173), we won't fix this.

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.

Generated at Thu Feb 08 03:22:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.