Bug #80708 | Problem importing encrypted tablespace | ||
---|---|---|---|
Submitted: | 11 Mar 2016 18:24 | Modified: | 7 Apr 2016 16:41 |
Reporter: | Sergei Glushchenko | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.7.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[11 Mar 2016 18:24]
Sergei Glushchenko
[12 Mar 2016 5:26]
MySQL Verification Team
Hello Sergei, Thank you for the report and test case. Thanks, Umesh
[7 Apr 2016 16:41]
Daniel Price
Posted by developer: Fixed as of the upcoming 5.7.13 release, and here's the changelog entry: An ALTER TABLE ... IMPORT TABLESPACE operation on file-per-table tablespace containing an encrypted table failed when run in a different session than the preceding ALTER TABLE ... DISCARD TABLESPACE operation. Thank you for the bug report.