-
Notifications
You must be signed in to change notification settings - Fork 752
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
refactor: use temp table to refactor materialized cte #16900
Conversation
ba5f7d5
to
b4ced32
Compare
Wait #16941 |
can not use temp table in http handler if cookie is not enabled http session for temp table has supported, is there a plan to update client? cc @everpcpc @sundy-li |
@youngsofun to support it. |
bendsql in runner upgraded to 0.23.1 |
2619b9e
to
8e6eecd
Compare
Docker Image for PR
|
Docker Image for PR
|
caab63e
to
59e593a
Compare
Docker Image for PR
|
It seems that ci benchmark is broken. cc @everpcpc |
cc @zhang2014 |
tests/sqllogictests/suites/mode/standalone/explain/materialized_cte.test
Outdated
Show resolved
Hide resolved
22665f6
to
99567d7
Compare
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
Use temp table to refactor materialized cte:
persist_materialized_cte
to decide if the cte is to persist storage or not. The default behavior is using the memory table. If the user's materialized cte results are large and may OOM, they can open the setting.Tests
Type of change
This change is