Status: Open (View Workflow)
Fix Version/s: None
Upstream MyRocks has this patch:
For the user, the server has a global @@slave_gtid_info variable. Possible values are ON, OFF, OPTIMIZED. OPTIMIZED only works for MyRocks and means that the storage engine takes care of maintaining the mysql.slave_gtid_info table.
ha_rocksdb.cc has code that manually updates slave_gtid_info to reflect the binlog position.
MariaDB's equivalent of slave_gtid_info is called gtid_slave_pos.
MariaDB currently doesn't have the SQL part of this feature. We could port it, but
- it may be hard to put something like this into MariaDB 10.2
- this does not seem like a priority task?
MDEV-12179, per-engine gtid_slave_pos. It is only in MariaDB-10.3, though.