[ 
https://issues.apache.org/jira/browse/IGNITE-28947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104043#comment-18104043
 ] 

Ignite TC Bot commented on IGNITE-28947:
----------------------------------------

{panel:title=Branch: [pull/13429/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13429/head] Base: [master] : New Tests 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL 3{color} [[tests 
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9251918]]
* {color:#013220}IgniteCalciteTestSuite3: 
RecursiveCteIntegrationTest.testHierarchicalQueryIsNotSupported - PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9251951&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9251951 
rerunBuildIds=none{color}

> 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
>         Attachments: RecursiveCteIntegrationTest.java
>
>          Time Spent: 10m
>  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)

Reply via email to