[MDEV-13148] LOCK TABLE on RocksDB table fails with a bogus error message Created: 2017-06-21  Updated: 2017-08-23  Resolved: 2017-08-23

Status: Closed
Project: MariaDB Server
Component/s: Locking, Storage Engine - RocksDB
Affects Version/s: 10.2
Fix Version/s: 10.2.9

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Duplicate Votes: 0
Labels: None


 Description    

MariaDB [test]> select @@log_bin, @@binlog_format;
 
+-----------+-----------------+
 
| @@log_bin | @@binlog_format |
 
+-----------+-----------------+
 
|         1 | ROW             |
 
+-----------+-----------------+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> CREATE TABLE t1 (i INT) ENGINE=RocksDB;
 
Query OK, 0 rows affected (0.08 sec)
 
 
 
MariaDB [test]> LOCK TABLE t1 WRITE;
 
ERROR 1105 (HY000): Can't execute updates on master with binlog_format != ROW.

MTR test case

 
--source include/have_log_bin.inc
 
--source include/have_binlog_format_mixed.inc
 
 
 
INSTALL SONAME 'ha_rocksdb';
 
CREATE TABLE t1 (i INT) ENGINE=RocksDB;
 
LOCK TABLE t1 WRITE;
 
 
 
DROP TABLE t1;



 Comments   
Comment by Sergei Petrunia [ 2017-08-21 ]

After slightly adjusting the testcase, I get the same error on upstream:

mysqltest: At line 7: query 'LOCK TABLE t1 WRITE' failed: 1932: Can't execute updates on master with binlog_format != ROW.

Comment by Sergei Petrunia [ 2017-08-23 ]

Fixed by fix for MDEV-13602

Generated at Thu Feb 08 08:03:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.