Will canceling InnoDB compression that's already in progress corrupt data?
If innodb_file_per_table is enabled, then a temp table is being populated with the new compression. The original table is currently intact, just not writable.

Running KILL QUERY 12345 on the Connection running the ALTER TABLE should do the following:


release the write lock
drop the temp table
leave the original table as is