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

Add max_execution_time_leaf #46102

Closed
jorisgio opened this issue Feb 7, 2023 · 0 comments · Fixed by #51823
Closed

Add max_execution_time_leaf #46102

jorisgio opened this issue Feb 7, 2023 · 0 comments · Fixed by #51823
Labels

Comments

@jorisgio
Copy link
Contributor

jorisgio commented Feb 7, 2023

Use case
Currently there is max_execution_time setting, that can be set in subqueries. But it makes it hard to use this setting with distributed sub-queries, as it is likely that timeout will be reached before distributed subquery finished.

Describe the solution you'd like

Add max_execution_time_leaf settings similar to the other restrictions on query complexity that only apply to distributed sub queries.

Describe alternatives you've considered

It is possible to workaround this using features like view, or dyanmically with cluster(view()) to set manually timeout in the subquery since we have control over them and they are not generated internally. But it is much less handy than simply using distributed tables, and for some reason other max_* seettings have a leaf version.

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