| Bug #71627 | mysqldbcopy's help has a typo 'snaphot' instead of 'snapshot'. | ||
|---|---|---|---|
| Submitted: | 7 Feb 2014 15:49 | Modified: | 18 Feb 2014 4:35 |
| Reporter: | Meiji Kimura | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Utilities | Severity: | S3 (Non-critical) |
| Version: | 1.3.6 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[8 Feb 2014 6:05]
MySQL Verification Team
Hello Meiji-San, Thank you for the bug report. Verified as described. Thanks, Umesh
[8 Feb 2014 6:07]
MySQL Verification Team
// How to repeat
[root@cluster-repo mysql-utilities-1.3.6]# mysqldbcopy --help |grep -A 3 "LOCKING"
--locking=LOCKING choose the lock type for the operation: no-locks = do
not use any table locks, lock-all = use table locks
but no transaction and no consistent read, snaphot
(default): consistent read using a single transaction.
[12 Feb 2014 21:45]
Chuck Bell
Fixed in release-1.4.2
[18 Feb 2014 4:35]
Philip Olson
Fixed as of the upcoming MySQL Utilities 1.4.2 release, and here's the changelog entry: A typo was fixed in the "mysqldbcopy" utility's help text. Thank you for the bug report.
Description: There is a typo 'snaphot' for --locking Option. The right arguement for LOCKING is 'snaphost', not 'snaphot'. How to repeat: (1) Type mysqldbcopy --help (2) You can see this explanation in help text. --locking=LOCKING choose the lock type for the operation: no-locks = do not use any table locks, lock-all = use table locks but no transaction and no consistent read, snaphot (default): consistent read using a single transaction. Suggested fix: Use 'snapshot' indtead of 'snaphot'.