We will only share developer content and updates, including notifications when new content is added. We will never send you sales emails. 🙂 By subscribing, you understand we will process your personal information in accordance with our Privacy Statement.
Hello everyone! This week we have a long list of resources for you to kick off your autumn (or Spring, for our Southern Hemisphere readers!) Optimize throughput with a blog post on how to tune your Kafka Connect source connectors, spin up a local Kafka deployment with a new quick start, get an in-depth introduction to Flink SQL, and much more. Happy learning!
Today we're going to talk about the different ways to configure kcat.
First of all, one of the reasons that kcat is so useful is that any piece of librdkafka configuration is available to it via the -X flag:
kcat -b broker_name -t topic_name -X client.id=rdkafka
If you've got a lot of configuration and don't want to be passing them in every time you run the command, you can feed kcat a config file:
kcat -b broker_name -t topic_name -X client -F ./path/to/config_file
If there's no config file set, kcat will consult $KCAT_CONFIG or, if you like, you can set configuration in a ~/.config/kcat.conf file to avoid passing in any config values at all.
We hope you enjoyed our curated assortment of resources! If you’d like to provide feedback, suggest ideas for content you’d like to see, or you want to submit your own resource for consideration, send us an email at email@example.com!
If you’re viewing this newsletter online, know that we appreciate your readership and that you can get this newsletter delivered directly to your inbox by scrolling down to the bottom of the page and filling out the form.
P.S. If you want to learn more about Kafka or Confluent Cloud, visit our developer site at Confluent Developer.