Unable to migrate to Cloud SQL because of lack of ability to skip replication errors. Much needed feature.

[Sameer Panjwani]

I have made 4 attempts thus far in migrating my DB from an external server to GCloud SQL 2nd Gen but have failed every time. 

The mysqldump process was successfully completed. Close to 2TB data was successfully imported into the cloud and the replication process successfully started. However, for some reason or the other, would get a 1062 duplicate error. I couldn't figure a way to skip it because of the lack of a SUPER privilege. I know those errors can be ignored but I'm not allowed to set any variable to tell the replication to skip 1062 errors. 

I would then just make another attempt, re-dumping the DB (it takes a few days cos of the size), then again resuming replication, only to face the same issue just before it can reach the final sync.

I need some solution to figure this out, quite tired of trying from scratch every time, this gone on for a few weeks and wasted bills as well.

[Yasser Karout]

Hello,

I noticed you posted this issue twice. Please use the initial post to keep of track of the discussion more easily [1].

[1] https://groups.google.com/forum/#!topic/google-cloud-sql-discuss/N5URxQatCo0