Google Summer of Code 2015
We participated in the Google Summer of Code 2015. MariaDB and the MariaDB Foundation believe we are making a better database that remains a drop-in replacement to MySQL. We also work on making LGPL connectors (currently in C, Java, C++ in development) and on MariaDB Galera Cluster, which allows you to scale your reads & writes. Lately, we also have MariaDB MaxScale which is a pluggable database proxy.
- Where to start
- Some suggested projects
- Enhancing mysqlbinlog
- Indexes on virtual columns
- Table functions
- Aggregate stored functions
- GIS enhancements
- Port InnoDB memcached interface to MariaDB
- Automatic provisioning of slave
- Indexes for BLOBs (in MyISAM and Aria)
- Improved temporary tables
- Provide GTID support for MHA
- Import and export popular data formats from and to dynamic columns
- MaxScale filter to capture incoming operations for consumption in external sources
- MaxScale filter to real Microsoft SQL Server syntax
Where to start
Please join us at
irc.freenode.net at #maria to mingle with the community. Don't forget to subscribe to email@example.com (this is the main list where we discuss development).
At the moment, tasks that may be suitable for GSoC 2015 are listed in the MariaDB Issue Tracker under «GSoC 2015 tasks»
Some suggested projects
This project consists of two parts -- it can either be performed by 2 students or 1 student with the relevant skills:
Support for GTID in mysqlbinlog
The mysqlbinlog tool needs to be updated to understand the replication feature called Global Transaction IDs (GTIDs) in MariaDB 10. The current version does not support GTIDs and the MySQL variant does not speak MariaDB 10's GTIDs.
Remote backup of binary logs
Indexes on virtual columns
We have the concept of virtual (non-materialized) columns, and currently to have an index on a virtual column one has to materialize it. To support indexes on fully virtual columns, a storage engine must call back into the server to calculate the value of the virtual column.
User functions (UDF-like) that return a table, rows and columns. It should be possible to use it in other statements. A possible implementation could be: the function exports a generator, we create a handler of the hidden "storage engine" class, no indexes, and convert this generator to rnd_init/rnd_next. Need to disable rnd_pos somehow. Alternatively, it can materialize the result set in a temporary table (like information_schema does), then this table can be used normally.
Aggregate stored functions
With CREATE FUNCTION one can create functions in SQL, but this syntax doesn't allow one to create an aggregate function (like SUM, AVG, etc). This task is to add support for aggregate stored functions.
GIS enhancements for 10.1 that we want to work on include adding support for altitude (the third coordinate), converters (eg. ST_GeomFromGeoJSON - ST_AsGeoJSON, ST_GeomFromKML - ST_AsKML, etc.), Getting data from SHP format (shp2sql convertor), as well as making sure we are fully OpenGIS compliant.
Port InnoDB memcached interface to MariaDB
MySQL 5.6 has a memcached plugin to InnoDB. MySQL 5.7 has improved performance of this. The task would be to port this to run against MariaDB, and make it work against XtraDB/InnoDB for the 10.2 series of MariaDB.
Automatic provisioning of slave
The purpose of this task is to create an easy-to-use facility for setting up a new MariaDB replication slave.
Indexes for BLOBs (in MyISAM and Aria)
MyISAM and Aria support special kinds of indexes that only store the hash of the data in the index tree. When two hashes match in the index, the engine compares actual row data to find whether the rows are identical. This is used in internal temporary tables that the optimizer creates to resolve SELECT DISTINCT queries. Normal unique indexes cannot always be used here, because the select list can be very long or include very long strings.
This task is to provide a direct SQL interface to this feature and to allow users to create these indexes explicitly. This way we can have unique constraints for blobs and very longs strings.
Improved temporary tables
It is a well-known and very old MySQL/MariaDB limitation that temporary tables can only be used once in any query; for example, one cannot join a temporary table to itself. This task is about removing this limitation
Provide GTID support for MHA
MySQL Master HA (MHA) is a tool to assist with automating master failover and slave promotion within short downtime, without suffering from replication consistency problems, and without performance penalty. We would like to have this tool support MariaDB 10 GTIDs.
Import and export popular data formats from and to dynamic columns
Provide import and export functions for popular data formats like JSON, XML (limited), PHP, ... for Connector/C and MariaDB Server (which use same code base for dynamic columns)
|Mentor:||Oleksandr Byelkin, Georg Richter|
MaxScale filter to capture incoming operations for consumption in external sources
Design a filter that will capture incoming inserts, updates and deletes, for specified tables (as regex) in a separate log file that is consumable as JSON or CSV form. So that external ETL processes can process it for data uploading into DWH or big data platform. Optionally a plugin that takes this log into a Kafka broker that can put this data on Hadoop node can be developed as next step.
MaxScale filter to real Microsoft SQL Server syntax
Develop a MaxScale filter that will translate SQL Server syntax to MariaDB syntax. Develop a SQL Server client protocol plugin.
|Mentor:||Markus Makela & Massimiliano Pinto|