[MDEV-11920] Allow subsequent table to be automatically encrypted with innodb-encrypt-tables=1 and innodb-encryption-threads=0 Created: 2017-01-26 Updated: 2017-05-25 Resolved: 2017-05-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Encryption, Storage Engine - InnoDB |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Minor |
| Reporter: | Chris Calender (Inactive) | Assignee: | Sergei Golubchik |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Currently, if you have innodb-encrypt-tables=1 (enables encryption) and innodb-encryption-threads=0 (disables background threads due to excessive CPU usage) , then you need to specify ENCRYPTED=YES in the CREATE TABLE command. It would be nice if you did not have to specify ENCRYPTED=YES in the CREATE TABLE command. |
| Comments |
| Comment by Sergei Golubchik [ 2017-05-25 ] |
|
As far as I understand, with innodb-encrypt-tables=1 all new tables are automatically encrypted unless you specify ENCRYPTED=NO. You do not have to specify ENCRYPTED=YES per table in this case. |