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
We have several tables where we rely on the ReplacingMergeTree function to deduplicate data, however not all of our tables rely on this. To guarantee deduplicated data, we have set the final setting for the accessing user, however this then applies FINAL to all tables. Ideally we would be able to specify final on a per-table setting level, which would then impact how the table is queried.
Describe the solution you'd like
To be able to create a table with
CREATE TABLE .. SETTINGS final = 1;
And then all queries on that table be executed with FINAL
Describe alternatives you've considered
Use a short min_age_to_force_merge_seconds timeout to force merges, however this then has a short duplicate period
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Use case
We have several tables where we rely on the ReplacingMergeTree function to deduplicate data, however not all of our tables rely on this. To guarantee deduplicated data, we have set the final setting for the accessing user, however this then applies FINAL to all tables. Ideally we would be able to specify final on a per-table setting level, which would then impact how the table is queried.
Describe the solution you'd like
To be able to create a table with
CREATE TABLE .. SETTINGS final = 1;
And then all queries on that table be executed with FINAL
Describe alternatives you've considered
Use a short min_age_to_force_merge_seconds timeout to force merges, however this then has a short duplicate period
Additional context
The text was updated successfully, but these errors were encountered: