MySQL Bugs: #13448: Partitions: fulltext searches fail

Bug #13448	Partitions: fulltext searches fail
Submitted:	23 Sep 2005 17:46	Modified:	31 Oct 2005 22:00
Reporter:	Peter Gulutzan	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Partitions	Severity:	S3 (Non-critical)
Version:	5.1.2-alpha-debug	OS:	Linux (SUSE 9.2)
Assigned to:	Mikael Ronström	CPU Architecture:	Any

Description:
If I create an 'articles' table just like the one
in the example in the MySQL Reference Manual, but
I say it's a partitioned table, I can't search.
I get the message
Table storage engine for 'articles' doesn't have this option
-- which is false, the storage engine is MyISAM.

How to repeat:
mysql> CREATE TABLE articles (
    ->        id INT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY,
    ->        title VARCHAR(200),
    ->        body TEXT,
    ->        FULLTEXT (title,body)
    ->      )
    ->      PARTITION BY HASH(id) PARTITIONS 6;
Query OK, 0 rows affected (0.02 sec)

mysql> INSERT INTO articles (title,body) VALUES
    ->      ('MySQL Tutorial','DBMS stands for DataBase ...'),
    ->      ('How To Use MySQL Well','After you went through a ...'),
    ->      ('Optimizing MySQL','In this tutorial we will show ...'),
    ->      ('1001 MySQL Tricks','1. Never run mysqld as root. 2. ...'),
    ->      ('MySQL vs. YourSQL','In the following database comparison ...'),
    ->      ('MySQL Security','When configured properly, MySQL ...');
Query OK, 6 rows affected (0.01 sec)
Records: 6  Duplicates: 0  Warnings: 0

mysql> SELECT * FROM articles
    ->      WHERE MATCH (title,body) AGAINST ('database');
ERROR 1031 (HY000): Table storage engine for 'articles' doesn't have this option

Fulltext Indexes isn't supported by the partition handler. Not even when the
underlying storage engine is MyISAM.

As I understand it, "Need Doc Info" is inappropriate for this situation, so I changed back to "Verified".

This is not a bug

Not a bug?!  It is if it doesn't appear in the documentation.  I've been trying to get this to work for 3 days only to find out that the function doesn't work as documented!!!

Related to bug#56590.