Can we remove Elasticsearch dependency from Zeebe?

Using zeebe 8.2 community version, I have configured Hazelcast exporter to Zeebe brokers and deployed in k8s environment. But when I check the logs,I can see elasticsearch exporter errors into zeebe brokers. Is there any way to get rid of elasticserach errors.?
Also using zeeqs to get data from Hazelcast exporter. But seems data is not getting transferred from zeebe brokers to hazelcast.

Hi @renuka_choudhari, welcome to the forums! It sounds like the exporters aren’t configured quite right and Zeebe is still trying to use Elasticsearch instead of Hazelcast, which would also explain why you’re not seeing the expected data in Hazelcast. Can you share your configuration (either Docker or Helm), and what errors you are seeing in the logs?

Thanks nathan.loding for quick reply.
Yes, the elasticsearch config data was still there, that is why hazelcast is not working properly as exporter.
Removed elasticsearch related configuration settings manually and it is working fine now. Broker is taking Hazelcast as exporter.
But getting error in hazelcast, while importing the records from Zeebe Broker.

ERROR 1 — [pool-1-thread-1] i.z.h.connect.java.ZeebeHazelcast : Failed to deserialize Protobuf message at sequence ‘105151’