Bug #81862 | Japanese doc's search returns wrong result | ||
---|---|---|---|
Submitted: | 15 Jun 2016 10:52 | Modified: | 16 Jun 2016 4:03 |
Reporter: | Tsubasa Tanaka (OCA) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Japanese Documentation | Severity: | S3 (Non-critical) |
Version: | 5.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | http://dev.mysql.com/doc/search |
[15 Jun 2016 10:52]
Tsubasa Tanaka
[15 Jun 2016 11:20]
MySQL Verification Team
Hello Tanaka-San, Thank you for the report and feedback! Thanks, Umesh
[16 Jun 2016 1:11]
Tsubasa Tanaka
I can reproduce this on MySQL 5.7.13's ngram parser. This depends on NATURAL LANGUAGE MODE or BOOLEAN MODE. Thus, this maybe Not a Bug. ``` $ curl http://dev.mysql.com/doc/refman/5.6/ja/checking-gpg-signature.html > test $ mysqladmin create d1 $ mysql d1 mysql> CREATE TABLE t1 (txt LONGTEXT, FULLTEXT KEY(txt) WITH PARSER ngram); mysql> INSERT INTO t1 VALUES (LOAD_FILE('/home/yoku0825/test')); mysql> SELECT 1 FROM t1 WHERE MATCH(txt) AGAINST('MeCab'); +---+ | 1 | +---+ | 1 | +---+ 1 row in set (0.00 sec) mysql57> SELECT 1 FROM t1 WHERE MATCH(txt) AGAINST('MeCab' IN BOOLEAN MODE); Empty set (0.00 sec) ``` This maybe expected behavior, Not a Bug, just ngram FT parser with NATURAL LANGUAGE MODE query is ill-suited...(this is another problem of this report) Would you mark this issue as "Not a Bug"?
[16 Jun 2016 4:03]
MySQL Verification Team
Thank you for confirming, as requested in previous note marking this issue as Not a Bug for now. Thanks, Umesh