[SERVER-28742] Assign and persist a table/index key prefix for grouped collections Created: 11/Apr/17 Updated: 12/Oct/17 Resolved: 15/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage 2017-05-08, Storage 2017-05-29 |
| Participants: |
| Description |
|
When wiredtiger is running in --groupCollections mode, a prefix must be assigned to each new collection and index to correctly disambiguate and order keys passed to WT sharing the same table. These prefixes should be persisted (to the catalog or an internal WT table invisible to above layers) as well added to WiredTigerRecordStore and WiredTigerIndex objects at construction. Prefixes must be unique for all live collections and indexes. Reusing a prefix can result in records in different collections colliding. If convenient, a prefix may be used once for a record store and once for an index. The oplog collection and its index(es) should reside in their own table and not be prefixed. |
| Comments |
| Comment by Githook User [ 15/May/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: |
| Comment by Githook User [ 05/May/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: Revert " This reverts commit 867eda89f5451408c9ba96eaa1035c89f3401bb1. |
| Comment by Githook User [ 05/May/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: |