[
https://issues.apache.org/jira/browse/BAHIR-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787308#comment-16787308
]
ASF subversion and git services commented on BAHIR-180:
-------------------------------------------------------
Commit 603d4e0435543a5e57028a7ce51a1fcc2c705ff5 in bahir-flink's branch
refs/heads/master from eskabetxe
[ https://gitbox.apache.org/repos/asf?p=bahir-flink.git;h=603d4e0 ]
[BAHIR-180] Improve eventual consistence for Kudu connector
Closes #40
> kudu connector improve real-time data performance
> -------------------------------------------------
>
> Key: BAHIR-180
> URL: https://issues.apache.org/jira/browse/BAHIR-180
> Project: Bahir
> Issue Type: Improvement
> Components: Flink Streaming Connectors
> Affects Versions: Flink-Next
> Reporter: mei jie
> Assignee: Joao Boto
> Priority: Major
> Fix For: Flink-Next
>
>
> kudu connector has poof performance to write real-time data with either
> strong consistency or eventual consistency. at my environment(3server with
> 250G memory, 5 disk, and the parallelism of flink is 60), the speed is about
> 20,000/s.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
