Author: js221926
Date: 2011-02-22 12:29:25 +0100 (Tue, 22 Feb 2011)
New Revision: 25135
Log:
Documentation for Cluster WL#5421 (ndb_restore --lossy-conversions option)
Modified:
trunk/dynamic-docs/changelog/mysqld-2.xml
trunk/dynamic-docs/command-optvars/ndb_restore.xml
trunk/refman-5.1/mysql-cluster-overview.xml
trunk/refman-5.1/mysql-cluster-programs-core.xml
Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml 2011-02-21 21:16:27 UTC (rev 25134)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml 2011-02-22 11:29:25 UTC (rev 25135)
Changed blocks: 1, Lines Added: 37, Lines Deleted: 0; 1282 bytes
@@ -6,6 +6,43 @@
]>
<changelog>
+ <logentry entrytype="feature">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="backup"/>
+ <manual type="ndb_restore"/>
+ <manual type="attribute promotion"/>
+ </tags>
+
+ <bugs>
+ <fixes wlid="5421"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.51-ndb-7.1.11"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Added the
+ <option role="ndb_restore">--lossy-conversions</option> option
+ for <command>ndb_restore</command>, which makes it possible to
+ enable attribute demotion when restoring a MySQL Cluster from an
+ <literal role="se">NDB</literal> native backup.
+ </para>
+
+ <para>
+ For additional information about type conversions currently
+ supported by MySQL Cluster for attribute promotion and demotion,
+ see <xref linkend="replication-features-different-data-types"/>.
+ </para>
+
+ </message>
+
+ </logentry>
+
<logentry entrytype="bug">
<tags>
Modified: trunk/dynamic-docs/command-optvars/ndb_restore.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/ndb_restore.xml 2011-02-21 21:16:27 UTC (rev 25134)
+++ trunk/dynamic-docs/command-optvars/ndb_restore.xml 2011-02-22 11:29:25 UTC (rev 25135)
Changed blocks: 1, Lines Added: 27, Lines Deleted: 0; 1039 bytes
@@ -973,4 +973,31 @@
</mysqloption>
+ <mysqloption id="lossy-conversion">
+
+ <xrefto id="option_ndb_restore_lossy-conversion"/>
+
+ <name>lossy-conversion</name>
+
+ <shortdescription>
+ Allow lossy conversions of column values (type demotions or
+ changes in sign) when restoring data from backup
+ </shortdescription>
+
+ <types>
+ <optype class="cmdline" format="--lossy-conversion"/>
+ <optype class="cmdline" format="-L"/>
+ </types>
+
+ <values vartype="boolean" platform="all">
+ <value default="FALSE">If option is not used</value>
+ </values>
+
+ <versions>
+ <manual version="5.1"/>
+ <introduced version="5.1.51-ndb-7.1.11"/>
+ </versions>
+
+ </mysqloption>
+
</mysqloptions>
Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml 2011-02-21 21:16:27 UTC (rev 25134)
+++ trunk/refman-5.1/mysql-cluster-overview.xml 2011-02-22 11:29:25 UTC (rev 25135)
Changed blocks: 1, Lines Added: 27, Lines Deleted: 0; 1404 bytes
@@ -2026,6 +2026,33 @@
</para>
</listitem>
+ <listitem>
+ <formalpara>
+
+ <title><command>ndb_restore</command> attribute demotion</title>
+
+ <para>
+ Beginning with MySQL Cluster NDB 7.1.11, it is possible to
+ enable attribute demotion when restoring a MySQL Cluster
+ from a native backup running
+ <command>ndb_restore</command> with a new
+ <option role="ndb_restore">--lossy-conversions</option>
+ option.
+ </para>
+
+ </formalpara>
+
+ <para>
+ In general,the rules governing demotion are the same as for
+ MySQL replication, although there are some exceptions that
+ you may need to take into account being employing this
+ option. See
+ <xref linkend="replication-features-different-data-types"/>,
+ for information about type conversions currently supported
+ by attribute promotion and demotion in MySQL Cluster.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
Modified: trunk/refman-5.1/mysql-cluster-programs-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-programs-core.xml 2011-02-21 21:16:27 UTC (rev 25134)
+++ trunk/refman-5.1/mysql-cluster-programs-core.xml 2011-02-22 11:29:25 UTC (rev 25135)
Changed blocks: 2, Lines Added: 42, Lines Deleted: 12; 3271 bytes
@@ -5058,17 +5058,52 @@
</orderedlist>
+ <para id="option_ndb_restore_lossy-conversion">
+ <indexterm>
+ <primary>ndb_restore</primary>
+ <secondary>--lossy-conversion option</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>--lossy-conversion option (ndb_restore)</primary>
+ </indexterm>
+
+ <option>--lossy-conversion</option>, <option>-L</option>
+ </para>
+
+ <para condition="dynamic:optvar:item" role="5.1:ndb_restore:lossy-conversion"/>
+
+ <para>
+ This option is intended to complement the
+ <option role="ndb_restore">--promote-attributes</option>
+ option. Using <option>--lossy-conversion</option> allows lossy
+ conversions of column values (type demotions or changes in
+ sign) when restoring data from backup. With some exceptions,
+ the rules governing demotion are the same as for MySQL
+ replication; see
+ <xref linkend="replication-features-different-data-types"/>,
+ for information about specific type conversions currently
+ supported by attribute demotion.
+ </para>
+
+ <para>
+ <command>ndb_restore</command> reports any truncation of data
+ that it performs during lossy conversions once per attribute
+ and column.
+ </para>
+
+ <para>
+ This option was added in MySQL Cluster NDB 7.1.11.
+ </para>
+
<para id="option_ndb_restore_preserve-trailing-spaces">
<indexterm>
<primary>--preserve-trailing-spaces option (ndb_restore)</primary>
</indexterm>
- In addition to
- <option role="ndb_restore">--promote-attributes</option>, a
- <option>--preserve-trailing-spaces</option> option is also
- available for use with <command>ndb_restore</command>
- beginning with MySQL Cluster NDB 6.3.8. This option (short
- form <option>-R</option>) causes trailing spaces to be
+ The <option>--preserve-trailing-spaces</option> option is also
+ available beginning with MySQL Cluster NDB 6.3.8. This option
+ (short form <option>-R</option>) causes trailing spaces to be
preserved when promoting a <literal role="type">CHAR</literal>
column to <literal role="type">VARCHAR</literal> or a
<literal>BINARY</literal> column to
@@ -6070,13 +6105,8 @@
manually. To cause the binary logs to be created, issue a
<literal role="stmt">SHOW TABLES</literal> statement on that
SQL node before running <literal role="stmt">START
- SLAVE</literal>.
+ SLAVE</literal>. This is a known issue in MySQL Cluster.
</para>
-
- <para>
- This is a known issue with MySQL Cluster management, which
- we intend to address in a future release.
- </para>
</important>
</refsection>
| Thread |
|---|
| • svn commit - mysqldoc@oter02: r25135 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.1 | jon.stephens | 22 Feb |
