You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Herb,
I have no experience using azure or eventhub in general, but checked your repo and it looks good I'd say.
Except one thing maybe: getSASLConfig() sets the Partitioner like
If the processor uses a different one, it will mess up the state. But at least there should be a log stating that the message was received in the first place, so it won't be the issue. It's also a good idea to use goka.DefaultConfig() instead of creating a new one from scratch using sarama.NewConfig(), to avoid missing some defaults that goka sets.
The spin in consumerGroup.Consume is intended, because internally this executes the rebalance-loop on g, so that shouldn't be the issue.
The log setup generation... actually indicates that everything is correct. Rather looks like there is no message in the stream for some reason.
Btw, the code says it's 8 partitions, but the log say it's 10. But that shouldn't be an issue. If input and table aren't co-partitioned, the processor will fail to restart anyway.
Sorry that's all I could see at the moment. Let me know if you need further assistance or I can help in any way.
Had anyone gotten this to work with azure eventhub.
I am using the simple example modified to use SASL.
created the 2 topics by hand on azure and am able to emit an event but the consumer isn't consuming.
topics
each with 10 partitions
azure setup
it just spins in the following call.
I reset my azure keys so the ones in my test repo wouldn't work. Maybe you can see an obvious processor setup problem.
example
The text was updated successfully, but these errors were encountered: