Author: jstephens
Date: 2006-12-07 06:48:10 +0100 (Thu, 07 Dec 2006)
New Revision: 4149
Log:
Documenting bugfixes:
Cluster (general) - Bug #22547
Cluster/Disk Data - Bug #23432, Bug #23576, Bug #24143, Bug #24331
Cluster/APIs - Bug #21690, Bug #24503
Cluster/Replication: Bug #14612, Bug #15021
Modified:
trunk/ndbapi/ndb-classes.xml
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/ndbapi/ndb-classes.xml
===================================================================
--- trunk/ndbapi/ndb-classes.xml 2006-12-07 00:23:43 UTC (rev 4148)
+++ trunk/ndbapi/ndb-classes.xml 2006-12-07 05:48:10 UTC (rev 4149)
Changed blocks: 2, Lines Added: 9, Lines Deleted: 3; 1009 bytes
@@ -33158,7 +33158,7 @@
<para>
This section discusses the <literal>NdbScanFliter</literal>
- class and it public members.
+ class and its public members.
</para>
</abstract>
@@ -33176,9 +33176,15 @@
<important>
<para>
- This interface is still under development and is likely to
- change in future releases.
+ Prior to MySQL 5.1.14, the comparison methods of this class did
+ not work with <literal>BIT</literal> values (see Bug #24503).
</para>
+
+ <para>
+ Development of this interface continues in MySQL 5.1, and the
+ charcateristics of the NdbScanFilter class are likely to change
+ further in future releases.
+ </para>
</important>
<formalpara>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2006-12-07 00:23:43 UTC (rev 4148)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2006-12-07 05:48:10 UTC (rev 4149)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 839 bytes
@@ -63,6 +63,15 @@
<listitem>
<para>
+ <literal>NDB Cluster</literal> (Cluster APIs): Using
+ <literal>BIT</literal> values with any of the comparison
+ methods of the <literal>NdbScanFilter</literal> class caused
+ the cluster's data nodes to fail. (Bug #24503)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: The failure of a data node
failure during a schema operation could lead to additional
node failures. (Bug #24752)
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2006-12-07 00:23:43 UTC (rev 4148)
+++ trunk/refman-5.1/mysql-cluster.xml 2006-12-07 05:48:10 UTC (rev 4149)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 689 bytes
@@ -15277,6 +15277,13 @@
BINLOG EVENTS</literal> statement on either the replication
master or slave MySQL servers.
</para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Beginning with MySQL
+ 5.1.14, if the <literal>apply_status</literal> table does not
+ exist on the slave, it is created by
+ <command>ndb_restore</command>. (Bug #14612)
+ </para>
</section>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-12-07 00:23:43 UTC (rev 4148)
+++ trunk/refman-5.1/news-5.1.xml 2006-12-07 05:48:10 UTC (rev 4149)
Changed blocks: 2, Lines Added: 75, Lines Deleted: 0; 3081 bytes
@@ -105,6 +105,16 @@
kinds of functions.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication):
+ <command>ndb_restore</command> now creates the
+ <literal>apply_status</literal> and
<literal>schema</literal>
+ tables if they do not already exist on the slave cluster. (Bug
+ #14612)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -166,6 +176,71 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): If errors
+ occurred during purging of the binary logs, extraneous rows
+ could remain left in the <literal>binlog_index</literal>
+ table. (Bug #15021)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data):
+ <command>ndb_restore</command> could sometimes fail when
+ attempting to restore Disk Data tables due to data node
+ failure caused by accessing unitialized memory. (Bug #24331)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Excessive
+ fragmentation of Disk Data files (including log files and data
+ files) could occur during the course of normal use. (Bug
+ #24143)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): It was possible to
+ execute a statement for creating a Disk Data table that
+ referred to a nonexistent tablespace, in which case the table
+ was an in-memory <literal>NDB</literal> table. Such a
+ statement instead now fails with an appropriate error message.
+ (Bug #23576)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Under some
+ circumstances, a <literal>DELETE</literal> from a Disk Data
+ table could cause <command>mysqld</command> to crash. (Bug
+ #23542)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Cluster APIs): Using
+ <literal>BIT</literal> values with any of the comparison
+ methods of the <literal>NdbScanFilter</literal> class caused
+ the cluster's data nodes to fail. (Bug #24503)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A value equal to or greater
+ than the allowed maximum for
+ <literal>LongMessageBuffer</literal> caused all data nodes to
+ crash. (Bug #22547)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4149 - in trunk: ndbapi refman-5.0 refman-5.1 | jon | 7 Dec |