[MySQL][Spider][VP]Spider-3.2 VP-1.1 released

I'm pleased to announce the release of Spider storage engine version 3.2(rc) and Vertical Partitioning storage engine version 1.1(beta).
Spider is a Storage Engine for database sharding.
http://spiderformysql.com/
Vertical Partitioning is a Storage Engine for vertical partitioning for a table.
http://launchpad.net/vpformysql

Please use the following for downloading binary file.
http://spiderformysql.com/download_spider.html

The main changes in this version are following.
Spider
- Add server parameter "spider_log_result_error_with_sql", "spider_version", "spider_internal_xa_id_type", "spider_casual_read", "spider_dry_access" and "spider_delete_all_rows_type".
- Add table parameter "casual_read" and "delete_all_rows_type".

Vertical Partitioning
- Add server parameter "vp_version".

From this release, release target is not only MySQL 5.5 but also MariaDB 10.0. MariaDB 10.0 version is bundling Spider, VP and Mroonga. Please try to use this. You can use Bached Key Access by setting join_cache_level to 5 and more. So please set it.
Limited Spider features for MariaDB 10.0 which I announced are now available except "Using Spider table through handlersocket".

Please see "99_change_logs.txt" in the download documents for checking other changes.

Thanks to Stephane, Nicolas, Koichi, Akihiko, Yasunori for supporting.

Enjoy!

[MariaDB][Spider]Spider is bundled in MariaDB!

Spider storage engine is bundled in MariaDB 10.0.4.
https://downloads.mariadb.org/mariadb/10.0.4/

After this release, you can use Spider immediately by installing MariaDB.
For using Spider after installing MariaDB, please execute "install_spider.sql"
which under share directory.

MariaDB 10.0.4 is still alpha version, so please don't use on production systems.
Currently, MariaDB bundled Spider has the following difference than MySQL bundled Spider.

New features
  batched key access
    This is a feature for join performance improvement.
    You can use BKA by setting join_cache_level to 5 and more.
  assisted discovery
    This is a feature for taking table structure from data node.
    For example, if there is a table structure as the following

CREATE TABLE `t1` (
  `id` bigint NOT NULL,
  `c1` varchar(100) NOT NULL,
  `c2` datetime NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

    you can create a Spider table by using the following DDL.

CREATE TABLE `t1` ENGINE=SPIDER DEFAULT CHARSET=latin1 CONNECTION='database "test", table "t1", server "s1"';

Current limited features
  Slave retring feature by using slave_transaction_retry_errors
  Using Spider table through handlersocket
  Optimization for single table updating
  Partitioned Spider table's
  - engine condition pushsown
  - fulltext index search
  - spacial index search
  - full table count optimization
  - parallel search


I and Groonga Developer Team were won the 8th Japan OSS incentive award after releasing Spider 3.0.
http://ossforum.jp/en/node/1277
Thank you for your cooperation!