You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2021/10/01 08:45:00 UTC

[jira] [Closed] (FLINK-19792) Interval join with equal time attributes is not recognized

     [ https://issues.apache.org/jira/browse/FLINK-19792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther closed FLINK-19792.
--------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

Fixed in master: 7033cbfe404bea1519d3342a611e2f92768d70f9

I did not back port this change due to the involved plan changes. A workaround has been mentioned in the comments.

> Interval join with equal time attributes is not recognized
> ----------------------------------------------------------
>
>                 Key: FLINK-19792
>                 URL: https://issues.apache.org/jira/browse/FLINK-19792
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner
>            Reporter: Timo Walther
>            Assignee: Francesco Guardiani
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available
>             Fix For: 1.15.0
>
>
> A user reported that interval joins with equal time attribute predicate are not recognized, instead a regular inner join is used:
> For example:
> {code}
> table1 = table_env.from_path("table1")
> table2 = table_env.from_path("table2")
> print(table1.join(table2).where("ts = ts2 && id = id2").select("id, ts")
> {code}
> The documentation clearly states that this should be supported:
> {code}
> For example, the following predicates are valid interval join conditions:
> ltime === rtime
> ltime >= rtime && ltime < rtime + 10.minutes
> {code}
> Source: https://ci.apache.org/projects/flink/flink-docs-release-1.11/dev/table/tableApi.html#joins
> See also the discussion here:
> https://stackoverflow.com/q/64445207/806430



--
This message was sent by Atlassian Jira
(v8.3.4#803005)