MySQL Bugs: #70401: Make "doesn't support FULLTXT parser plugins" error generic, not engine specific

Bug #70401	Make "doesn't support FULLTXT parser plugins" error generic, not engine specific
Submitted:	23 Sep 2013 11:45
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server: FULLTEXT search	Severity:	S4 (Feature request)
Version:	5.6.13	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
As fix for the missing error reported in bug #62004 a new error code 

  ER_INNODB_NO_FT_USES_PARSER

was introduced with the associated error message

  Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table

While InnoDB is currently the only engine supporting FULLTEXT indexes but not fulltext parser plugins it doesn't seem to make sense to be that specific in the error name and message as there is at least a slight chance that other engines may implement FT with the same limitation ...

How to repeat:
Check e.g. ./sql/share/errmsg-utf8.txt:

  ER_TABLE_HAS_NO_FT
    eng "The table does not have FULLTEXT index to support this query"

vs.

  ER_INNODB_NO_FT_USES_PARSER
    eng "Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table"

Suggested fix:
Rename the error code to e.g.

  ER_TABLE_NO_FT_USES_PARSER
    eng "Storage engine does not support WITH PARSER on FULLTEXT INDEX"

to make reuse with other engines possible