You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Dawid Wysakowicz (JIRA)" <ji...@apache.org> on 2019/03/11 10:26:00 UTC

[jira] [Commented] (FLINK-11842) Introduce FlinkLogicalMatch

    [ https://issues.apache.org/jira/browse/FLINK-11842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789378#comment-16789378 ] 

Dawid Wysakowicz commented on FLINK-11842:
------------------------------------------

AFAIK we agreed to follow SQL standard. Any non-sql compliant changes, should be discussed in the ML first, I think.

> Introduce FlinkLogicalMatch
> ---------------------------
>
>                 Key: FLINK-11842
>                 URL: https://issues.apache.org/jira/browse/FLINK-11842
>             Project: Flink
>          Issue Type: New Feature
>          Components: API / Table SQL
>            Reporter: godfrey he
>            Assignee: godfrey he
>            Priority: Major
>
> {{FlinkLogicalMatch}} supports output timeout events in Blink, which does not support in Flink. However this nuances involves quite a few changes in Calcite, include parser, sql validation, RelBuilder and so on.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)