In June, I told about the consolidation of the MariaDB project tools. The final piece of this consolidation, to report bugs in the MariaDB project tracking tool called JIRA has now been finalized.

Bug reporting stays open! JIRA is open to anyone. The bug reports are publicly available, even without logging in and as a bonus it will be easier to follow what is going on in the project since you don’t have to jump between several tools to get the complete picture.

All bugs that existed in Launchpad have been migrated to JIRA. To find a bug that was originally reported on Launchpad use the following approaches:

  • If you happen to have the original bug id you can search for the bug by typing lp:bugid into the search field in the upper right corner of JIRA. Also, if you have the link to the bug report on Launchpad, you’ll be able to open that bug report and get hold of the id (which by the way also can be seen in the URL).
  • You can also search on keywords, e.g. “ALTER TABLE” or “microsecond”
  • In addition JIRA includes a nice search functionality with which more advanced searches can be done like searching for issues reported by a specific user. This search is found in the top navigation under “Issues” and is called “Search for issues”.

Getting the bugs into the project tracking tool of MariaDB can be seen as an enabler of the personal task I set for myself in my MariaDB Directions blog post last week, on creating a longer-term roadmap for MariaDB. Now with the development tasks, bug reports and planning inside the same tool, anyone can see what is going into which version of MariaDB.

Please make yourself familiar with MariaDB development by checking out JIRA and do participate in the development by:

  • Creating new issues in JIRA for features you would like to see in upcoming versions of MariaDB
  • Reporting possible bugs in MariaDB, “Create Issue” in JIRA
  • Commenting and adding more information to existing issues in JIRA

You’ll have to create an account for yourself to do that, which is very straight forward. Just click on the Sign Up –link in conjunction with the Login and follow the instructions.

If you did report MariaDB bugs on Launchpad before you’re also seen as the reporter of the bug in JIRA and an account has automatically been created for you in JIRA. However this account doesn’t hold your email address, since it was not (easily at least) possible to export that from Launchpad (probably because of privacy reasons). We are glad to activate your automatically created account in JIRA. Todo so please send us your name and email address through the Monty Program contact form.


We’re pleased to announce the first preview version of the Cassandra Storage Engine!

The Cassandra Storage Engine (SE) allows access to Cassandra databases from MariaDB/MySQL, and to provide data integration between the SQL and NoSQL worlds.

Have you ever needed to

  • grab some of Cassandra’s data from your web frontend, or SQL query?
  • insert a few records into Cassandra from some part of your app?

With Cassandra SE, this is easily possible. Cassandra SE makes Cassandra’s column families appear as MariaDB/MySQL tables that you can insert to, update, and select from. You can perform joins on Cassandra data, or againist data in Cassandra and data in MariaDB.

Today we’re releasing a source tarball, as well as a binary tarball package for Ubuntu 12.04. Download links and documentation for this preview release are available at the Cassandra Storage Engine page in our Knowledgebase. Try it out and let us know what you think!

Infor announced this week, that they will provide open source database alternatives to some of their products. MariaDB has been chosen, tested, and certified by Infor to be the open source database of choice (together with MySQL) for the Infor LN and ION products. Infor LN is Infor’s flagship ERP and is sometimes better known by its former name, Baan. It has 25 years of manufacturing know-how built into it and is used by more than 5,000 companies worldwide in a wide range of industries. These include automotive, industrial equipment and machinery, high tech and electronics, and aerospace and defense. This is a big stamp of approval that even the most critical systems can be run on MariaDB.

In other news, there are currently several really interesting paths coming together into some important milestones. The rest of this post will be about them and I hope you are as excited about them as we are and please do let us know what you think, as always.

MariaDB 10.0

First up, MariaDB 10.0. In my late spring blog post about the next version of MariaDB, we informed you that the next version will be called MariaDB 10.0. There was a little storm of feedback on this and most of the feedback was related to how different tools will react with this versioning change. We’re still looking into this, but it’s good to remember that MariaDB includes features and functionality that aren’t in MySQL and that it would be good for tools to handle the MariaDB version string separately to make use of the advantages of MariaDB, like extended statistics and more switches compared to MySQL. Currently we are just a few days away from releasing the Alpha version of MariaDB 10.0 and I would like to make particular mention of two features:

  • Multi-source replication, which is a longtime wish of many users. In scenarios where you partition your data over many masters you can then replicate the data from all masters onto one slave. This is very useful for analytical queries towards the whole data or for backing up all data.
  • Get the query plan of a running statement (SHOW EXPLAIN). In MySQL and MariaDB up until now a query plan printout (EXPLAIN) wasn’t always correct because the actual running query wasn’t studied, which is the case now with SHOW EXPLAIN.

To get more details on what MariaDB 10.0 includes, please read Monty’s blog post. The Alpha version of MariaDB 10.0 is about to be released. Stay tuned!

Cassandra, JSON and Dynamic Columns

For those of you keeping score, one and a half years ago Dynamic Columns was introduced into MariaDB. This feature allows you to store a different set of columns for every row in a table. In that manner Dynamic Columns can be called NoSQL-like.

Whether or not the first intention of introducing Dynamic Columns was to become the foundation for data interchange, it definitely has. Since we introduced Dynamic Columns we have received user input, and have researched how to make it better and the end result is that Dynamic Columns now has some new capabilities:

  • Database interoperability: It’s pretty rare that companies use only a single type of databases and even critical business systems are often built on several different types of databases. Usually the data residing in those different databases are combined in an upper application level. MariaDB introduces the possibility to do this at a low level inside the MariaDB database. The first implementation of this is integration with Cassandra. Yes, you can now combine data residing in Cassandra with data inside MariaDB and all this is done through normal looking queries on the MariaDB side.
  • Data interchange: JSON has become a very popular standard for data interchange. In Dynamic Columns one can now request a row in JSON format.

The feature preview release of the Dynamic Columns with the above features included will be made available today and all of this will naturally become part of MariaDB 10.0, currently scheduled for the version 10.0.1.

MariaDB Galera Cluster

Next, you may recall that at the beginning of the month we introduced MariaDB Galera Cluster. This Alpha version has been out now for about three weeks and we’ve been testing and fixing it to prepare for the next development release. To be honest, most end user problems have been related to packaging and running the product on a specific platform. The final steps of finalizing, and preparing for, the Beta version are currently being taken.

Be part of the MariaDB project

Another push we’re making at this time is to actively extend involvement in MariaDB. Every new installation of MariaDB of course counts to this, but what I’m actually referring to is that we want to involve more companies and individuals in the MariaDB project. This doesn’t necessarily mean digging into the MariaDB source code. That is always welcome, of course. But another very important way to help the project is to sponsor specific work in MariaDB or make general financial contributions.

Patrik Sallner, CEO of SkySQL, said yesterday in his blog post about the launch of their new SkySQL products and offerings for MariaDB and MySQL, that there are a lot of businesses out there having really critical workloads running on MySQL and MariaDB. If you happen to represent one of these businesses, please consider the possibility of being part of planning the future of the product your critical business is run on. Please contact me through Monty Program for further information.

A personal task and wish

Lastly, we try to be as open as possible inside the MariaDB team in regards to the MariaDB project and I think we have succeeded fairly well. We are definitely continuing on that path. However there are always things we can do to improve, and one of them that I personally think is important for both MySQL and MariaDB is evolution predictability. Users want to know in which direction the product is going and to have a roadmap that clearly tells what’s going to be in the next version and what is planned for future versions after that. I will work on the MariaDB side to create a longer-term roadmap with as many details as possible and I do hope we’ll see something similar from the Oracle MySQL team.