Author: jstephens
Date: 2006-06-03 04:01:32 +0200 (Sat, 03 Jun 2006)
New Revision: 2264
Log:
- Partitioning by KEY is the only user-defined partitioning type supported for
MySQL Cluster
- Added some indexterms relevant to previous
- Removed reference to Bug #13520 from intro to Partitioning chapter (bug was
fixed yonks ago)
Modified:
trunk/refman-5.1/ndbcluster.xml
trunk/refman-5.1/partitioning.xml
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-06-02 20:56:40 UTC (rev 2263)
+++ trunk/refman-5.1/ndbcluster.xml 2006-06-03 02:01:32 UTC (rev 2264)
@@ -14015,17 +14015,29 @@
</listitem>
<listitem>
+ <indexterm>
+ <primary>MySQL Cluster</primary>
+ <secondary>partitioning support</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>partitioning</primary>
+ <secondary>support in MySQL Cluster</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>MySQL Cluster limitations</primary>
+ <secondary>partitioning</secondary>
+ </indexterm>
+
<para>
- It is not possible to drop partitions from
- <literal>NDB</literal> tables using <literal>ALTER TABLE
- ... DROP PARTITION</literal>. The other partitioning
- extensions to <literal>ALTER TABLE</literal> —
- <literal>ADD PARTITION</literal>, <literal>REORGANIZE
- PARTITION</literal>, and <literal>COALESCE
- PARTITION</literal> — are supported for Cluster
- tables, but use copying and so are not optimised. See
- <xref linkend="partitioning-management-range-list"/> and
- <xref linkend="alter-table"/>.
+ Support for user-defined partitioning for MySQL Cluster in
+ MySQL ¤t-series; is restricted to
+ <literal>KEY</literal> partitioning. (For testing and
+ evaluation purposes, you are not prevented from using
+ other partitioning types, but only <literal>KEY</literal>
+ partitioning is supported by MySQL AB for
+ <literal>NDBCluster</literal> tables.)
</para>
<para>
@@ -14038,6 +14050,19 @@
additional discussion of these and related issues, see
<xref linkend="partitioning-key"/>.
</para>
+
+ <para>
+ It is not possible to drop partitions from
+ <literal>NDB</literal> tables using <literal>ALTER TABLE
+ ... DROP PARTITION</literal>. The other partitioning
+ extensions to <literal>ALTER TABLE</literal> —
+ <literal>ADD PARTITION</literal>, <literal>REORGANIZE
+ PARTITION</literal>, and <literal>COALESCE
+ PARTITION</literal> — are supported for Cluster
+ tables, but use copying and so are not optimised. See
+ <xref linkend="partitioning-management-range-list"/> and
+ <xref linkend="alter-table"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-06-02 20:56:40 UTC (rev 2263)
+++ trunk/refman-5.1/partitioning.xml 2006-06-03 02:01:32 UTC (rev 2264)
@@ -57,15 +57,14 @@
<para>
The partitioning implementation in MySQL 5.1 is still undergoing
- development and is not yet production-ready. Much the same is true
- of this chapter: Some of the features described herein are not yet
- actually implemented, and others might not yet function exactly as
- described (for example, the <literal>DATA DIRECTORY</literal> and
- <literal>INDEX DIRECTORY</literal> options for partitions are
- adversely affected by Bug #13520). We have attempted to note these
- discrepancies in this chapter. Before filing bug reports, we
- encourage you to check the following resources:
+ development. For known issues with MySQL partitioning, see
+ <xref linkend="partitioning-limitations"/>, where we have noted these.
</para>
+
+ <para>
+ You may also find the following resources to be useful when working
+ with partitioned tables.
+ </para>
<para>
<emphasis role="bold">Additional Resources</emphasis>:
@@ -271,7 +270,10 @@
<literal>ARCHIVE</literal>, or <literal>CSV</literal> storage
engines. Prior to MySQL 5.1.6, it was also not feasible to create
a partitioned table using the <literal>BLACKHOLE</literal> storage
- engine. (Bug #14524).
+ engine. (Bug #14524). Partitioning by <literal>KEY</literal>
+ is supported for use with the <literal>NDBCluster</literal>
+ storage engine, but other types of user-defined partitioning are
+ not yet supported for Cluster tables in MySQL ¤t-series;.
</para>
<para>
@@ -3897,6 +3899,10 @@
This section discusses current restrictions and limitations on
MySQL partitioning support, as listed here:
</para>
+
+ <indexterm>
+ <primary>partitioning limitations</primary>
+ </indexterm>
<itemizedlist>
@@ -3941,6 +3947,12 @@
</listitem>
<listitem>
+
+ <indexterm>
+ <primary>partitioning</primary>
+ <secondary>storage engines (limitations)</secondary>
+ </indexterm>
+
<para>
A table that uses the <literal>MERGE</literal>,
<literal>ARCHIVE</literal>, or <literal>CSV</literal> storage
@@ -3952,6 +3964,12 @@
<literal>BLACKHOLE</literal> storage engine also could not be
partitioned.
</para>
+
+ <para>
+ Partitioning by <literal>KEY</literal> is the only type of
+ partitioning supported for the <literal>NDBCluster</literal>
+ storage engine.
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2264 - trunk/refman-5.1 | jon | 3 Jun |
