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

Julian Hyde commented on CALCITE-968:
-------------------------------------

[~milinda], Your change from {{union.getInputs()}} to 
{{call.getChildRels(union)}} was not right (and isEmpty returns false when 
applied to a RelSubset). The real issue is that Volcano is not populating the 
list of siblings. I have logged CALCITE-990 for this, and will have a fix soon.

If you're wondering why this was not discovered first: I previously tested 
PruneEmptyRules.UNION_INSTANCE with HepPlanner, which does not have this 
problem. 

> Support stream joins
> --------------------
>
>                 Key: CALCITE-968
>                 URL: https://issues.apache.org/jira/browse/CALCITE-968
>             Project: Calcite
>          Issue Type: New Feature
>          Components: core, stream
>            Reporter: Milinda Lakmal Pathirage
>            Assignee: Julian Hyde
>         Attachments: CALCITE-968-0.patch
>
>
> Stream joins are used to relate information from different streams or stream 
> and relation combinations. Calcite lacks (proper) support for 
> stream-to-relation joins and stream-to-stream joins.
> stream-to-relation join like below fails at the SQL validation stage.
> select stream orders.orderId, orders.productId, products.name from orders 
> join products on orders.productId = products.id
> But if 'products' is a stream, the query is valid according to Calcite, even 
> though the stream-to-stream join in above query is not valid due to unbounded 
> nature of streams.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to