[SERVER-32109] $rename does not update value if existing "to" field has the same numeric value but different type. Created: 29/Nov/17 Updated: 30/Oct/23 Resolved: 13/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.6.0-rc6 |
| Fix Version/s: | 3.6.1, 3.7.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Justin Seyster |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ufz | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v3.6
|
||||
| Sprint: | Query 2017-12-04, Query 2017-12-18 | ||||
| Participants: | |||||
| Description |
|
On 3.6, a $rename operator applied to a destination field that already exists, and has the same value as the source field, will not update that field. On 3.4, the field type is changed as expected.
|
| Comments |
| Comment by Githook User [ 13/Dec/17 ] |
|
Author: {'name': 'Justin Seyster', 'email': 'justin.seyster@mongodb.com', 'username': 'jseyster'}Message: Before this change, a {$rename: {from: "to"}} would check to see if We could use a precise equality check, but it's more expensive. More (cherry picked from commit 4d53b4beb00eaa341bf2a134fbc9366d3333e830) |
| Comment by Githook User [ 13/Dec/17 ] |
|
Author: {'name': 'Justin Seyster', 'email': 'justin.seyster@mongodb.com', 'username': 'jseyster'}Message: Before this change, a {$rename: {from: "to"}} would check to see if We could use a precise equality check, but it's more expensive. More |
| Comment by David Storch [ 29/Nov/17 ] |
|
Great find, robert.guo. Another gem from the generational fuzzer I presume? |