MySQL Bugs: #30807: Falcon: error message for ANALYZE is too vague

Bug #30807	Falcon: error message for ANALYZE is too vague
Submitted:	4 Sep 2007 19:43	Modified:	5 Dec 2007 20:29
Reporter:	Peter Gulutzan	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Falcon storage engine	Severity:	S3 (Non-critical)
Version:	6.0.3-alpha-debug	OS:	Linux (SUSE 10 64-bit)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I create a partitioned Falcon table.
I say "ALTER TABLE table_name ANALYZE partition_name".
I get the message "Got error -1 from storage engine".

The message "Got error -1" fails to tell me
what I did wrong.

How to repeat:
mysql> create table t6 (s1 int) engine=falcon partition by list(s1) (partition p1 values in (null,2), partition p2 values in (1));
Query OK, 0 rows affected (0.72 sec)

mysql> insert into t6 values (null),(1),(2);
Query OK, 3 rows affected (0.02 sec)
Records: 3  Duplicates: 0  Warnings: 0

mysql> alter table t6 analyze partition p1;
ERROR 1030 (HY000): Got error -1 from storage engine

Thank you for the bug report. Verified as described.

[miguel@skybr 6.0]$ bin/mysql -uroot test
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 6.0.3-alpha-debug Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create table t6 (s1 int) engine=falcon partition by list(s1) (partition p1 values
    -> in (null,2), partition p2 values in (1));
Query OK, 0 rows affected (0.39 sec)

mysql> insert into t6 values (null),(1),(2);
Query OK, 3 rows affected (0.00 sec)
Records: 3  Duplicates: 0  Warnings: 0

mysql> alter table t6 analyze partition p1;
ERROR 1030 (HY000): Got error -1 from storage engine
mysql>

this appears to be a duplicate (subset) of 27492 which appears in turn
to be a bad interaction between a falcon note saying that the operation
is not supported by the engine, and the partitioning engine.

This is not a duplicate of bug#27492.

Sorry, I meant to type 27429.  The description of that bug starts:

For unsupported operations OPTIMIZE/CHECK/REPAIR/ANALYZE
TABLE, Falcon reports -- as a note, not an error --
"The storage engine for the table doesn't support [statement]".

But if the table is partitioned, and the operation
is OPTIMIZE PARTITION, Falcon reports an error:
ERROR 1296 (HY000): Got error -1 'can't open file ...

Chris, another vague error message.

Duplicate of Bug#27429, "Falcon: inconsistent errors for optimize". Also, this is not a storage engine bug.

The handler class returns HA_ADMIN_NOT_IMPLEMENTED for unsupported ANALYZE/OPTIMIZE/REPAIR/CHECK operations performed on any table, partitioned or not. The discrepancy in error handling is due to differences in how mysql_admin_table() and mysql_alter_table() process the error.