You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Etienne Chauchot (Jira)" <ji...@apache.org> on 2022/05/06 08:09:00 UTC

[jira] [Commented] (FLINK-27457) CassandraOutputFormats should support flush

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

Etienne Chauchot commented on FLINK-27457:
------------------------------------------

[~chesnay] can you assign me this ticket as I addressed already it in [the cassandra upgrade PR|https://github.com/apache/flink/pull/19586] because this PR showed the need for a flush mechanism.

> CassandraOutputFormats should support flush
> -------------------------------------------
>
>                 Key: FLINK-27457
>                 URL: https://issues.apache.org/jira/browse/FLINK-27457
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Cassandra
>            Reporter: Etienne Chauchot
>            Priority: Major
>
> When migrating to Cassandra 4.x in [this PR|https://github.com/apache/flink/pull/19586] a race condition in the tests between the asynchronous writes and the junit assertions was uncovered. So it was decided to introduce the flush mechanism to asynchronous writes in the Cassandra output formats similarly to what was done in Cassandra sinks.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)