Sergey Vojtovich <svoj@mariadb.org> writes:
* binlog-max-flush-queue-time
This is not needed (it is about MySQL 5.6 group commit, MariaDB uses a different implementation. I suppose one could say it is always set to 0).
* binlog-row-image
This is not merged to 10.0 yet (as far as I know). It looks like it would make sense to merge later though.
* master-info-repository * relay-log-info-repository
This is not merged from 5.6. It is about storing slave configuration and old-style position in tables instead of files. I am not much in favour of merging this, though it could make sense I suppose. Mainly for the configuration part. For the position, the prefered way forward is for users to switch to MariaDB GTID, which has the position crash-safe in a different way and is overall much better.
* binlog-rows-query-log-events
We have another very similar option --binlog-annotate-row-events for this. It does not seem to make sense to merge the MySQL 5.6 implementation. I am not sure if it makes sense to try to make the two compatible somehow, probably only if there is a user request.
* binlog-order-commits
Not used in MariaDB group commit (effectively, it is always enabled).
* server-uuid
Hm, I thought we had this already? I guess not... Anyway, I think the server-uuid feature is stupid, and I would suggest not to merge it. AFAIK, this is anyway only a read-only system variable, it cannot be set in my.cnf or command line...
* server-id-bits
This seems to be an NDB specific option, I think we should not merge it nor implement something compatible.
* slave-allow-batching * slave-rows-search-algorithms
I believe this is a feature that improves efficiency of row-based replication of UPDATE/DELETE on tables with no or poor indexing. We could merge it later, I think.
* slave-checkpoint-period * slave-checkpoint-group
This is about multi-threaded slave which we will not have in MariaDB - we have a different implementation for parallel replication. So they do not make sense in MariaDB. It would be ok to implement dummy do-nothing options for compatibility.
* slave-parallel-workers * slave-pending-jobs-size-max
We have in MariaDB these options which are similar: --slave-parallel-threads --slave-parallel-max-queued
* enforce-gtid-consistency * gtid-mode
This is for MySQL 5.6 GTID, which will not be in MariaDB (we have a completely different GTID implementation). So they should not be implemented, nor should we have dummy options for compatibility.
* rpl-stop-slave-timeout
This is not merged to MariaDB yet, but it seems like it would make sense to do so. Hope this helps, - Kristian.