List:Commits« Previous MessageNext Message »
From:jon.stephens Date:February 10 2011 9:20pm
Subject:svn commit - mysqldoc@docsrva: r25073 - in trunk: dynamic-docs/changelog refman-5.1
View as plain text  
Author: jstephens
Date: 2011-02-10 22:20:39 +0100 (Thu, 10 Feb 2011)
New Revision: 25073

Log:


Documentation for WL#5568 (NDB stats for I_S tables)




Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/refman-5.1/information-schema.xml
   trunk/refman-5.1/mysql-cluster-overview.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2011-02-10 19:48:58 UTC (rev 25072)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2011-02-10 21:20:39 UTC (rev 25073)
Changed blocks: 1, Lines Added: 39, Lines Deleted: 0; 1434 bytes

@@ -6,6 +6,45 @@
 ]>
 <changelog>
 
+  <logentry entrytype="feature">
+
+    <tags>
+      <highlight type="cluster"/>
+      <highlight type="diskdata"/>
+      <manual type="information_schema"/>
+      <manual type="resource usage"/>
+    </tags>
+
+    <bugs>
+      <fixes wlid="5568"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.51-ndb-7.0.22"/>
+      <version ver="5.1.51-ndb-7.1.11"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <literal role="is">INFORMATION_SCHEMA.TABLES</literal> table
+        now provides disk usage as well as memory usage information for
+        Disk Data tables. Also,
+        <literal role="is">INFORMATION_SCHEMA.PARTITIONS</literal>,
+        formerly did not show any statistics for
+        <literal role="se">NDB</literal> tables. Now the
+        <literal>TABLE_ROWS</literal>,
+        <literal>AVG_ROW_LENGTH</literal>,
+        <literal>DATA_LENGTH</literal>,
+        <literal>MAX_DATA_LENGTH</literal>, and
+        <literal>DATA_FREE</literal> columns contain correct information
+        for the table&apos;s partitions.
+      </para>
+
+    </message>
+
+  </logentry>
+
   <logentry entrytype="bug">
 
     <tags>


Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml	2011-02-10 19:48:58 UTC (rev 25072)
+++ trunk/refman-5.1/information-schema.xml	2011-02-10 21:20:39 UTC (rev 25073)
Changed blocks: 6, Lines Added: 60, Lines Deleted: 20; 5094 bytes

