Bug #40848 information_schema.tables.index_length should not return 0 for NDB tables

• Submitted: 19 Nov 2008 10:22
• Modified: 20 Nov 2008 14:03
• Reporter: Kai Voigt
• Status: Won't fix
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: pro:mysql-5.1.24-ndb-6.3.14-telco
• OS: MacOS
• CPU Architecture: Any

[19 Nov 2008 10:22] Kai Voigt

Description:
information_schema.tables.index_length contains 0 for NDB tables, this would mean 0 bytes of index being stored. But this is not true. Better to return NULL indicating that the value cannot be supplied

How to repeat:
Setup cluster, create cluster table(s) and run

SELECT SUM(INDEX_LENGTH) FROM INFORMATION_SCHEMA.TABLES WHERE ENGINE='ndbcluster'

Will return 0

Suggested fix:
Make information_schema.tables.index_length returning NULL for NDB tables

[19 Nov 2008 11:12] Sveta Smirnova

Thank you for the report.

Verified as described, although current behavior is consistent with other storage engines:

SELECT SUM(INDEX_LENGTH), ENGINE FROM INFORMATION_SCHEMA.TABLES group by ENGINE;
SUM(INDEX_LENGTH)       ENGINE
0       CSV
0       MEMORY
60416   MyISAM
0       ndbcluster

[19 Nov 2008 13:36] Hartmut Holzgraefe

Same for "show table status;" ...

[20 Nov 2008 13:26] Jonas Oreland

given that the others also report 0, I suggest "won't fix"