I understand that MemSQL allows online alter table statements. But, in situations where the best course of action is to create a new table and swap them out, what is possible? My normal pattern for doing such a switch would involve creating triggers on the old table to insert/update the new table with any changes while an insert into occurs. Then performing a rename that should only block the write operations briefly until both the old object and the new object are renamed within a transaction. It is my understanding that triggers only exist in memSQL for timestamps. Is there any best memSQL practice for maintaining changing data while not failing write operations?
Thanks for any suggestions.