Keith Wall
Keith Wall
As this is known to affect only kaf (sarama based), not a priority for 0.5.0. Probably not high priority for 0.6.0.
> Kaf is sending the unframed SASL authenticate. There's no way to override that behaviour currently. [birdayz/[email protected]:kaf:enable-sasl-v1](https://github.com/birdayz/kaf/compare/master...k-wall:kaf:enable-sasl-v1) (edit: I've opened a PR to add the ability) kaf 0.2.7 is released...
My gut feel is we can defer this until post 0.5.0
@k-wall is this a duplicate?
I noticed that HashoCorp Vault does timestamp key version at creation time. We could consider using that to detect delete/recreate using the same name.
@k-wall assigned to myself - I want to improve the problem statement.
@gracegrimwood go for it! We need to decide how best to split things up. My embryonic idea (which you should feel free to ignore) was to have separate Multi Tenant...
Closed as duplicate
I'm not using Sarama much right now. Have you examined the logs from the Broker side?
hello, thanks for raising the issue. I took a quick look today. I find that compression.type gzip and lz4 are working, both zstd and snappy fail with a JNI error....