Spider Feature Matrix
You are viewing an old version of this article. View
the current version here.
MariaDB starting with 10.0.4
The Spider storage engine was introduced in MariaDB 10.0.4
Not complete yet - still being updated
F(*) Federation only , P(*)partioning only . Spider column is for SpiderForMySQL found on the Spider web sIte.
| Feature | Spider | 10.0.6 | 10.0 RC |
|---|---|---|---|
| Clustering and High Availability | |||
| Commit, Rollback transactions on multiple backend | Yes | Yes | Yes |
| Multiplexing to a number of replicas using xa protocol 2PC | Yes | Yes | Yes |
| Split brain resolution based on a majority decision, failed node is remove from the list of replicas | Yes | Yes | Yes |
| Enable a failed backend to re enter the cluster transparently | No | No | No |
| Synchronize DDL to backend, table modification, schema changes | No | No | No |
| Synchronize DDL to other Spider | No | No | No |
| Transparent partitioning | No | No | No |
| Covered by generic SQL test case | Yes | Yes | Yes |
| Heterogenous Backends | |||
| MariaDB and MySQL database backend | Yes | Yes | Yes |
| Oracle database backend, if build from source against the client library 'ORACLE_HOME' | Yes | Yes | Yes |
| Local table attachment | Yes | Yes | Yes |
| Performance | |||
| Index Condition Pushdown | No | No | Yes |
| Engine Condition Pushdown | Yes | F(*) | Yes |
| Concurrent partition scan | Yes | No | Yes |
| Batched key access | Yes | P(*) | Yes |
| Block hash join | No | Yes | Yes |
| HANDLER backend propagation | Yes | F(*) | Yes |
| HANDLER backend translation from SQL | Yes | F(*) | Yes |
| HANDLER OPEN cache per connection | No | No | Yes |
| HANDLER use prepared statement | No | No | Yes |
| HANDLER_SOCKET protocol backend propagation | Yes | No | Yes |
| HANDLER_SOCKET backend translation from SQL | No | No | No |
Map reduce for ORDER BY ... LIMIT | Yes | Yes | Yes |
Map reduce for MAX & MIN & SUM | Yes | No | Yes |
Map reduce for some GROUP BY | Yes | No | Yes |
| Batch multiple WRITES in auto commit to reduce network round trip | Yes | Yes | Yes |
| Relaxing backend consistency | Yes | Yes | Yes |
| Execution Control | |||
| Configuration at table and partition level, settings can change per data collection | Yes | Yes | Yes |
| Configurable empty result set on errors. For API that does not have transactions replay | Yes | Yes | Yes |
| Query Cache tuning per table of the on remote backend | Yes | Yes | Yes |
| Index Hint per table imposed on remote backend | Yes | Yes | Yes |
| SSL connections to remote backend connections | Yes | Yes | Yes |
| Table definition discovery from remote backend | Yes | F(*) | ? |
| Direct SQL execution to backend via UDF | Yes | Yes | Yes |
| Table re synchronization between backends via UDF | Yes | Yes | Yes |
| Maintain Index and Table Statistics of remote backends | Yes | Yes | Yes |
| Can use Independent Index and Table Statistics | No | Yes | Yes |
| Maintain local or remote table increments | Yes | Yes | Yes |
| LOAD DATA INFILE translate to bulk inserting | Yes | Yes | Yes |
| Performance Schema Probes | Yes | Yes | Yes |
| Load Balance Reads to replicate weight control | Yes | Yes | Yes |
| Fine tuning tcp timeout, connections retry | Yes | Yes | Yes |
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.
