Save YAML with problems found during checksumming
Registered by
markus_albe
Make possible to have an easily parseable structure to find skipped tables, tables that couldn't be checksummed and other unexpected events (can't think of one right now) that could lead to undetected inconsistencies in the slaves. This allows for automation of checksumming (errors in the process could be checked using programmatic means, instead of parsing output), and would be helpful for very large checksums where going through the output is rather tedious (--replicate-check could use it to ouput summary of issues along with summary of found inconsitencies)
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)