Bug #80858 | Make setting of READ_BACKUP to 1 an inplace ALTER TABLE operation | ||
---|---|---|---|
Submitted: | 25 Mar 2016 9:00 | Modified: | 21 Jun 2016 12:13 |
Reporter: | Mikael Ronström | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[25 Mar 2016 9:00]
Mikael Ronström
[21 Jun 2016 12:13]
Jon Stephens
Documented fix in the NDB 7.5.3 changelog as follows: It is now possible to set READ_BACKUP for an existing table online using ALTER TABLE ... ALGORITHM=INPLACE, COMMENT="NDB_TABLE=READ_BACKUP=1" (Bug #80858, Bug #23001617). See "Setting NDB_TABLE options in table comments", for further information about the READ_BACKUP option. Also updated the indicated portion of the documentation. Closed.