[SERVER-37337] Allow operations to be done from subtrees in BiggieSE Created: 27/Sep/18 Updated: 29/Oct/23 Resolved: 19/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage NYC 2018-10-08, Storage NYC 2018-10-22 |
| Participants: |
| Description |
|
Right now, for example, if you were to do a find() operation in Biggie, it would have to start from the root, but in some cases it would be better to start operations in subtrees to improve performance and have more flexible functionality. In addition, this also fixes a few issues when running jstest that makes the storage engine crash, such as retrieving the size of the data, truncating the collection when using --repeat in resmoke.py and the merge() adding children to the incorrect node |
| Comments |
| Comment by Githook User [ 19/Oct/18 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |