[MDEV-14519] Add mapping for encryption key ID while doing IMPORT TABLESPACE Created: 2017-11-28 Updated: 2020-12-15 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Encryption, Storage Engine - InnoDB |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Valerii Kravchuk | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
We need some mechanism to remap the encryption key IDs when importing a tablespace. It may be simplest to make IMPORT TABLESPACE to look for a new file, tablename.enc (or similar), which would contain a mapping from old encryption key IDs (and key versions) to the correspond ones in the importing server. Typical use case is along the following lines: 1. Export encrypted table(s) from backup on source. Let's assume they are encrypted with default key or key #M on source |