[SERVER-10296] Permit $unset and $rename to manipulate objects with invalid field names (e.g. containing leading $ or .) Created: 23/Jul/13 Updated: 02/Aug/18 Resolved: 26/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.2 |
| 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 | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
The new update framework is more restrictive in what it will admit as a valid field name. Many invalid field names were not caught by the old framework. We still would, however, like to allow users to repair bad field names by using the $unset and $rename operators. To do so, we will need to weaken the field name restrictions enforced for $unset entirely, and relax the 'source' field name restrictions for $rename. Marking as QA required since we should validate that we can repair data with invalid field names via $unset and $rename. |
| Comments |
| Comment by auto [ 26/Jul/13 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}Message: |