Re: EXT: Re: Flink cassandra connector performance issue

2022-03-25 Thread Etienne Chauchot
lthcare) a écrit : Absolutely . Understood! We shall do.😊 -Original Message- From: Chesnay Schepler Sent: 22 March 2022 15:52 To:dev@flink.apache.org; Martijn Visser; Marco Zühlke Cc: R, Aromal (GE Healthcare, consultant); Nellimarla, Aswini (GE Healthcare) Subject: EXT: Re: Flink

RE: EXT: Re: Flink cassandra connector performance issue

2022-03-22 Thread Ghiya, Jay (GE Healthcare)
Absolutely . Understood! We shall do.😊 -Original Message- From: Chesnay Schepler Sent: 22 March 2022 15:52 To: dev@flink.apache.org; Martijn Visser ; Marco Zühlke Cc: R, Aromal (GE Healthcare, consultant) ; Nellimarla, Aswini (GE Healthcare) Subject: EXT: Re: Flink cassandra

Re: Flink cassandra connector performance issue

2022-03-22 Thread Chesnay Schepler
I'd be quite curious on what the analysis that the mapper isn't re-used is based on. A given CassandraPojoSink instance has been re-using the same mapper since it was added in 1.1: https://github.com/apache/flink/blob/release-1.1/flink-streaming-connectors/flink-connector-cassandra/src/main/java

Re: Flink cassandra connector performance issue

2022-03-22 Thread Martijn Visser
Hi Jay, Thanks for reaching out! As just mentioned in the ticket, the Cassandra connector hasn't been actively maintained in the last couple months/years. It would be great if there would be more contributors who could help out with this. See also my previous request [1] on the Dev mailing list, w