[jira] [Comment Edited] (FLINK-26793) Flink Cassandra connector performance issue

["Etienne Chauchot (Jira)" <ji...@apache.org>]

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

Etienne Chauchot edited comment on FLINK-26793 at 3/22/22, 10:37 AM:
---------------------------------------------------------------------

I just saw this ticket. I think solving this perf problem now even if we plan to migrate this connector to the new source/sink api makes sense. [~martijnvisser] I can take care of it if you agree


was (Author: echauchot):
I just saw this ticket. I think solving this perf problem now even if we plan to migrate this connector to the new source/sink api makes sense. [~martijnvisser] I can take car of it if you agree

> Flink Cassandra connector performance issue 
> --------------------------------------------
>
>                 Key: FLINK-26793
>                 URL: https://issues.apache.org/jira/browse/FLINK-26793
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Cassandra
>    Affects Versions: 1.14.4
>            Reporter: Jay Ghiya
>            Priority: Major
>
> A warning is observed during long runs of flink job stating “Insertions into scylla might be suffering. Expect performance problems unless this is resolved.”
> Upon initial analysis - “flink cassandra connector is not keeping instance of mapping manager that is used to convert a pojo to cassandra row. Ideally the mapping manager should have the same life time as cluster and session objects which are also created once when the driver is initialized”
> Reference: https://stackoverflow.com/questions/59203418/cassandra-java-driver-warning



--
This message was sent by Atlassian Jira
(v8.20.1#820001)