Closed evenyag closed 3 months ago
The changes introduce a new feature: the "merge_mode" option to the mito engine options. This includes modifications to the engine's key checking function, alongside new SQL scripts and test cases demonstrating the handling of NULL values in various merge modes like last_non_null
and last_row
.
File Path | Summary |
---|---|
src/mito2/src/region/options.rs |
Added a comment about updating a function if exposing an option to table options. |
src/store-api/src/mito_engine_options.rs |
Added "merge_mode" to valid keys in is_mito_engine_option_key . |
tests/.../common/insert/merge_mode.result |
Introduced SQL behaviors for different merge modes (last_non_null , last_row , invalid). |
tests/.../common/insert/merge_mode.sql |
Added tables and data insertion examples for various merge modes in SQL. |
In the realm where data flows,
merge_mode
now softly glows, Last non-null, or last row to keep, Through tables, it will sweep. With queries set and tests in hand, Mito's reign we now expand.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 84.67%. Comparing base (
b5c6c72
) to head (a0b0579
). Report is 7 commits behind head on main.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
This PR exposes the merge_mode table options and adds sqlness tests for it.
Checklist
Summary by CodeRabbit
New Features
last_non_null
andlast_row
during table creation and data insertion.Tests