[jira] [Resolved] (FLINK-7159) Semantics of OVERLAPS in Table API diverge from the SQL standard

["Haohui Mai (JIRA)" <ji...@apache.org>]

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

Haohui Mai resolved FLINK-7159.
-------------------------------
    Resolution: Fixed

This has been resolved as a part of FLINK-6429.

> Semantics of OVERLAPS in Table API diverge from the SQL standard
> ----------------------------------------------------------------
>
>                 Key: FLINK-7159
>                 URL: https://issues.apache.org/jira/browse/FLINK-7159
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>
> According to http://web.cecs.pdx.edu/~len/sql1999.pdf
> ISO/IEC 9075-2:1999 (E) ©ISO/IEC, 8.12 <overlaps predicate>
> {noformat}
> The result of the <overlaps predicate> is the result of the following expression:
> ( S1 > S2 AND NOT ( S1 >= T2 AND T1 >= T2 ) )
> OR
> ( S2 > S1 AND NOT ( S2 >= T1 AND T2 >= T1 ) )
> OR
> ( S1 = S2 AND ( T1 <> T2 OR T1 = T2 ) )
> {noformat}
> The Table API diverges from this semantic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)