The Ultimate Guide to High Availability with MariaDB

Spider storage engine condition pushdown

Hi,

We are using Spider storage engine for sharding with MariaDB.
MariaDB version - 10.0.10
Spider version - 3.2
Platform - CentOs 6.5

Problem:
----------------

We have a simple scenario, where we have a table with Spider storage engine, which is list partitioned based on a column.
Each partition is pointing to a shard.
Whenever a query is fired from the Master database with a WHERE clause, the WHERE condition is not being pushed to the shard, instead all the data from shard is being transferred to the DB where Spider storage engine is present. 
I came to know that this issue has been fixed in the Spider storage engine, and also I verified the MariaDB 10.0.9-spider-3.2 source code and it has cond_push and cond_pop functions.
Please let me know how else can I enable this condition pushdown.

Regards,
-Lokesh Kumar

Answer Answered by Daniel Black in this comment.

have you tried set global optimizer_switch='engine_condition_pushdown=on'?

Don't forget to add to my.cnf

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.