Gitanjali You can achieve your usecase using GroupByN/GroupByFields snap. Check below example.
Jens,
I just verified that our instructions work as described for Confluent Cloud accounts:
What do you mean that “it works with the REST API endpoint”? Our Kafka snaps do not work with the Confluent REST Proxy, which is a low-performance HTTP protocol adapter layer relative to the high-performance binary protocol used by the Kafka brokers. Our account requires the host:port value shown as the Bootstrap server in the Confluent Cloud Cluster settings:
Your account screenshot is showing several things misconfigured:
Security Protocol must be SASL_SSL, not SASL_PLAINTEXT.SASL Mechanism must be PLAIN (you have this part correct).SASL Username or Key and SASL Password or Key must be set to the Key and Secret values obtained when creating the API key in Confluent Kafka. No re-encoding of anything is necessary.Hi @ptaylor ,
First, sorry for my explanation, I forgot to mention I also tested it with a rest post snap for the rest api endpoint.
For the configuration, then it seems that is has to be on our snaplex side to connect to confluent I suppose, because with implementing the configuration like you showed it still gets a timeout connection. But now I can investigate further.
Thank you for your time.
Regards
Jens
