How to efficiently manage data retention in MariaDB ColumnStore?
1
vote
1
answer
39
views
I’m using MariaDB 10.11+ with ColumnStore and have created a ColumnStore table to handle large volumes of analytical data. My use case requires keeping only the last 90 days of data. The table includes a created_at column of type DATETIME for tracking data age.
However, I’ve run into the following limitations:
- ColumnStore does not support user-defined partitioning, making
time-based partitioning difficult.
- Deleting old records does not reclaim disk space (its only delete
metadata).
- The documentation suggests workarounds like creating daily tables or
truncating and recreating tables with only the required data, which
feels inefficient and operationally complex.
My question is:
Is there a more effective or officially recommended way to manage data lifecycle and enforce data retention in MariaDB ColumnStore—preferably one that allows for reclaiming disk space and minimizing operational overhead?
Any best practices, tools, or workflows others are using would be greatly appreciated
Asked by Amalka
(13 rep)
Jun 3, 2025, 06:58 AM
Last activity: Jun 11, 2025, 02:55 PM
Last activity: Jun 11, 2025, 02:55 PM