Christopher Mason

I ran into this one recently, but for producing, with the opposite fix: reducing the max message size. ``` %7|1615433222.151|PRODUCE|rdkafka#producer-1| [thrd:kafka:9092/1]: kafka:9092/1: patient [0]: No more space in current MessageSet...

This has been implemented over in https://github.com/edenhill/kafkacat/pull/295. Check it out!

It would be wonderful if there was a way we could feed a JSON stream from `kafkacat -C -J` into `kafkacat -P -J` and have it produce exactly the same...

@Tommmster check out https://github.com/edenhill/kcat/pull/295

This would be really helpful to copy messages between topics or brokers! Nice work! Another feature that would be amazingly helpful in this scenario would be to preserve headers. `-J`...

Hi @qiujiangkun I've implemented the header production from JSON over in this branch: https://github.com/masoncj/kafkacat/tree/producer_json_headers However, I'm seeing an issue with this PR (absent any of my code above) where the...

@qiujiangkun, I was able to identify and fix the source of the corruption I was seeing above. It didn't have anything to do with jq or line breaks (`jq -c`...

@edenhill this is proving really useful for me in copying data between topics/servers. For example: ``` ./kafkacat -C -F ~/.kafka-dev -o beginning -e -t patient -J | ./kafkacat -P -b...

Just came here to say I ran into this recently in a single broker setup. Is there a suggested path forward to avoid this error where topic creation happens before...

Just as an aside, I'm also noticing this same hotspot in code that is very insert intensive.