Author: jstephens
Date: 2009-10-30 12:01:34 +0100 (Fri, 30 Oct 2009)
New Revision: 17386
Log:
Documented fix for Cluster Bug #48416
Added info/workaround to Cluster Upgrade/Downgrade Compatibility section
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/refman-5.1/mysql-cluster-multi-computer.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-10-30 10:51:20 UTC (rev 17385)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-10-30 11:01:34 UTC (rev 17386)
Changed blocks: 1, Lines Added: 37, Lines Deleted: 0; 1346 bytes
@@ -10,9 +10,46 @@
<tags>
<highlight type="cluster"/>
+ <manual type="upgrades"/>
+ <manual type="unique indexes"/>
+ <manual type="error 293"/>
</tags>
<bugs>
+ <fixes bugid="48416"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.39-ndb-7.0.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ After upgrading a MySQL Cluster containing tables having unique
+ indexes from an NDB 6.3 release to an NDB 7.0 release, attempts
+ to create new unique indexes failed with <errortext>inconsistent
+ trigger</errortext> errors (error code
+ <errorcode>293</errorcode>).
+ </para>
+
+ <para>
+ For more information (including a workaround for previous MySQL
+ Cluster NDB 7.0 releases), see
+ <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
<fixes bugid="40679"/>
<seealsobug bugid="46955"/>
</bugs>
Modified: trunk/refman-5.1/mysql-cluster-multi-computer.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-multi-computer.xml 2009-10-30 10:51:20 UTC (rev 17385)
+++ trunk/refman-5.1/mysql-cluster-multi-computer.xml 2009-10-30 11:01:34 UTC (rev 17386)
Changed blocks: 2, Lines Added: 31, Lines Deleted: 1; 2231 bytes
@@ -2522,7 +2522,7 @@
<listitem>
<para>
- Once an <literal>NDB</literal> table had an
+ Once an <literal role="se">NDB</literal> table had an
<literal role="stmt" condition="alter-table">ALTER
ONLINE TABLE</literal> operation performed on it using a
MySQL Cluster NDB 6.3.x release, it could not be
@@ -2533,6 +2533,36 @@
<listitem>
<para>
+ Following an upgrade from MySQL Cluster NDB 6.3 to MySQL
+ Cluster NDB 7.0, if there were any tables having unique
+ indexes prior to the upgrade, attempts to create unique
+ indexes failed. This could also occur when performing
+ offline <literal role="stmt">ALTER TABLE</literal>
+ operations on tables having indexes that were not
+ dropped as a result of the <literal role="stmt">ALTER
+ TABLE</literal>. This issue was due to a change in the
+ way was resolved in MySQL Cluster NDB 7.0.9. (Bug
+ #48416)
+ </para>
+
+ <formalpara>
+
+ <title>Workaround</title>
+
+ <para>
+ For upgrades to MySQL Cluster NDB 7.0 releases prior
+ to version 7.0.9, a workaround are available:
+ Following the upgrade, perform a second rolling
+ restart of the cluster before before performing any
+ <literal role="stmt">ALTER TABLE</literal> operations
+ involving indexes.
+ </para>
+
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <para>
A table created in a previous version of MySQL Cluster
does not automatically support
<literal role="se">NDB</literal>-native default values
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r17386 - in trunk: dynamic-docs/changelog refman-5.1 | jon.stephens | 30 Oct |
