You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Recursive CTE support for datafusion is still in the planning stage, and it is tracked in #462. But the SQL planner still doesn't rejects the recursive CTEs and let them silently fail (or work, depending on the internal implementation).
To Reproduce
Steps to reproduce the behavior:
WITH RECURSIVE numbers(n) AS (
SELECT1as n
UNIONSELECT n +1as n FROM numbers WHERE n <10
)
SELECT*FROM numbers;
Running the query above would result with a cryptic error:
Plan("'datafusion.public.numbers' not found")
Expected behavior
It should fail immediately (even before processing the sub-expressions of the CTE) if the RECURSIVE property is used.
isidentical
changed the title
SQL Planner doesn't distungish normal CTEs from the recursive ones.
SQL Planner doesn't distinguish normal CTEs from the recursive ones.
Oct 4, 2022
Describe the bug
Recursive CTE support for datafusion is still in the planning stage, and it is tracked in #462. But the SQL planner still doesn't rejects the recursive CTEs and let them silently fail (or work, depending on the internal implementation).
To Reproduce
Steps to reproduce the behavior:
Running the query above would result with a cryptic error:
Expected behavior
It should fail immediately (even before processing the sub-expressions of the CTE) if the
RECURSIVE
property is used.Additional context
Implementation regarding recursive CTEs for datafusion is being discussed here.
The text was updated successfully, but these errors were encountered: