Enable typed Array and Tuple SQL planning - #658
Merged
Merged
Conversation
…-values # Conflicts: # control_plane/src/query_plan/clickhouse_exact.rs # data_plane/src/query_engines/asap_clickhouse_query_engine/relational_adapter.rs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SQL arrayElement and tupleElement expressions now use the Planner collection frontend and the existing shared QueryPlan operators. Pin the reviewed Planner revision and verify its output through a real backend process against ClickHouse.
The process fixture installs the selected plan, executes typed external leaves followed by local Array/Tuple projections, and checks metadata, NULL/default behavior, time boundaries, and Float64 values against native ClickHouse. It also asserts the external_dag execution path; this is operator composition, not summary acceleration. Existing mixed summary tests reuse the extracted process launcher.
Validation: all three ClickHouse differential process tests passed on this head (8.36 seconds), using the pinned sketch library and a real ClickHouse server. The six-row collection fixture does not establish workload performance. Lambda expressions, tuple dot syntax, and direct collection outputs remain unsupported.