[
https://issues.apache.org/jira/browse/FLINK-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803963#comment-16803963
]
Jark Wu commented on FLINK-12025:
---------------------------------
Temporal table join is a big topic and should be discussed detailed in the
community. Besides the things Piotr mentioned above, there are some other
things need to consider.
1. how to keep compatible with current temporal table. (keep two ways or
deprecate one?)
2. how to join a temporal table in physical plan (lookup mode or scan mode)
3. lookup mode is the classic form to join a remote database table (i.e. join
dimension table) but need some additional information, e.g. primary keys,
indexes. The concern is how to expose these information in API.
Btw, we are also planning to support this feature in
{{flink-table-planner-blink}} first (as a subtask of blink merge) before 1.9
released.
> Support FOR SYSTEM_TIME AS OF in temporal table
> -----------------------------------------------
>
> Key: FLINK-12025
> URL: https://issues.apache.org/jira/browse/FLINK-12025
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Major
>
> Since Calcite 1.19 has been released and "FOR SYSTEM_TIME AS OF" been
> supported. I suggest we can support it in the temporal table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
