Bug #12414 | index merge optimization doesn't work with FULLTEXT indexes | ||
---|---|---|---|
Submitted: | 6 Aug 2005 14:21 | Modified: | 14 Sep 2005 19:55 |
Reporter: | Gleb Paharenko | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S4 (Feature request) |
Version: | 5.0.10 | OS: | Linux (Linux) |
Assigned to: | CPU Architecture: | Any |
[6 Aug 2005 14:21]
Gleb Paharenko
[7 Aug 2005 9:29]
Aleksey Kishkin
Hi! it's in TODO: http://dev.mysql.com/doc/mysql/en/fulltext-todo.html
[7 Aug 2005 9:39]
Gleb Paharenko
Hi! There is a quoting from: http://dev.mysql.com/doc/mysql/en/fulltext-todo.html I'm sorry (it is a bit not clear for me) - but, could you tell me, where is exactly said about index merge optimization? I think it is not a phrase about MERGE tables (because index merge optimization and MERGE tables are different things), maybe it is "Impoved performance of FULLTEXT searches'? " Improved performance for all FULLTEXT operations. Proximity operators. Support for “always-index words.” These could be any strings the user wants to treat as words, such as “C++”, “AS/400”, or “TCP/IP”. Support for full-text search in MERGE tables. Support for the ucs2 character set. Make the stopword list dependent on the language of the dataset. Stemming Generic user-suppliable UDF preparser. Make the model more flexible (by adding some adjustable parameters to FULLTEXT in CREATE TABLE and ALTER TABLE statements)."
[7 Aug 2005 9:40]
Gleb Paharenko
I've ment: http://dev.mysql.com/doc/mysql/en/index-merge-optimization.html
[7 Aug 2005 9:41]
Gleb Paharenko
Not: http://dev.mysql.com/doc/mysql/en/merge-storage-engine.html
[7 Aug 2005 11:39]
Aleksey Kishkin
I see. Sorry for misunderstanding. Let me check.
[18 Aug 2007 1:15]
Igor Babaev
- This is a request for an optimization that does not look to be widely used. By the above reason I move the bug to 'To be fixed later'. Product management will decide in what version a fix for this problem appears.