| Bug #118590 | Trigger not restored and util.loadDump() fails with MySQLSH 2013 during restoration using MySQL Kubernetes Operator | ||
|---|---|---|---|
| Submitted: | 7 Jul 9:22 | Modified: | 7 Jul 14:52 |
| Reporter: | rahul chaudhari | Email Updates: | |
| Status: | Analyzing | Impact on me: | |
| Category: | MySQL Operator | Severity: | S2 (Serious) |
| Version: | MySQL 8.0.35 | OS: | Linux (Tested on Kubernetes v1.26+ with standard InnoDBCluster CRD.) |
| Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
| Tags: | kubernetes, mysql-operator, mysqlsh, trigger-missing, util.loadDump | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
