MySQL Bugs: #54335: MCM should accept mysqld config variables containing "-" as well as "

Bug #54335	MCM should accept mysqld config variables containing "-" as well as "_"
Submitted:	8 Jun 2010 13:08	Modified:	23 Feb 2015 17:43
Reporter:	Erlend Dahl	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster Manager: CLI	Severity:	S4 (Feature request)
Version:	1.x	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
In bug#50099, MCM was changed to consistently use "_" in mysqld config variable names.

Support indicates that it would be desirable to accept forms contaning "_" and "-" as equivalent.

So 

set ndb_cluster_connection_pool:mysqld=12 mycluster;

and

set ndb-cluster-connection-pool:mysqld=12 mycluster;

would both be accepted and produce the same result. Similar for the get command.

See also bug#54294 about documenting the current state of affairs.

How to repeat:
As above.

See http://dev.mysql.com/doc/refman/5.1/en/command-line-options.html

"Within option names, dash (“-”) and underscore (“_”) may be used interchangeably. For example, --skip-grant-tables and --skip_grant_tables  are equivalent. (However, the leading dashes cannot be given as underscores.)"

This applies to all MySQL programs including mysqld.

Added the following entry to the MySQL Cluster Manager 1.3.4 changelog:

"When referring to cluster attributes in an mcm configuration command (get, reset. or set), dashes (“-”) and underscores (“_”) can now be used interchangeably within attribute names. For example, “set ndb-cluster-connection-pool:mysqld=12 mycluster” now works the same as “set ndb_cluster_connection_pool:mysqld=12 mycluster,” while only the latter was accepted before."