[SERVER-27609] Move internal CollectionMetadata checks in MigrationSourceManager to CollectionMetadata Created: 09/Jan/17 Updated: 27/Oct/23 Resolved: 10/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
MigrationSourceManager checks that CollectionMetadata is set properly – collVersion, keyPattern. https://github.com/mongodb/mongo/blob/cdc7af4c6d453b8c1ce2319d0cd3b50074609d87/src/mongo/db/s/migration_source_manager.cpp#L145-L149 This should be something that CollectionMetadata assures, rather than specifically checked by CollectionMetadata users. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 10/Nov/17 ] |
|
I agree that the issues described are no longer extant. |
| Comment by Kaloian Manassiev [ 10/Nov/17 ] |
|
dianna.hohensee, I believe this was fixed as part of the rewrite of the catalog cache. Do you mind checking if this was already done and close it if so? |