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

[4 Feb 2006 11:54] Hartmut Holzgraefe
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
[8 Feb 2006 16:17] Jorge del Conde
I got the same problem under FC4 using a recent clone of 5.1
[16 Feb 2006 11:39] Bugs System
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
[21 Feb 2006 14:30] Sergey Vojtovich
Fixed in 5.1.8
[28 Feb 2006 0:51] Paul DuBois
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)

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.