[SERVER-9661] config upgrade fails if collection missing "key" field Created: 13/May/13 Updated: 11/Jul/16 Resolved: 13/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.3 |
| Fix Version/s: | 2.4.4, 2.5.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
Seems like, at least in some cases, config upgrade will fail if the "key" field is missing in a config.collections entry. This can happen on a collection drop. |
| Comments |
| Comment by auto [ 22/May/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by auto [ 13/May/13 ] |
|
Author: {u'date': u'2013-05-13T16:30:49Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Greg Studer [ 13/May/13 ] |
|
In 2.4.3, only happens if unique or noBalance was set on the dropped collection. |