[SERVER-76936] Normalize error handling in case of non-droppable collections Created: 09/May/23 Updated: 10/May/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
The DatabaseImpl::isDroppableCollection function checks if the namespace complies with naming restrictions and therefore can be dropped. In the event of an error, in some cases it returns a Status in others it throws an exception. Goal of this ticket if to normalize these error cases taking into account any implications on how callers behave in case of error. |