- Make ha_rocksdb::check_if_supported_inplace_alter() take into
account the Alter_inplace_info::ALTER_PARTITIONED flag
- Adjust the testcase to work in MariaDB
Failure to do so caused a failure in rocksdb.rocksdb test.
When test_if_cheaper_ordering computes is_covering= ...,
- MySQL calls table->file->primary_key_is_clustered()
- MariaDB calls (table->file->index_flags(nr, 0, 1) &
HA_CLUSTERED_INDEX)
The first produces true, the second used to produce false.
- EXPLAIN result differences are due to MariaDB's MDEV-11172
- Don't print the value of rocksdb_supported_compression_types
to .result file
- The rest is trivial Maria-fication
- EXPLAIN is different
- error message is
- the output order is different, because MySQL knows when to use
ha_partition::handle_unordered_scan_next_partition.
Reading the table data without any ordering happens to produce
MariaDB uses ha_partition::handle_ordered_index_scan for this index
scan (this is a deficiency), which causes it to produce the row with
pk=1 first.
MariaDB uses
- MariaDB produces a warning instead of error when the key
length is too long
- Trivial test results updates
- rocksdb.rocksdb still fails but this commit makes some progress.
rocksdb.lock: LOCK TABLE t1 LOW_PRIORITY WRITE does not produce a
warining in MariaDB
rocksdb.unique_check:
- MariaDB's mtr prints connection actions
- New (but temporary) ER_LOCK_WAIT_TIMEOUT text
rocksdb.allow_pk_no_concurrent_insert:
- Fix path
rocksdb.locking_issues
- Fix path
- The test still fails but for a different reason now
- Introduce @@rocksdb_supported_compression_types read-only variable.
It has a comma-separated list of compiled-in compression algorithms.
- Make rocksdb.compression_zstd test skip itself when ZSTD support
is not compiled in
I've moved it to storage/rocksdb/mysql-test/rocksdb/my.cnf,
but replication tests do not include that file?
Will need to get back to this when getting replication to work
facebook/mysql-5.6 has error messages with extra info, MariaDB doesn't
have extra info:
-ERROR HY000: Lock wait timeout exceeded; try restarting transaction: Timeout on index: test.t1.PRIMARY
+ERROR HY000: Lock wait timeout exceeded; try restarting transaction
This patch updates .result files so that differences do not get in the
way; if we decide to use new error message text in MariaDB, this patch
can be applied in reverse.
- Before this, one had to provide appropriate --mysqld=.... options to
mysql-test-run.
- Also moved one option from rocksdb/suite.opt to rocksdb/my.cnf.
MySQL's log entries start with log entries like
YYYY-MM-DD 08:25:04 ...
while MariaDB
YYYY-MM-DD 8:25:04 ...
note that '08' turns into ' 8'.
Made grep pattern to account for this.
- Make the same changes as in the previous cset and in
a cset changing rocksdb.col_opt_null a few csets before.
- MySQL 5.6.11 has fixes for Bug #68472, Bug #16394472, MariaDB doesn't.
adjust the testcase accordingly.
Make the same changes as with rocksdb.col_opt_null a few csets before:
- MariaDB doesn't provide a default value for non-NULL columns
- Wording in error messages is different
- limits for DECIMAL columns are different
- YEAR(2) is deprecated but still supported
- Also added a --sorted_result for an I_S query.
Based on discussion at maria-developers@:
- Remove 'Support --force-restart "pseudo-argument"'
that was added a few csets before
- Instead, use "source include/restart_mysqld.inc" in the
testcases that need a freshly-started server
The differences are due:
- MariaDB 10.1+ assigns different DEFAULT values
= in some cases, MariaDB's table has no default value, while
MySQL's has '' as default.
= BLOB/TEXT can have a default value.
- MariaDB's MTR runs tests with diffferent timezone (affects result of
FROM_UNIXTIME())
- MySQL has removed YEAR(2). MariaDB produces warning but still creates
the column of this type.
- Different wording in warning/error messages.
- MariaDB has different wording for a few error messages
- MySQL changed Extra='' to Extra=NULL for EXPLAIN outputs, MariaDB didnt
- The testsuite in storage/rocksdb/mysql-test needs paths to include
files adjusted
- In SHOW COLUMNS output, Extra column is "NULL" in MariaDB vs '' in MySQL
Running MTR tests produces an error like this after the test run:
... 140562896741120 [ERROR] Invalid (old?) table or database name '.rocksdb'
There seems to be no way to have the MariaRocks to prevent these, so
the current way to fix them is to have --ignore-db-dirs in my.cnf
- Add include/have_rocksdb.inc (TODO: is there any way to have this
file somewhere under storage/rocksdb/mysql-test ?)
- Make rocksdb.test require have_partition.inc because it uses
partitioned tables
copy of
commit 86587affafe77ef555f7c3839839de44f0f203f3
Author: Tian Xia <tianx@fb.com>
Date: Tue Oct 4 10:01:52 2016 -0700
Allow filtering of show commands through admission control
