Bug #47250 blackhole+fulltext search cause uneeded 'Got error 131 when reading table'
Submitted: 10 Sep 2009 13:16 Modified: 10 Sep 2009 14:12
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:5.0.88,5.1.38,5.5.99-m3 OS:Any
Assigned to: CPU Architecture:Any

[10 Sep 2009 13:16] Shane Bester
trying to do fulltext searches on a table supposedly not supporting it pollutes the error logs with:

[ERROR] Got error 131 when reading table '.\test\t1'

mysql client gets this message:

mysql> select * from t1 where match(a) against ('');
ERROR 1031 (HY000): Table storage engine for 't1' doesn't have this option

How to repeat:
drop table if exists t1;
create table t1(a char(1),fulltext key(a))engine=blackhole;
select * from t1 where match(a) against ('');

Suggested fix:
if blackhole doesn't support full text matches, then don't allow the table to be created in the first place. and don't print that error into the logs.
[10 Sep 2009 14:12] Valeriy Kravchuk
Thank you for the problem report.