MySQL Bugs: #6232: Full-Text Index Problem

Bug #6232	Full-Text Index Problem
Submitted:	24 Oct 2004 8:16	Modified:	25 Oct 2004 8:33
Reporter:	alireza vahedi	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S1 (Critical)
Version:	4.1	OS:	Windows (windows(xp,2000) - linux)
Assigned to:	Sergei Golubchik	CPU Architecture:	Any

Description:
hi
i recently install MySQL 4.1.6-gamma successfully.
my problem is about fulltext index.
I have a database with 10 tables. character set of my databases is UTF-8 and them collations is utf8_persian_ci .
when i want add a fulltext index to my tables 2 case happen:

1.if my table contain only PERSIAN characters, there is no problem.
2.but if my table contain both PERSIAN & ENGLISH characters, MySQL server crashs.

if you want, I can send my table that crashs.
please help me.

i test mysql version 5, but my problem don't solve.

thank you

How to repeat:
hi
i recently install MySQL 4.1.6-gamma successfully.
my problem is about fulltext index.
I have a database with 10 tables. character set of my databases is UTF-8 and them collations is utf8_persian_ci .
when i want add a fulltext index to my tables 2 case happen:

1.if my table contain only PERSIAN characters, there is no problem.
2.but if my table contain both PERSIAN & ENGLISH characters, MySQL server crashs.

if you want, I can send my table that crashs.
please help me.

i test mysql version 5, but my problem don't solve.

thank you

Hi,

Thank you for the report, but we need a repeatable test case. It would be good if you create a small test case, or upload your table and provide an exactly query that crashes MySQL server.

Thanks for the test case!
Could you also show the output of  SHOW VARIABLES statement ?

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Thanks for the test case.

The problem was that your table contained bytes that are not valid utf8 characters. Though mysqld didn't crash for me, it did hang forever.
I now added a protection against it, these bytes are now skipped during the indexing.

Fixed in 4.1.8