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

Julian Hyde commented on CALCITE-2812:
--------------------------------------

I don't have an opinion of what should be the name and default value of the SQL 
clause.

The embodiment in the RelNode algebra can be different from SQL. (SQL is fond 
of making things 1-based, because, well, users. But we don't have to be 
consistent with SQL.)

> Add algebraic operators to allow expressing recursive queries
> -------------------------------------------------------------
>
>                 Key: CALCITE-2812
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2812
>             Project: Calcite
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 1.18.0
>            Reporter: Stamatis Zampetakis
>            Assignee: Ruben Quesada Lopez
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.20.0
>
>          Time Spent: 10h
>  Remaining Estimate: 0h
>
> In order to parse, optimize, and execute, recursive queries, expressed in 
> SQL, datalog, SPARQL, or other high level language we need first to be able 
> to represent recursive queries in relational algebra.
> The subject has been previously discussed in the dev list (see thread with 
> title [Recursive query, graph query, 
> Datalog|http://mail-archives.apache.org/mod_mbox/calcite-dev/201712.mbox/%3CCAPSgeESFyih9_hf9=uMWFN00BCR7sjf0T+FRY2=ary3ygm1...@mail.gmail.com%3E])
>  where various ideas  and optimizations were proposed. 
> In this issue, we attempt to address only the algebraic part providing the 
> following:
> # logical operator(s) for expressing recursion;
> # naive physical operator(s) for the Enumerable convention;
> # ability to create a recusive plan using the RelBuilder. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to