You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Shengkai Fang (Jira)" <ji...@apache.org> on 2020/07/01 02:18:00 UTC
[jira] [Commented] (FLINK-15221) supporting Exactly-once for kafka
table APi
[ https://issues.apache.org/jira/browse/FLINK-15221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149050#comment-17149050 ]
Shengkai Fang commented on FLINK-15221:
---------------------------------------
According to [FLIP-122 |https://cwiki.apache.org/confluence/display/FLINK/FLIP-122%3A+New+Connector+Property+Keys+for+New+Factory], we have already introduced new property keys and it's not suitable to continue using key '{{connector.sink-semantic}}'. I think key '{{sink.semantic}}' is a better idea, which has the same format as key '{{sink.partitioner}}'.
> supporting Exactly-once for kafka table APi
> -------------------------------------------
>
> Key: FLINK-15221
> URL: https://issues.apache.org/jira/browse/FLINK-15221
> Project: Flink
> Issue Type: Wish
> Components: Table SQL / API
> Reporter: chaiyongqiang
> Assignee: chaiyongqiang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Table Api doesn't support End to End Exactly once sematic like datastream Api. Does Flink have a plan for this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)