[SERVER-43325] Not all exceptions inside collection validation should result in {valid: false} Created: 13/Sep/19 Updated: 22/Aug/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The entire collection validation code block is wrapped inside of a `try catch` block. |
| Comments |
| Comment by Gregory Wlodarek [ 02/Apr/20 ] |
|
I think catching exceptions in the outermost level of validate shouldn't be automatically treated as corruption being detected as that may not always be the case. I'd be okay with simply returning {ok: 0} in these cases, but that still leaves the question of what should the valid field be set to. Perhaps omitting the valid field, in these cases, is fine. |
| Comment by Connie Chen [ 02/Apr/20 ] |
|
gregory.wlodarek Is this still a problem? |