[SERVER-10267] Audit and repair modifier in-place decisions in light of new in-place update mechanism Created: 19/Jul/13 Updated: 02/Aug/18 Resolved: 22/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When we had originally designed the ModifierInterface, we believed that we would go through a prepare phase that would need to decide about in-placeness. Subsequently, we changed to a different model for in-place, where the mutable Document tracks the in-place status for itself. In light of this change, it is not clear whether the ExecInfo inPlace field is still relevant or necessary, or that the decisions operators are using to set it are correct, or what the consequences of setting it might be. We should probably remove it, but we should at least look at all the instances and evaluate our options. |
| Comments |
| Comment by auto [ 22/Jul/13 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}Message: |