MySQL Bugs: #17116: myisam_ftdump doesn't work with fulltext indexes using a parser plugin

Bug #17116	myisam_ftdump doesn't work with fulltext indexes using a parser plugin
Submitted:	4 Feb 2006 11:54	Modified:	28 Feb 2006 0:51
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S3 (Non-critical)
Version:	5.1	OS:
Assigned to:	Sergey Vojtovich	CPU Architecture:	Any

Description:
As far as i understand the actual fulltext index storage format is always the same 
even if a parser plugin is used, but myisam_ftdump refuses to work with such 
tables.

On the other hand mtisam_ftdump would be extremly usefully for debugging
when writing a fulltext parser plugin.

How to repeat:
create a table using a fulltext parser plugin as documented in

  http://dev.mysql.com/doc/refman/5.1/en/plugin-creating.html

now try to analyze the index contents using myisam_ftdump:

$ myisam_ftdump t 0
got error 138

I got the same problem under FC4 using a recent clone of 5.1

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2719

Fixed in 5.1.8

Noted in 5.1.7 changelog.

<command>myisam_ftdump</command> did not work for
<literal>FULLTEXT</literal> indexes associated with a parser
plugin. (Bug #17116)