| Bug #31208 | cache indexing of partitioned table fails | ||
|---|---|---|---|
| Submitted: | 26 Sep 2007 14:45 | Modified: | 12 Oct 2007 16:10 |
| Reporter: | Cyril SCETBON | Email Updates: | |
| Status: | Closed | ||
| Category: | Server: Docs | Severity: | S2 (Serious) |
| Version: | 5.1.20-beta, 5.1, 5.2 BK | OS: | Linux |
| Assigned to: | Jon Stephens | Target Version: | |
| Triage: | D4 (Minor) | ||
[27 Sep 2007 9:07]
Sveta Smirnova
Thank you for the report. Verified as described.
[12 Oct 2007 16:10]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Documented revised to make it clear that key caching is not supported at all for partitioned tables.
Description: when using cache index statement with a partitionned table it fails. Documentation says that load index is not supported for partitionned tables but nothing about cache index statement How to repeat: mysql> SET GLOBAL keycache2.key_buffer_size=64*1024*1024; Query OK, 0 rows affected (0.07 sec) mysql> create table toto (id int) partition by hash(id) partitions 5; Query OK, 0 rows affected (0.01 sec) mysql> cache index toto in keycache2; +-----------+--------------------+----------+---------------------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +-----------+--------------------+----------+---------------------------------------------------------------------+ | test.toto | assign_to_keycache | note | The storage engine for the table doesn't support assign_to_keycache | +-----------+--------------------+----------+---------------------------------------------------------------------+ 1 row in set (0.00 sec)