@@ -681,6 +681,12 @@
           reflects the true amount of storage for variable-width columns
           of <literal role="se">NDB</literal> tables. (Bug#18413)
         </para>
+
+        <para>
+          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
+          7.1.11, <literal>DATA_LENGTH</literal> includes data on disk
+          as well as in main memory.
+        </para>
       </listitem>
 
       <listitem>

@@ -689,6 +695,13 @@
           column shows the free space in bytes for
           <literal>InnoDB</literal> tables.
         </para>
+
+        <para>
+          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
+          7.1.11, <literal>DATA_FREE</literal> includes
+          <literal role="se">NDB</literal> table data on disk as well as
+          in main memory.
+        </para>
       </listitem>
 
       <listitem>

@@ -4179,12 +4192,19 @@
         </para>
 
         <para>
-          For partitions of <literal role="se">NDB</literal> tables,
-          whether the tables use implicit or explicit partitioning, the
-          <literal>TABLE_ROWS</literal> column value is always 0.
-          However, you can obtain this information using the
-          <command>ndb_desc</command> utility.
+          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
+          7.1.11, <literal>TABLE_ROWS</literal> shows correct
+          information for <literal role="se">NDB</literal> tables.
+          Previously, for partitions of <literal role="se">NDB</literal>
+          tables, the <literal>TABLE_ROWS</literal> column value was
+          always 0.
         </para>
+
+        <para>
+          For <literal role="se">NDB</literal> tables, you can also
+          obtain this information using the <command>ndb_desc</command>
+          utility.
+        </para>
       </listitem>
 
       <listitem>

@@ -4216,12 +4236,19 @@
         </para>
 
         <para>
-          For partitions of <literal role="se">NDB</literal> tables,
-          whether the tables use implicit or explicit partitioning, the
-          <literal>DATA_LENGTH</literal> column value is always 0.
-          However, you can obtain equivalent information using the
-          <command>ndb_desc</command> utility.
+          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
+          7.1.11, <literal>DATA_LENGTH</literal> shows correct
+          information for <literal role="se">NDB</literal> tables.
+          Previously, for partitions of <literal role="se">NDB</literal>
+          tables, the <literal>DATA_LENGTH</literal> column value was
+          always 0.
         </para>
+
+        <para>
+          For <literal role="se">NDB</literal> tables, you can also
+          obtain this information using the <command>ndb_desc</command>
+          utility.
+        </para>
       </listitem>
 
       <listitem>

@@ -4231,12 +4258,19 @@
         </para>
 
         <para>
-          For partitions of <literal role="se">NDB</literal> tables,
-          whether the tables use implicit or explicit partitioning, the
-          <literal>MAX_DATA_LENGTH</literal> column value is always
-          <literal>NULL</literal>. However, you can obtain equivalent
-          information using the <command>ndb_desc</command> utility.
+          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
+          7.1.11, <literal>MAX_DATA_LENGTH</literal> shows correct
+          information for <literal role="se">NDB</literal> tables.
+          Previously, for partitions of <literal role="se">NDB</literal>
+          tables, the <literal>MAX_DATA_LENGTH</literal> column value
+          was always <literal>NULL</literal>.
         </para>
+
+        <para>
+          For <literal role="se">NDB</literal> tables, you can also
+          obtain this information using the <command>ndb_desc</command>
+          utility.
+        </para>
       </listitem>
 
       <listitem>

@@ -4261,12 +4295,18 @@
         </para>
 
         <para>
-          For partitions of <literal role="se">NDB</literal> tables,
-          whether the tables use implicit or explicit partitioning, the
-          <literal>DATA_FREE</literal> column value is always 0.
-          However, you can obtain equivalent information using the
-          <command>ndb_desc</command> utility.
+          Beginning with MySQL Cluster NDB 7.0.22 and MySQL Cluster NDB
+          7.1.11, <literal>DATA_FREE</literal> shows correct information
+          for <literal role="se">NDB</literal> tables. Previously, for
+          partitions of <literal role="se">NDB</literal> tables, the
+          <literal>DATA_FREE</literal> column value was always 0.
         </para>
+
+        <para>
+          For <literal role="se">NDB</literal> tables, you can also
+          obtain this information using the <command>ndb_desc</command>
+          utility.
+        </para>
       </listitem>
 
       <listitem>


Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml	2011-02-10 19:48:58 UTC (rev 25072)
+++ trunk/refman-5.1/mysql-cluster-overview.xml	2011-02-10 21:20:39 UTC (rev 25073)
Changed blocks: 2, Lines Added: 63, Lines Deleted: 0; 3031 bytes

@@ -1994,6 +1994,38 @@
           </para>
         </listitem>
 
+        <listitem>
+          <formalpara>
+
+            <title><literal>INFORMATION_SCHEMA</literal> inprovements</title>
+
+            <para>
+              Beginning with MySQL Cluster NDB 7.1.11, Beginning with
+              MySQL Cluster NDB 7.0.22,
+              <literal>INFORMATION_SCHEMA</literal> provides disk usage
+              information for MySQL Cluster Disk Data tables.
+              Previously,
+              <literal role="is">INFORMATION_SCHEMA.TABLES</literal>
+              showed only the space usage for the in-memory data part of
+              the table. Now, it also shows the space allocated for and
+              used by the disk_part data of that table as well.
+            </para>
+
+          </formalpara>
+
+          <para>
+            In addition, the
+            <literal role="is">INFORMATION_SCHEMA.PARTITIONS</literal>
+            table (which did not show any statistics for
+            <literal role="se">NDB</literal> tables) now shows correct
+            values in this table&apos;s <literal>TABLE_ROWS</literal>,
+            <literal>AVG_ROW_LENGTH</literal>,
+            <literal>DATA_LENGTH</literal>,
+            <literal>MAX_DATA_LENGTH</literal>, and
+            <literal>DATA_FREE</literal> columns, for each partition.
+          </para>
+        </listitem>
+
       </itemizedlist>
 
       <para>

@@ -2982,6 +3014,37 @@
           </para>
         </listitem>
 
+        <listitem>
+          <formalpara>
+
+            <title><literal>INFORMATION_SCHEMA</literal> inprovements</title>
+
+            <para>
+              Beginning with MySQL Cluster NDB 7.0.22,
+              <literal>INFORMATION_SCHEMA</literal> provides disk usage
+              information for MySQL Cluster Disk Data tables.
+              Previously,
+              <literal role="is">INFORMATION_SCHEMA.TABLES</literal>
+              showed only the space usage for the in-memory data part of
+              the table. Now, it also shows the space allocated for and
+              used by the disk_part data of that table as well.
+            </para>
+
+          </formalpara>
+
+          <para>
+            In addition, the
+            <literal role="is">INFORMATION_SCHEMA.PARTITIONS</literal>
+            table (which did not show any statistics for
+            <literal role="se">NDB</literal> tables) now shows correct
+            values in this table&apos;s <literal>TABLE_ROWS</literal>,
+            <literal>AVG_ROW_LENGTH</literal>,
+            <literal>DATA_LENGTH</literal>,
+            <literal>MAX_DATA_LENGTH</literal>, and
+            <literal>DATA_FREE</literal> columns, for each partition.
+          </para>
+        </listitem>
+
       </itemizedlist>
 
       <para>


Thread
svn commit - mysqldoc@docsrva: r25073 - in trunk: dynamic-docs/changelog refman-5.1jon.stephens10 Feb