You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2022/09/24 02:39:00 UTC

[jira] [Comment Edited] (FLINK-29098) StoreWriteOperator#prepareCommit should let logSinkFunction flush first before fetching offset

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

Jingsong Lee edited comment on FLINK-29098 at 9/24/22 2:38 AM:
---------------------------------------------------------------

master: 50b1b2951fcdfbfc139e21950086dddb3e01c690
release-0.2: db55ca641654a75e69f56ae3c34ccc08ec90f205


was (Author: lzljs3620320):
master: 50b1b2951fcdfbfc139e21950086dddb3e01c690

> StoreWriteOperator#prepareCommit should let logSinkFunction flush first before fetching offset
> ----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-29098
>                 URL: https://issues.apache.org/jira/browse/FLINK-29098
>             Project: Flink
>          Issue Type: Bug
>          Components: Table Store
>    Affects Versions: table-store-0.3.0
>            Reporter: Jane Chan
>            Assignee: Jane Chan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: table-store-0.3.0, table-store-0.2.1
>
>
> The cause for unstable CompositePkAndMultiPartitionedTableITCase#testEnableLogAndStreamingReadWriteMultiPartitionedRecordsWithMultiPk was found that the StoreWriteOperator#prepareCommit may get an empty log offset due to some condition where KafkaProducer#flush are not called.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)