[SERVER-42038] "The key is too long" after upgrading from 3.4 to 3.6 Created: 02/Jul/19 Updated: 27/Oct/23 Resolved: 16/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.21, 3.6.13 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vincent van Megen | Assignee: | Eric Sedor |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Upgrade from 3.4.21 to 3.6 and run a update query. |
| Participants: |
| Description |
|
After upgrading from 3.4 to 3.6 i'm getting the following errors when running simple update on some documents:
The updateOne command is updateOne({'_id': mongid}, {'$set': {'status': 'OK'}}) Downgrading to 3.4 solves this issue. PHP mongodb version 1.5.5 db version v3.4.21
Running on 3 dedicated servers in a replicaset (64gb ram, 1tb ssd, 8 cores). |
| Comments |
| Comment by Eric Sedor [ 16/Jul/19 ] |
|
vincentvm I am going to close this ticket but if you have additional information it may help users who find this issue in the future. Thanks again! |
| Comment by Eric Sedor [ 03/Jul/19 ] |
|
vincentvm; we can close this ticket if you no longer have a problem. But if you can provide details about what you found to be incorrect about the _id value and what you changed to resolve the issue, it may help other users in the future. |
| Comment by Vincent van Megen [ 02/Jul/19 ] |
|
This has been resolved, apparently 3.4 didn't complain about incorrect mongoid's. |