[SERVER-4819] different dup dropping semantics with background vs non background indexing Created: 31/Jan/12 Updated: 31/Jan/12 Resolved: 31/Jan/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Non background index build - {a:[2,3]}document is partially indexed before being dropped at the end of the index build. As a result, {a:2}document is also marked as a dup and dropped.
Background index build - {a:[2,3]}document is dropped as soon as indexing is attempted, as a result {a:2}gets inserted.
|
| Comments |
| Comment by Aaron Staple [ 31/Jan/12 ] |
|
The issue isn't just ordering, but dependencies between documents. With background:true, and the above documents, there will a values of 2 and 3 in the index for any document ordering. For background:false one of 2 or 3 may not be in the index depending on ordering. This may be fine behavior to have, but we might want to make it explicit when we document what dropDups does. |
| Comment by Eliot Horowitz (Inactive) [ 31/Jan/12 ] |
|
the order of dropDups is not guaranteed |