Author: jstephens
Date: 2010-11-10 16:01:45 +0100 (Wed, 10 Nov 2010)
New Revision: 23647
Log:
Changelog entries for Cluster bugfixes:
BUG#54199, BUG#57735, BUG#58110
Modified:
trunk/dynamic-docs/changelog/mysqld-2.xml
trunk/ndbapi/overview.xml
Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml 2010-11-10 14:40:38 UTC (rev 23646)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml 2010-11-10 15:01:45 UTC (rev 23647)
Changed blocks: 1, Lines Added: 97, Lines Deleted: 0; 2810 bytes
@@ -9,7 +9,104 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="clusterapi"/>
+ <manual type="NdbOperation::getValue()"/>
+ <manual type="NdbTransaction::execute()"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="58110"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.51-ndb-6.3.40"/>
+ <version ver="5.1.51-ndb-7.0.21"/>
+ <version ver="5.1.51-ndb-7.1.10"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Attempting to read the same value (using
+ <literal role="ndbapi:NdbOperation">getValue()</literal>) more
+ than 9000 times within the same transaction caused the
+ transaction to hang when executed. Now when more reads are
+ performed in this way than can be accommodated in a single
+ transaction, the call to
+ <literal role="ndbapi:NdbTransaction">execute()</literal> fails
+ with a suitable error.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="cluster"/>
+ <manual type="BETWEEN"/>
+ <manual type="condition pushdown"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="57735"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.51-ndb-6.3.40"/>
+ <version ver="5.1.51-ndb-7.0.21"/>
+ <version ver="5.1.51-ndb-7.1.10"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A query using <literal>BETWEEN</literal> as part of a
+ pushed-down <literal>WHERE</literal> condition could cause
+ mysqld to hang or crash.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="diskdata"/>
+ <manual type="INFORMATION_SCHEMA"/>
+ <manual type="data nodes"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="54199"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.51-ndb-7.0.21"/>
+ <version ver="5.1.51-ndb-7.1.10"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When one or more data nodes was not running, queries on the
+ <literal role="is">INFORMATION_SCHEMA.FILES</literal> table took
+ an excessive length of time to complete because the MySQL server
+ waited for responses from the stopped node or nodes to time out.
+ Now in such cases, MySQL does not attempt to contact nodes which
+ are not known to be running.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
<manual type="Windows"/>
<manual type="angel process"/>
<manual type="space character"/>
Modified: trunk/ndbapi/overview.xml
===================================================================
--- trunk/ndbapi/overview.xml 2010-11-10 14:40:38 UTC (rev 23646)
+++ trunk/ndbapi/overview.xml 2010-11-10 15:01:45 UTC (rev 23647)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 7; 1397 bytes
@@ -84,15 +84,15 @@
<para>
The NDB API provides a number of classes implementing the
functionality described above. The most important of these
- include the <literal>Ndb</literal>,
- <literal>Ndb_cluster_connection</literal>,
- <literal>NdbTransaction</literal>, and
- <literal>NdbOperation</literal> classes. These model
- (respectively) database connections, cluster connections,
+ include the <literal role="ndbapi">Ndb</literal>,
+ <literal role="ndbapi">Ndb_cluster_connection</literal>,
+ <literal role="ndbapi">NdbTransaction</literal>, and
+ <literal role="ndbapi">NdbOperation</literal> classes. These
+ model (respectively) database connections, cluster connections,
transactions, and operations. These classes and their subclasses
are listed in <xref linkend="ndb-classes"/>. Error conditions in
- the NDB API are handled using <literal>NdbError</literal>, a
- structure which is described in <xref linkend="ndb-ndberror"/>.
+ the NDB API are handled using
+ <literal role="ndbapi">NdbError</literal>.
</para>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r23647 - in trunk: dynamic-docs/changelog ndbapi | jon.stephens | 10 Nov |
