Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
-
1.0.7
-
2019-04
Description
Setting up a columnstore table in a slave and replicating to it currently does not work and silently fails. I believe this is because we use master / slave replication in a multi um setup to ensure synchronization of non columnstore lookup tables and columnstore table definitions where we obviously don't want the slave to process any dml since the data is already available.
Another challenge is that columnstore does not have a mode to ignore non supported constructs and so most innodb ddl will fail. This could be worked around by precreating the schema.
Attachments
Issue Links
- duplicates
-
MCOL-1050 when columnstore can be as a replication slave target??
- Closed