Bug #103983 | Native cloning should work with BLACKHOLE tables (e.g. just copy definition) | ||
---|---|---|---|
Submitted: | 11 Jun 2021 16:40 | Modified: | 30 Oct 2023 17:22 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Clone Plugin | Severity: | S4 (Feature request) |
Version: | 8.0, 8.1, 8.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | 8.0, 8.1, 8.2, blackhole, cloning, native_cloning |
[11 Jun 2021 16:40]
Simon Mudd
[12 Jun 2021 7:19]
MySQL Verification Team
Hello Simon, Thank you for the reasonable feature request! regards, Umesh
[30 Oct 2023 17:22]
Simon Mudd
While I use native cloning a lot for cloning servers using traditional replication, this is also a blocker for moving to Group Replication as GR will also refuse to clone (and work) if blackhole tables are present. Again, while the blackhole table type might seem somewhat strange there are a few use cases where it can be useful so supporting this for DML and DDL and GR actually turns out to be useful in a number of different scenarios. Remember all that's needed is for the table definition to be copied over between hosts as no data copy is needed.