[DRIVERS-2807] Update GridFS spec for a performant "rename all revisions by filename" feature Created: 08/Jan/24 Updated: 09/Jan/24 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | GridFS |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Jérôme Tamarelle | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Driver Changes: | Not Needed | ||||||||||||||||
| Description |
SummaryThe spec doesn't provide an API to rename every revisions of a filename. The proposed implementation is inefficient as it requires doing an update_one command for each revision, while it's more efficient to do an update_many with the filename as criteria.
The rename by filename API is necessary for PHP Stream Wrapper. MotivationWho is the affected end user?Applications that use a lot of revisions of the same filename. How does this affect the end user?Bad performance scaling when the number of revisions grows How likely is it that this problem or use case will occur?Edge case, maybe an incorrect usage of GridFS. If the problem does occur, what are the consequences and how severe are they?Degraded performances Is this issue urgent?No Is this ticket required by a downstream team?PHPLIB implementation of GridFS stream wrapper Is this ticket only for tests?No Acceptance CriteriaUpdate the spec to give a performant way to rename all revisions of a filename |
| Comments |
| Comment by Tom Selander [ 09/Jan/24 ] |
|
Triage: Minor spec changes and mostly edge cases, should be OK to backlog |