"What is MariaDB 10.3" shows all features already implemented for 10.3
The following features were discussed at the 2016 MariaDB Developer's Meeting for consideration in MariaDB 10.3. See Thoughts on MariaDB Server 10.3 from MariaDB Developers Meeting in Amsterdam, part 1.
- Hidden Columns
- Long unique constraints
- SQL based CREATE AGGREGATE FUNCTION
- Now it looks like one step ahead has been made with the implementation of a Pluggable Data Type API. It still exists in a separate branch, but it is now planned for inclusion in MariaDB Server 10.3. On top of the API the idea is to build User Defined Types according to the SQL Standard.
- Better support for CJK (Chinese, Japanese, and Korean) languages. The idea is to include the ngram full-text parser and MeCab full-text parser plugins. Also the GB 18030 standard for Chinese charsets is on the radar for 10.3.
- On the storage engine side MyRocks will be included in 10.2, which will open MyRocks to a wider audience. It’s obvious that it will need work during 10.3 timeframe to grow in maturity. Another interesting storage engine discussed during the last few years is Spider, an engine that provides a sharding solution for databases. Although Spider already exists in MariaDB Server, there is a set of patches that needs to be incorporated on the server side to improve functionality and performance. These patches can be found in MDEV-7698.
- In MySQL 8.0 there are a couple of interesting new features for InnoDB that are interesting for MariaDB as well. The timelines of 10.3 and 8.0 will partially determine whether these will be in 10.3.
- InnoDB deadlock detect
- The new information schema table.
- Lock wait policy
- Persistent autoincrement
- Support for SEQUENCE
- Addition of a PL/SQL parser
- Support for INTERSECT
- Support for EXCEPT
We manage our development plans in JIRA, so the definitive list will be there. This search shows what we currently plan for 10.3. It shows all tasks with the Fix-Version being 10.3. Not all these tasks will really end up in 10.3, but tasks with the "red" priorities have a much higher chance of being done in time for 10.3. Practically, you can think of these tasks as "features that will be in 10.3". Tasks with the "green" priorities probably won't be in 10.3. Think of them as "bonus features that would be nice to have in 10.3".