
The fastest growing Open Source Database
Showing 5 of 35 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: ahmdssh
MariaDB's HNSW vector index currently builds graphs sequentially, one row at a time. This creates two problems: ALTER TABLE on large tables stalls for hours because every vector insertion runs a CPU-intensive graph traversal on a single thread, and OPTIMIZE TABLE provides no quality improvement because it blindly rebuilds with the same hardcoded parameters, also leaving dead edges from deleted rows in the graph. This proposal addresses both by hooking into MariaDB's bulk insert API to defer all graph construction until after the base table is fully populated, then building the graph in parallel across multiple worker threads. Since OPTIMIZE TABLE already falls back to a table rebuild internally, both operations share the same unified path. The result is significantly faster index construction through parallelization, and meaningfully better graph quality through configurable rebuild parameters, with no changes to the normal single-row insert path.
Mentors: Student: Jaeheon Shim
This project aims to implement the ANY_VALUE() and GROUPING() functions in MariaDB, addressing longstanding gaps in compatibility with MySQL 8.0 and modern SQL standards. Currently, the absence of these functions limits MariaDB’s usability in applications that rely on advanced GROUP BY semantics, particularly when migrating from MySQL or working with rollup queries. To solve this, I will extend MariaDB’s SQL parser and execution engine to support both functions. For ANY_VALUE(), I will implement a new aggregate function that allows safe selection of non-aggregated columns under ONLY_FULL_GROUP_BY. For GROUPING(), I will introduce a function that distinguishes between NULL values originating from rollup aggregation and those present in the underlying data, by tracking rollup state during query execution. The primary deliverables of this project include fully functional implementations of ANY_VALUE() and GROUPING() in MariaDB, comprehensive MTR test suites validating correctness and MySQL compatibility, and updated documentation describing their usage and behavior. The final outcome will improve MariaDB’s standards compliance and provide developers with essential tools for writing expressive and portable SQL queries.
Mentors: Student: Mohd Jarir Noor Khan
This project enhances MariaDB’s SQL engine by introducing native bitwise operations for binary and bit types and implementing the JSON MEMBER OF operator. Currently, bitwise operations are limited to 64-bit integers, restricting flexibility for large binary data, and JSON membership queries require complex workarounds. The project will extend the Type_handler framework and Item expression system to support byte-wise binary operations and integrate MEMBER OF into the SQL parser and execution engine. Deliverables include a new Func_handler_bit_bin for binary operations, full implementation of Item_func_json_member_of, parser extensions, and comprehensive MTR test coverage. These improvements will increase SQL expressiveness, performance, and compatibility with modern database workloads.
Mentors: Student: Itzanway
This project aims to resolve significant performance bottlenecks in MariaDB’s INFORMATION_SCHEMA when dealing with a high number of databases or tables. Currently, many INFORMATION_SCHEMA queries require the creation of internal temporary tables and expensive filesystem scans. The proposal focuses on two major optimizations: MDEV-31342: Implementing a mechanism to bypass temporary table creation for simple queries, allowing results to be streamed directly to the client. MDEV-31535: Optimizing the directory scanning process by leveraging the in-memory privilege cache to filter database/table visibility, thereby reducing redundant and slow I/O operations. Combined, these changes will drastically improve the responsiveness of metadata queries in large-scale MariaDB deployments.
Mentors: Student: Tarun Wadhwa
With MDEV-34705, MariaDB introduced the ability to store binary logs inside InnoDB tablespace files ( .ibb ) instead of traditional flat sequential files. While this brings significant performance improvements, it also creates a compatibility challenge: legacy servers and tools cannot read the new format. This project will extend mariadb-binlog to read InnoDB-format binlogs and generate legacy-format binary log files as output, ensuring backward compatibility for downgrades, migrations, and third-party tooling. Deliverables - Command line option to generate Legacy Binlog file from InnoDB based Binlog - Checksum support - Unit and Integration tests - Design documentation covering architecture, usage, and known limitations