Bug #76450 generated column with "KEY" makes PRIMARY KEY

Description:
When creating generated column with "KEY" keyword, MySQL always tries to make PRIMARY KEY.

Is that an expected behavier? (that means doc is not enough)
Or a Parser's bug?

I expected "KEY", not "PRIMARY"/"UNIQUE", makes SECONDARY INDEX.

http://dev.mysql.com/doc/refman/5.7/en/create-table.html#create-table-generated-columns

How to repeat:
mysql57> CREATE TABLE t2 (num int, val varchar(32) AS (md5(num)) STORED KEY);
Query OK, 0 rows affected (0.03 sec)

mysql57> SHOW CREATE TABLE t2\G
*************************** 1. row ***************************
       Table: t2
Create Table: CREATE TABLE `t2` (
  `num` int(11) DEFAULT NULL,
  `val` varchar(32) GENERATED ALWAYS AS (md5(num)) STORED NOT NULL,
  PRIMARY KEY (`val`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
1 row in set (0.00 sec)

Hello Tanaka-San,

Thank you for the report.

Thanks,
Umesh

Posted by developer:
 
Generated columns follow the same syntax as ordinary columns.  For ordinary columns, the manual already says: 
"The key attribute PRIMARY KEY can also be specified as just KEY when given in a column definition." 
(http://dev.mysql.com/doc/refman/5.7/en/create-table.html)

I confirmed that you're correct.

mysql57> create table t1 (num int key);
Query OK, 0 rows affected (0.04 sec)

mysql57> show create table t1\G
*************************** 1. row ***************************
       Table: t1
Create Table: CREATE TABLE `t1` (
  `num` int(11) NOT NULL,
  PRIMARY KEY (`num`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
1 row in set (0.00 sec)

I change this case's status to "Closed", and I'm sorry to taking your time.
Thanks,