[SERVER-29616] Permit $rename with non-viable path as the source Created: 13/Jun/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Justin Seyster | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Execution
|
||||
| Participants: | |||||
| Description |
|
The current implementation of $rename treats as an error any rename operation with a source path that is "non-viable": .e.g., attempting to rename "a.b" in a document that contains {a: 1}. The check for that includes a TODO noting that we could instead treat this as a no-op, as we do for any $rename with a non-existent source path. If we do want to make that change, now would be a good time, as we are making backwards-incompatible changes to update functionality. |