Closed GoogleCodeExporter closed 9 years ago
I think mk-table-sync's behavior with NDB Cluster is virtually unknown. There
are
probably a lot of special cases to consider.
Original comment by baron.schwartz
on 19 Sep 2008 at 2:22
Original comment by baron.schwartz
on 1 Oct 2008 at 3:13
Issue 127 has been merged into this issue.
Original comment by baron.schwartz
on 25 Dec 2008 at 10:09
This is an issue in ordinary MySQL servers too. See issue 127; there are
important
comments there. There are not enough resources to devote to this issue right
now, so
if it's important to you, consider sponsoring the development to fix it, or
submit a
well-tested patch.
Summary was: mk-table-sync reports a lot of statement to execute in a 2 clusters
w/replication architecture
Original comment by baron.schwartz
on 25 Dec 2008 at 10:13
Target these for release end of January 2009.
Original comment by baron.schwartz
on 4 Jan 2009 at 5:04
Remove old milestone label.
Original comment by dan...@percona.com
on 1 Jul 2009 at 2:11
Original comment by dan...@percona.com
on 1 Jul 2009 at 2:14
Original comment by dan...@percona.com
on 2 Sep 2009 at 2:26
what does these no comment changes mean ?
Original comment by cscet...@gmail.com
on 2 Sep 2009 at 8:27
They mean we've changed a label, like changing Type-Enhancement to Type-Defect,
or
adding/removing a milestone label. So, they're "administrative" stuff.
Original comment by dan...@percona.com
on 3 Sep 2009 at 12:33
patch against 4623 for:
* making Nibble method work by adding ORDER BY;
* missing crc's initialisation.
Original comment by vova.kol...@gmail.com
on 15 Sep 2009 at 9:16
Attachments:
The latest mk-table-sync now does ORDER BY key_cols. Can the original poster
try the
newest version?
Removed Aug'09 milestone label.
Original comment by dan...@percona.com
on 2 Oct 2009 at 2:58
ORDER BY fix confirmed,
thank you.
Original comment by vova.kol...@gmail.com
on 2 Oct 2009 at 6:31
Thanks for confirming this.
Original comment by dan...@percona.com
on 26 Oct 2009 at 4:31
thank you for the patch !
Original comment by cscet...@gmail.com
on 9 Sep 2010 at 8:50
Original issue reported on code.google.com by
cscet...@gmail.com
on 17 Sep 2008 at 4:37