[SERVER-40313] Parsing table logging settings should ignore user-provided input Created: 22/Mar/19 Updated: 06/Dec/22 Resolved: 15/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.7, 4.1.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | 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 | ||||
| Sprint: | Execution Team 2020-06-29 | ||||
| Participants: | |||||
| Linked BF Score: | 3 | ||||
| Description |
|
When we change table logging settings and parses the index metadata, the server crashes if the metadata happens to contain both "log=(enabled=true)" and "log=(enabled=false)". This parsing more robust so that it is not possible to accidentally parse any user-provided strings. It is also possible that the metadata is structured such that table logging is not enabled altogether, which is a more subtle failure. |
| Comments |
| Comment by Louis Williams [ 15/Jun/20 ] |
|
I'm closing this ticket because it's not necessary after |