TRUNCATE is equivalent to DROP + CREATE. Which means to fix this bug we should filter tablespace creation operations when preparing a partial backup based on the original pattern which was used to create the partial backup.
A related problem is when during a partial backup a regular CREATE TABLE is executed for a InnoDB table which does not match the filters. It would still be present in the resulting backup after prepare, but that's not what users would expect.
TRUNCATE is equivalent to DROP + CREATE. Which means to fix this bug we should filter tablespace creation operations when preparing a partial backup based on the original pattern which was used to create the partial backup.
A related problem is when during a partial backup a regular CREATE TABLE is executed for a InnoDB table which does not match the filters. It would still be present in the resulting backup after prepare, but that's not what users would expect.