Bug #82928 X protocol: Please put protobuf message definitions into their own repository
Submitted: 9 Sep 2016 17:04 Modified: 22 Sep 2016 10:33
Reporter: Simon Mudd (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Document Store: X Plugin Severity:S4 (Feature request)
Version:5.7.15 OS:Any
Assigned to: CPU Architecture:Any
Tags: documentation, plugin, x protocol

[9 Sep 2016 17:04] Simon Mudd
Description:
The MySQL X protocol uses as a basis for all communication messages in a format based on Google's protobuf.

If Oracle wants to make the X protocol specification clear and concise these protobuf files should be isolated from their current location buried in the server code to somewhere where it's easy to follow changes to them.

MySQL server or client code can then "import" these public definitions as needed to build the software that's used.
Drivers of software designed to support the MySQL X protocol can also find these definitions more easily.
"Vendors" or owners of other forks of MySQL-like software will also find this easier.

For adoption of the MySQL X protocol to be easy make it easy to grab and use these definitions by any interested party.

Any changes in these files will also be easier to see and follow for all concerned.

How to repeat:
The current code is here:

https://github.com/mysql/mysql-server/tree/5.7/rapid/plugin/x/protocol

but that requires searching on github, or downloading the whole source tree.

I'd rather just grab the specifications from somewhere like here:

https://github.com/sjmudd/mysql-server-rapid-plugin-x-protocol (or better an Oracle equivalent URL)

as this makes importing the data into a driver and keeping it in sync much easier.

Suggested fix:
Please put the protobuf files into their own tiny public repository so it's easier to see if there are changes in the messages or their descriptions.
[22 Sep 2016 10:33] MySQL Verification Team
Hello Simon,

Thank you for the feature request.

Thanks,
Umesh