Summary

The GridFS spec says that when a user attempts to delete a GridFS file and its files collection document is not found, "Drivers MAY attempt to delete any orphaned chunks with files_id equal to id." There is no strong reason for this to be optional. It should be updated to a "MUST" requirement.

Motivation

Who is the affected end user?

GridFS users who have orphaned file chunks.

How does this affect the end user?

There is a larger possibility of orphaned chunks being left in the chunks collection.

How likely is it that this problem or use case will occur?

Moderate likelihood: requires a midway failure to have occurred in a previous GridFS operation to create orphaned chunks.

If the problem does occur, what are the consequences and how severe are they?

A user could be storing more data than needed.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No.

Acceptance Criteria

• Amend the spec language from MAY to MUST.
• Add a unified test with command monitoring.