[
https://issues.apache.org/jira/browse/CALCITE-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rui Wang updated CALCITE-4125:
------------------------------
Description:
Right now stream JOIN is supported in syntax (e.g. in planner), however, there
are more areas needs a enhancement:
1. Does windowing strategy in JOIN have a constraint? For example, is a TUMBLE
stream allowed to join a HOP stream?
2. If there is any constraints on windowing strategy in JOIN, how will that
affect JOIN reordering?
3. How to optimize stream join stream or stream join table, which, by nature,
should be different from table join table?
was:
Right now stream JOIN is supported in syntax (e.g. in planner), however, there
are more areas needs a enhancement:
1. Does windowing strategy in JOIN have a constraint? For example, is a TUMBLE
stream allowed to join a HOP stream?
2. If there is any constraints on windowing strategy in JOIN, how will that
affect JOIN ordering?
3. How to optimize stream join stream or stream join table, which, by nature,
should be different from table join table?
> Stream Join
> -----------
>
> Key: CALCITE-4125
> URL: https://issues.apache.org/jira/browse/CALCITE-4125
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Rui Wang
> Priority: Major
>
> Right now stream JOIN is supported in syntax (e.g. in planner), however,
> there are more areas needs a enhancement:
> 1. Does windowing strategy in JOIN have a constraint? For example, is a
> TUMBLE stream allowed to join a HOP stream?
> 2. If there is any constraints on windowing strategy in JOIN, how will that
> affect JOIN reordering?
> 3. How to optimize stream join stream or stream join table, which, by nature,
> should be different from table join table?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
