[SERVER-69532] Limit the number of logs of non-conformant BSON or schema violating documents Created: 08/Sep/22 Updated: 14/Aug/23 Resolved: 14/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
In rare cases, we might have customers having a large number of non-conformant BSON documents injected into the collection throughout the years with the same type of issue. We might not want to saturate the log with the similar problem. Same for schema validation, as the user can easily set bypassing the schema check when inserting data. |
| Comments |
| Comment by Connie Chen [ 14/Aug/23 ] |
|
Closing as won't do because validation logging is meant to be verbose and if we limit the number of logs when we fix the issues, you won't be able to confirm it's been fixed. |