Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
N/A
Description
rocksdb.rocksdb_range test fails. there are also other similar test failures.
CURRENT_TEST: rocksdb.rocksdb_range
|
--- /home/psergey/dev-git/10.2-mariarocks/storage/rocksdb/mysql-test/rocksdb/r/rocksdb_range.result 2016-10-26 21:41:21.688861122 +0000
|
+++ /home/psergey/dev-git/10.2-mariarocks/storage/rocksdb/mysql-test/rocksdb/r/rocksdb_range.reject 2016-10-30 21:08:55.290270527 +0000
|
@@ -89,7 +89,7 @@
|
explain
|
select * from t2 force index (a) where a=0 and pk>=3;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t2 range a a 8 NULL # Using index condition
|
+1 SIMPLE t2 range a a 8 NULL # Using index condition; Using where
|
select * from t2 force index (a) where a=0 and pk>=3;
|
pk a b
|
3 0 3
|
@@ -201,7 +201,7 @@
|
explain
|
select * from t2 where a between 99 and 2000 order by a desc;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t2 range a a 4 NULL # Using index condition
|
+1 SIMPLE t2 range a a 4 NULL # Using where
|
select * from t2 where a between 99 and 2000 order by a desc;
|
pk a b
|
999 99 999
|
 |
mysqltest: Result length mismatch
|
The reason it fails is that MyRocks (or MariaRocks) does not return the
table_flags() & HA_PRIMARY_KEY_IN_READ_INDEX
|
flag. See https://github.com/facebook/mysql-5.6/issues/376 for details.
This doesn't prevent Index Condition Pushdown in MySQL, but it does prevent it in MariaDB.
Attachments
Issue Links
- is part of
-
MDEV-9658 Make MyRocks in MariaDB stable
- Closed