You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run a scheduled compaction job for append only time series tables, and it gets slower as the tables grow. ducklake_merge_adjacent_files looks at every live file in the table on each run, but only files written since the last run can be new merge candidates in my use case. min_file_size/max_file_size help a bit, but they can't express "only recent files".
Would you be open to a newer_than => TIMESTAMPTZ option, so a scheduled job can do:
For context, I'm building o11ylite, an observability app that stores logs, traces and metrics in DuckLake with frequent small ingests and periodic compaction. A time filter would drastically reduce my compaction cost on production, 🙏🏿 🙏🏿 .
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I run a scheduled compaction job for append only time series tables, and it gets slower as the tables grow.
ducklake_merge_adjacent_fileslooks at every live file in the table on each run, but only files written since the last run can be new merge candidates in my use case.min_file_size/max_file_sizehelp a bit, but they can't express "only recent files".Would you be open to a
newer_than => TIMESTAMPTZoption, so a scheduled job can do:and only consider files written after that point?
For context, I'm building o11ylite, an observability app that stores logs, traces and metrics in DuckLake with frequent small ingests and periodic compaction. A time filter would drastically reduce my compaction cost on production, 🙏🏿 🙏🏿 .
I prepared a PR here: #1363
All reactions