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] [Comment Edited] (FLINK-8545) Implement upsert stream table source
Date Fri, 02 Feb 2018 16:09:00 GMT

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

Hequn Cheng edited comment on FLINK-8545 at 2/2/18 4:08 PM:
------------------------------------------------------------

Hi, the {{Tuple}} input format is a good choice. It is consistent with the {{UpsertStreamTableSink}}.

Yes, upsert stream source should have state so that to generate retract messages. As for the
problem of deletes on non-inserted keys, if i understand correctly, do you mean caching the
unordered delete message until the corresponding insert message comes? I was think the scenario
that only delete messages are ingested. For example, users use flink job to ingest delete messages
from a source database and output to a target database.

 

 

 


was (Author: hequn8128):
Hi, the {{Tuple}} input format is a good choice. It is consistent with the {{UpsertStreamTableSink}}.

Yes, upsert stream source should have state so that to generate retract messages. As for the
problem of deletes on non-inserted keys, if i understand correctly, do you mean caching the
unordered delete message until the corresponding insert message comes? I was think the scenario
that only delete messages are ingested. For example, users use flink job to sync delete messages
from a source database to a target database.

 

 

 

> 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
(v7.6.3#76005)

Mime
View raw message