Bug #76164 | InnoDB FTS with MeCab parser prints empty error message | ||
---|---|---|---|
Submitted: | 5 Mar 2015 6:28 | Modified: | 17 Mar 2015 23:48 |
Reporter: | Tsubasa Tanaka (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: FULLTEXT search | Severity: | S3 (Non-critical) |
Version: | 5.7.6, 5.7.7 | OS: | Linux (CentOS 6.5) |
Assigned to: | CPU Architecture: | Any | |
Tags: | error, fulltext, MeCab |
[5 Mar 2015 6:28]
Tsubasa Tanaka
[5 Mar 2015 7:24]
MySQL Verification Team
Hello tanaka-san, Thank you for the report and test case. Thanks, Umesh
[5 Mar 2015 7:25]
MySQL Verification Team
// 5.7.7 [umshastr@hod03]/export/umesh/mysql-5.7.7: bin/mysql -uroot -p -S /tmp/mysql_ushastry.sock Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.7.7-rc-enterprise-commercial-advanced MySQL Enterprise Server - Advanced Edition (Commercial) Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> show plugins; +----------------------------+----------+--------------------+-------------------+-------------+ | Name | Status | Type | Library | License | +----------------------------+----------+--------------------+-------------------+-------------+ .. | mecab | ACTIVE | FTPARSER | libpluginmecab.so | PROPRIETARY | +----------------------------+----------+--------------------+-------------------+-------------+ 44 rows in set (0.00 sec) mysql> use test Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> CREATE TABLE t1 (val longtext, FULLTEXT KEY (val) WITH PARSER MeCab)Engine= InnoDB CHARACTER SET= utf8; Query OK, 0 rows affected (0.01 sec) mysql> INSERT INTO t1 VALUES (LOAD_FILE('/export/umesh/mysql-5.7.7/sample.txt')); Query OK, 1 row affected (0.08 sec) mysql> quit Bye // Extract from error log 2015-03-05T07:19:02.452734Z 0 [Note] /export/umesh/mysql-5.7.7/bin/mysqld: ready for connections. Version: '5.7.7-rc-enterprise-commercial-advanced' socket: '/tmp/mysql_ushastry.sock' port: 15000 MySQL Enterprise Server - Advanced Edition (Commercial) 2015-03-05T07:20:19.047071Z 2 [ERROR] Mecab:
[13 Mar 2015 13:56]
Shaohua Wang
Posted by developer: The actual error is "too long sentence", but I don't know what exactly is the limit in mecab yet.
[13 Mar 2015 15:44]
Tsubasa Tanaka
I've confirmed that is "too long sentence" error too. But that isn't problem. The issue is "mecab_parser_print_error can't handle error-message from mecab library". MeCab library's limit doesn't matter.
[16 Mar 2015 2:14]
Shaohua Wang
Posted by developer: Yes, we will fix the message issue. Thanks for reporting the bug!
[17 Mar 2015 23:48]
Daniel Price
Posted by developer: Fixed as of the upcoming 5.7.8, 5.8.0 releases, and here's the changelog entry: The "InnoDB" full-text search feature with the mecab parser plugin would print an empty error message.