[jira] [Closed] (FLINK-8578) Implement rowtime DataStream to Table upsert conversion.

["Jark Wu (Jira)" <ji...@apache.org>]

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

Jark Wu closed FLINK-8578.
--------------------------
    Resolution: Duplicate

This feature has been consumed by

FLIP-149: https://cwiki.apache.org/confluence/display/FLINK/FLIP-149%3A+Introduce+the+upsert-kafka+Connector

and FLIP-136: https://cwiki.apache.org/confluence/display/FLINK/FLIP-136%3A++Improve+interoperability+between+DataStream+and+Table+API

> Implement rowtime DataStream to Table upsert conversion.
> --------------------------------------------------------
>
>                 Key: FLINK-8578
>                 URL: https://issues.apache.org/jira/browse/FLINK-8578
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Hequn Cheng
>            Assignee: Hequn Cheng
>            Priority: Major
>
> Flink-8577 implements upsert from stream under proctime. This task is going to solve the order problem introduce by proctime. As proposed by Fabian in FLINK-8545, it would be good to be able to declare a time attribute that decides whether an upsert is performed or not.
> {code:java}
> Table table = tEnv.upsertFromStream(input, 'a, 'b.rowtime.upsertOrder, 'c.key)
> {code}
> This is a good way to solve the order problem using rowtime. And an idea comes to my mind that we can even remove the `.upsertOrder`, because the rowtime attribute can only be defined once in a table schema. Removing `.upsertOrder` also makes it easier to design api for TableSource and sql, i.e, we don't need to add another new feature for the api.
> Any suggestions are welcomed!



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