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, which also contains an overview of the current issues with the connector.
I'm also including @Marco Zühlke <mzueh...@apache.org> who previously volunteered to help out with the connector. It would be great if you could all help out :) Best regards, Martijn Visser https://twitter.com/MartijnVisser82 [1] https://lists.apache.org/thread/1qokt5tp8dcp58dmshbwjc43ssbm1vvk On Tue, 22 Mar 2022 at 07:33, Ghiya, Jay (GE Healthcare) <jay.gh...@ge.com> wrote: > Hi @dev@flink.apache.org<mailto:dev@flink.apache.org>, > > Greetings from gehc. > > This is regarding flink Cassandra connector implementation that could be > causing the performance issue that we are facing. > > The summary of the error is > > "Insertions into scylla might be suffering. Expect performance problems > unless this is resolved." > > Upon doing initial analysis we figured out - "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 > > Can we take a look at this? Also can we help fix this ? @R, Aromal (GE > Healthcare, consultant)<mailto:aroma...@ge.com> Is our lead dev on this. > > Here is the jira issue on the same - > https://issues.apache.org/jira/browse/FLINK-26793 > > -Jay > >
