In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Cassandra 2.6.1

What is the connector configuration?

any

What is the captured database version and mode of depoyment?

DSE

What behaviour do you expect?

What behaviour do you see?

Getting:
```
2024-06-27 14:10:47,853 ERROR [io.deb.ser.ConnectorLifecycle] (pool-7-thread-1) Connector completed: success = 'false', message = 'java.lang.NullPointerException', error = 'java.lang.NullPointerException': java.lang.NullPointerException
at io.debezium.connector.common.BaseSourceTask.resetErrorHandlerRetriesIfNeeded(BaseSourceTask.java:340)
at io.debezium.connector.common.BaseSourceTask.poll(BaseSourceTask.java:284)
at io.debezium.embedded.async.AsyncEmbeddedEngine$PollRecords.doCall(AsyncEmbeddedEngine.java:1152)
at io.debezium.embedded.async.AsyncEmbeddedEngine$PollRecords.doCall(AsyncEmbeddedEngine.java:1136)
at io.debezium.embedded.async.RetryingCallable.call(RetryingCallable.java:47)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)```

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

<Your answer>

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

Implementation ideas (optional)

The root cause seems to be a change in:
DBZ-6236 Reset ErrorHandler retry counter on successful poll

The new code should take into account the case of a null coordinator, or alternatively we should add the coordinator class to Cassandra.

Looking at https://github.com/debezium/debezium-connector-cassandra/blob/e0f566e843a7500d8ca40e4629e594a5ba737a4b/core/src/main/java/io/debezium/connector/cassandra/AbstractConnectorTask.java#L77 in the Cassandra connector, it seems to return null for the Coordinator. Probably since there was no previous use of it.