[
https://issues.apache.org/jira/browse/FLINK-26793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510717#comment-17510717
]
Etienne Chauchot commented on FLINK-26793:
------------------------------------------
[~bumblebee] splitting looks good to me. I guess migration to new API Jira
already exists. As I know the current code I could take care of the urgent perf
issue. If you need some details about the new API there is a talk from [~arvid]
that explains it:
[https://www.youtube.com/watch?v=LCMfbGv38u8&list=PLDX4T_cnKjD0J2LFr7yBk2aSS_o2l-7ue]
> 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)
