[MDEV-11124] MariaRocks: rocksdb.rocksdb fails with a duplicate key error Created: 2016-10-24  Updated: 2016-10-25  Resolved: 2016-10-25

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Sergei Petrunia Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-9658 Make MyRocks in MariaDB stable Closed

 Description    

rocksdb.rocksdb                          [ fail ]
 
        Test ended at 2016-10-24 12:02:33
 
 
 
CURRENT_TEST: rocksdb.rocksdb
 
mysqltest: At line 1196: query 'INSERT INTO t1 (i,t,s,m,b) VALUES (1,2,3,4,5),(1000,100,10000,1000000,1000000000000000000),(5,100,10000,1000000,100000000000000000),(2,3,4,5,6),(3,4,5,6,7),(101,102,103,104,105),
 
(10001,103,10002,10003,10004),(10,11,12,13,14),(11,12,13,14,15),(12,13,14,15,16)' 
failed: 1062: Duplicate entry '6-3' for key 'b_t'



 Comments   
Comment by Sergei Petrunia [ 2016-10-24 ]

.. and the reason of this is that in MariaDB, the function

void Field::make_sort_key(uchar *buff,uint length)

stores the NULL-indicator byte for the field. In MySQL, it does not. We store NULL-indicator bytes twice and screw up the comparison.

Comment by Sergei Petrunia [ 2016-10-24 ]

Commit in MariaDB that introduced the change:
0791692bdc311f39181b9df236981a2cb439638e
MDEV-3875 Wrong result (missing row) on a DISTINCT query with the same subquery in the SELECT list and GROUP BY

Comment by Sergei Petrunia [ 2016-10-25 ]

Fix pushed into MariaRocks tree.

Generated at Thu Feb 08 07:47:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.