summaryrefslogtreecommitdiff
path: root/storage/tokudb/PerconaFT/ft/serialize/rbtree_mhs.h
diff options
context:
space:
mode:
authorJacob Mathew <jacob.mathew@mariadb.com>2018-09-11 16:29:44 -0700
committerJacob Mathew <jacob.mathew@mariadb.com>2018-09-11 16:29:44 -0700
commiteb2ca3d44586ebfb887ee54ea5e5275ee4b25623 (patch)
treecd9be9a3dfd3aaa2c948bc639a361b69988996a8 /storage/tokudb/PerconaFT/ft/serialize/rbtree_mhs.h
parente76c4c06f18c0d09a296a60b6d00332620e98e53 (diff)
downloadmariadb-git-eb2ca3d44586ebfb887ee54ea5e5275ee4b25623.tar.gz
MDEV-16912: Spider Order By column[datatime] limit 5 returns 3 rowsbb-10.2-MDEV-16912
The problem occurs in 10.2 and earlier releases of MariaDB Server because the Partition Engine was not pushing the engine conditions to the underlying storage engine of each partition. This caused Spider to return the first 5 rows in the table with the data provided by the customer. 2 of the 5 rows did not qualify the WHERE clause, so they were removed from the result set by the server. To fix the problem, I have back-ported support for engine condition pushdown in the Partition Engine from MariaDB Server 10.3. Author: Jacob Mathew. Reviewer: Kentoku Shiba.
Diffstat (limited to 'storage/tokudb/PerconaFT/ft/serialize/rbtree_mhs.h')
0 files changed, 0 insertions, 0 deletions