Vicențiu Ciorbaru - MariaDB ColumnStore – A Columnar Storage Engine, First Class Citizen in MariaDB

#MariaDB has had ColumnStore (a columnar storage engine) available for a while now. The problem was that #ColumnStore (formerly known as #InniDB) was coded in such a way that required a custom version of MariaDB to function. The installation was also non-trivial, with quite a set of dependencies needed.

Comment 💬, Share 🔗, Like 👍, and Subscribe ✅ to our channel 📺, and turn on the 🔔 to be alerted to new videos about #OpenSource #Databases... and many other things!

After a significant amount of work, both within MariaDB's codebase and ColumnStore's codebase, it is now possible with MariaDB 10.5 to simply load the ColumnStore plugin and run CREATE TABLE ... ENGINE=ColumnStore.
In this talk we will do an overview of the state of ColumnStore in MariaDB, discuss use cases as well as cover some implementation details to better understand performance implications when using #ColumnStore.

You can find more information about #OpenSource #Databases and Percona Database Events in these links 👇👇👇

Connect With us on our Social Networks 👇👇👇

[ranjjoseable]

Thanks! This a great presentation.
I have a confusion now! At 20:21 it is said that running multiple queries in parallel, this columnstore would create problems (bottlenecks). I'm evaluating using columnstore for building a dashboard module. The module will involve multiple people running queries in parallel. So what does it mean in this context? many the dashboard will invoke simultaneous requests to aggregate data and show and there will be filters too that users may apply. Is using columnstore a good approach in this case!?