parse gtid for parseHandler if MySQL works in GTID_MODE, and begin to startWithGTID after mysqldump is done

[jianhaiqing]

Purpose of This PR:

1. if MySQL is GTID_MODE=ON, canal would be start to replicate with GTID after mysqldump is done.
2. Add one more func GtidSet() for parseHandler, to save gtid set after parsing gtid from mysqldump.

[siddontang]

PTAL @GregoryIan

[siddontang]

CI failed @jianhaiqing

[jianhaiqing]

More details about GTID between MySQL and MariaDB.
mysqldump --set-gtid-purged from MySQL is not compatible with mysqldump of MariaDB, while MariaDB use --gtid instead

 [MariaDB]
 mysqldump --host=`hostname -i` --port=3306 --user=root --password=my-secret-pw --master-data --gtid --single-transaction --skip-lock-tables --compact --skip-opt --quick --no-create-info --skip-extended-insert --skip-tz-utc --hex-blob --default-character-set=utf8 longrun t6

-- CHANGE MASTER TO MASTER_LOG_FILE='mariadb-bin.000001', MASTER_LOG_POS=1138;
CHANGE MASTER TO MASTER_USE_GTID=slave_pos;
SET GLOBAL gtid_slave_pos='0-1-4';
INSERT INTO `t6` VALUES (1,11);
INSERT INTO `t6` VALUES (2,11);

[MySQL]
mysqldump --host=`hostname -i` --port=23306 --user=root --password=my-secret-pw --master-data --set-gtid-purged --single-transaction --skip-lock-tables --compact --skip-opt --quick --no-create-info --skip-extended-insert --skip-tz-utc --hex-blob --default-character-set=utf8 longrun t6

SET @MYSQLDUMP_TEMP_LOG_BIN = @@SESSION.SQL_LOG_BIN;
SET @@SESSION.SQL_LOG_BIN= 0;
SET @@GLOBAL.GTID_PURGED='5906b63d-4009-11e9-81f3-00505690245b:1-144473,
abc8b882-b168-11e8-a790-1866daabb9a4:1-3439091213';
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000258', MASTER_LOG_POS=4372;
INSERT INTO `t6` VALUES (1,11);
INSERT INTO `t6` VALUES (2,11);
INSERT INTO `t6` VALUES (3,11);
SET @@SESSION.SQL_LOG_BIN = @MYSQLDUMP_TEMP_LOG_BIN;

[IANTHEREAL]

@WangXiangUSTC PTAL

[IANTHEREAL]

I'm not quite understand the purpose of this pr, do you want to automatically replicate binlog data starting from gtid if gtid is turned on for both the source database and the target data?

[jianhaiqing]

I'm not quite understand the purpose of this pr, do you want to automatically replicate binlog data starting from gtid if gtid is turned on for both the source database and the target data?

Yes, if replicate start with GTID, it would be easier to continue to replicate after master-slave switch occurs.

[jianhaiqing]

As you know, there might be SLB in front of master or slave, so gtid replication would be better.

[jianhaiqing]

Purpose of This PR:

1. if MySQL is GTID_MODE=ON, canal would be start to replicate with GTID after mysqldump is done.
2. Add one more func GtidSet() for parseHandler, to save gtid set after parsing gtid from mysqldump.

[WangXiangUSTC]

Purpose of This PR:

1. if MySQL is GTID_MODE=ON, canal would be start to replicate with GTID after mysqldump is done.
2. Add one more func GtidSet() for parseHandler, to save gtid set after parsing gtid from mysqldump.

can update thease description in the first comment

[WangXiangUSTC]

LGTM

[siddontang]

Rest LGTM