Bug #71339 Manual does not show how to pass "sets" to GTID_SUBSET() etc
Submitted: 10 Jan 2014 9:13 Modified: 23 Jan 2014 12:21
Reporter: Valeriy Kravchuk Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6 OS:Any
Assigned to: Jon Stephens CPU Architecture:Any
Tags: GTID_SUBSET, GTID_SUBTRACT, missing manual

[10 Jan 2014 9:13] Valeriy Kravchuk
Description:
We have entire manual page, http://dev.mysql.com/doc/refman/5.6/en/gtid-functions.html, about new GTID functions. Unfortunately it does give explanations on how to pass GTID sets to some of the functions.

One can infer something from common sense, example of passing single GTID (as a string literal) and http://dev.mysql.com/doc/refman/5.6/en/replication-gtids-concepts.html (that defines a kind of formal syntax for GTID set), but even there it is not formally clear than one needs to use quotes around the entire set of GTIDs separated by commas:

mysql> select GTID_SUBSET('3E11FA47-71CA-11E1-9E33-C80AA9429562:1-5',
    -> '3E11FA47-71CA-11E1-9E33-C80AA9429562:1-5,3E11FA47-71CA-11E1-9E33-C80AA9429562:1-6') as a;
+---+
| a |
+---+
| 1 |
+---+
1 row in set (0.00 sec)

mysql> select GTID_SUBSET('3E11FA47-71CA-11E1-9E33-C80AA9429562:1-7',
    -> '3E11FA47-71CA-11E1-9E33-C80AA9429562:1-5,3E11FA47-71CA-11E1-9E33-C80AA9429562:1-6') as a;
+---+
| a |
+---+
| 0 |
+---+
1 row in set (0.00 sec)

How to repeat:
Try to find on this manual page how to pass GTID set to any GTID function:

http://dev.mysql.com/doc/refman/5.6/en/gtid-functions.html

Suggested fix:
Make sure that manual explains new features and functions with examples covering real use.
[17 Jan 2014 11:27] MySQL Verification Team
Hello Valeriy,

Thank you for the report.

Thanks,
Umesh
[23 Jan 2014 12:21] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Fixed in mysqldoc rev 37484. Closed.