[
https://issues.apache.org/jira/browse/CALCITE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milinda Lakmal Pathirage updated CALCITE-968:
---------------------------------------------
Attachment: CALCITE-968-0.patch
Hi [~julianhyde],
I tried a temporary fix to SqlValidatorImpl, implemented DeltaJoinTransposeRule
based on Product Rule (I don't think this is 100% correct) and wrote a simple
stream-to-relaiton join test to verify the planner. But I am getting an error
during optimization with VolcanoPlanner. According to my understanding this
can happen due to two reasons:
- A missing rule. But I think Logical to Enumerable conversion works by default.
- I am doing something incorrect when implementing ProductsTable
Highly appreciate any tips.
> 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)
