Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Table setting final to force any queries on specific table to use FINAL #63683

Open
rorylshanks opened this issue May 13, 2024 · 1 comment
Labels

Comments

@rorylshanks
Copy link

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

Add any other context or screenshots about the feature request here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants