[SERVER-29066] Sharded findAndModify will not implicitly create the database if it does not exist Created: 04/May/17 Updated: 30/Oct/23 Resolved: 05/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.5, 3.5.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||
| Operating System: | ALL | ||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||
| Steps To Reproduce: | Start a ShardingTest and run:
|
||||||||||||||
| Sprint: | Sharding 2017-05-29 | ||||||||||||||
| Participants: | |||||||||||||||
| Description |
|
The sharded findAndModify will fail with NamespaceNotFound error if the database does not exist. The problem was introduced by this change. |
| Comments |
| Comment by Githook User [ 14/Jun/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 06/May/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 05/May/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |