Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parser, builtin: MATCH/AGAINST are not supported #4009

Closed
winkyao opened this issue Aug 3, 2017 · 2 comments
Closed

parser, builtin: MATCH/AGAINST are not supported #4009

winkyao opened this issue Aug 3, 2017 · 2 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@winkyao
Copy link
Contributor

winkyao commented Aug 3, 2017

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
CREATE TABLE t1(f1 VARCHAR(6) NOT NULL, FULLTEXT KEY(f1),UNIQUE(f1));
EXPLAIN SELECT 1 FROM t1 WHERE 1 > ALL((SELECT 1 FROM t1 JOIN t1 a ON (MATCH(t1.f1) AGAINST ("")) WHERE t1.f1 GROUP BY t1.f1));
  1. What did you expect to see?
mysql> CREATE TABLE t1(f1 VARCHAR(6) NOT NULL, FULLTEXT KEY(f1),UNIQUE(f1));
Query OK, 0 rows affected (0.05 sec)

mysql> EXPLAIN SELECT 1 FROM t1 WHERE 1 > ALL((SELECT 1 FROM t1 JOIN t1 a ON (MATCH(t1.f1) AGAINST ("")) WHERE t1.f1 GROUP BY t1.f1));
+----+-------------+-------+------------+----------+---------------+------+---------+-------+------+----------+-----------------------------------+
| id | select_type | table | partitions | type     | possible_keys | key  | key_len | ref   | rows | filtered | Extra                             |
+----+-------------+-------+------------+----------+---------------+------+---------+-------+------+----------+-----------------------------------+
|  1 | PRIMARY     | t1    | NULL       | index    | NULL          | f1_2 | 8       | NULL  |    1 |   100.00 | Using index                       |
|  2 | SUBQUERY    | t1    | NULL       | fulltext | f1            | f1   | 0       | const |    1 |   100.00 | Using where; Ft_hints: no_ranking |
|  2 | SUBQUERY    | a     | NULL       | index    | NULL          | f1_2 | 8       | NULL  |    1 |   100.00 | Using index                       |
+----+-------------+-------+------------+----------+---------------+------+---------+-------+------+----------+-----------------------------------+
3 rows in set, 1 warning (0.00 sec)
  1. What did you see instead?
mysql> CREATE TABLE t1(f1 VARCHAR(6) NOT NULL, FULLTEXT KEY(f1),UNIQUE(f1));
Query OK, 0 rows affected (0.09 sec)

mysql> EXPLAIN SELECT 1 FROM t1 WHERE 1 > ALL((SELECT 1 FROM t1 JOIN t1 a ON (MATCH(t1.f1) AGAINST ("")) WHERE t1.f1 GROUP BY t1.f1));
ERROR 1105 (HY000): line 0 column 77 near "t1.f1) AGAINST ("")) WHERE t1.f1 GROUP BY t1.f1))" (total length 126)
  1. What version of TiDB are you using (tidb-server -V)?
@winkyao winkyao added easy help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Aug 3, 2017
@ngaut ngaut removed the rc3.1 label Aug 16, 2017
@zimulala zimulala removed the easy label Aug 23, 2017
@morgo
Copy link
Contributor

morgo commented Nov 24, 2018

FULLTEXT functions and indexes are currently documented as unsupported: https://www.pingcap.com/docs/sql/mysql-compatibility/

@morgo
Copy link
Contributor

morgo commented Nov 24, 2018

I am going to close this issue in favour of #1793 (they are closely related).

Please feel free to re-open this issue if you have any questions. Thanks!

@morgo morgo closed this as completed Nov 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

4 participants