[
https://issues.apache.org/jira/browse/IGNITE-28947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107958#comment-18107958
]
Ignite TC Bot commented on IGNITE-28947:
----------------------------------------
Fixed recursive CTE planning to report unsupported queries gracefully instead
of failing unexpectedly.
The Release Note field has been filled with the wording above. Please review it
and edit it if needed.
> 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
> Priority: Major
> Labels: calcite, ignite-2, sql
> Fix For: 2.19
>
> Attachments: RecursiveCteIntegrationTest.java
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
