Merge lp:~sergei.glushchenko/percona-xtrabackup/transportabe-tablespaces into lp:percona-xtrabackup/2.0
Status: | Merged |
---|---|
Approved by: | Alexey Kopytov |
Approved revision: | no longer in the source branch. |
Merged at revision: | 547 |
Proposed branch: | lp:~sergei.glushchenko/percona-xtrabackup/transportabe-tablespaces |
Merge into: | lp:percona-xtrabackup/2.0 |
Diff against target: |
459 lines (+403/-10) 2 files modified
src/xtrabackup.cc (+391/-4) test/t/xb_export.sh (+12/-6) |
To merge this branch: | bzr merge lp:~sergei.glushchenko/percona-xtrabackup/transportabe-tablespaces |
Related bugs: | |
Related blueprints: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alexey Kopytov (community) | Approve | ||
Review via email: mp+161073@code.launchpad.net |
Description of the change
Blueprint: Support transportable tablespaces in xtrabackup --export
https:/
MySQL 5.6 has a feature which allows user to export InnoDB tablespaces and
import them later. This feature is very similar to XtraDB feature.
Xtrabackup has an option to export single table tablespace from backup.
It dump table metadata in format which InnoDB can recognize (.exp files).
But MySQL has it's own format of metadata stored in .cfg files.
This patch allows Xtrabackup to produce metadata in both formats when
export is performed. The code to support cfg export is copied from
MySQL sources with some modifications.
Existing testcase xb_export.sh has been modified to test export
on MySQL 5.6 as well. It however works even when .cfg is not generated
because bug http://
MySQL 5.6.8. It fails however in case of incorrect or corrupted .cfg
file.
Will post Jenkins link later
http:// jenkins. percona. com/job/ percona- xtrabackup- 2.0-param/ 424/
Not finished yet, but looks promising.