Vladislav Pyatkov created IGNITE-28947:
------------------------------------------
Summary: Handle recursive CTE planning gracefully
Key: IGNITE-28947
URL: https://issues.apache.org/jira/browse/IGNITE-28947
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
Assignee: Vladislav Pyatkov
Attachments: RecursiveCteIntegrationTest.java
This ticket does not add support for recursive CTE execution.
h3. Motivation
Calcite already parses and validates WITH RECURSIVE queries and creates
transient tables and TableSpool operators during planning. Ignite Calcite
metadata currently assumes that every TableScan unwraps to IgniteTable.
For transient CTE tables, this can cause internal metadata failures, for
example in collation or distribution calculation, before the planner reaches
the actual unsupported feature boundary.
Update metadata handling for transient tables so that recursive CTE planning
fails with a clear, stable “recursive CTE is not supported” error rather than
an internal exception.
h3. Definition of done
* A recursive CTE does not fail with an internal exception.
* The user receives a clear unsupported-feature error for recursive CTEs.
* Existing non-recursive query planning remains unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
