flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hequn Cheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8545) Implement upsert stream table source
Date Tue, 06 Feb 2018 12:56:00 GMT

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

Hequn Cheng commented on FLINK-8545:

Hi, [~fhueske], I think you are right. For deletions on non-inserted keys, both ordered
and unordered deletions don't have to send downstream,  because \{{Table A + delete on
non-inserted keys = Table A}}. And, with upsert check, late arrived messages can be ignored
too. What do you think?

> Implement upsert stream table source 
> -------------------------------------
>                 Key: FLINK-8545
>                 URL: https://issues.apache.org/jira/browse/FLINK-8545
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API &amp; SQL
>            Reporter: Hequn Cheng
>            Assignee: Hequn Cheng
>            Priority: Major
> As more and more users are eager for ingesting data with upsert mode in flink sql/table-api,
it is valuable to enable table source with upsert mode. I will provide a design doc later
and we can have more discussions. Any suggestions are warmly welcomed !

This message was sent by Atlassian JIRA

View raw message