From 7272016cd2f2545e597a340d1909ff5b35c73006 Mon Sep 17 00:00:00 2001 From: ruinivist Date: Sun, 25 Jan 2026 02:26:36 +0000 Subject: [PATCH] chore: rename --- {01-broken-setup => 01-docker-setup}/docker-compose.yaml | 0 README.md | 6 ++++-- 2 files changed, 4 insertions(+), 2 deletions(-) rename {01-broken-setup => 01-docker-setup}/docker-compose.yaml (100%) diff --git a/01-broken-setup/docker-compose.yaml b/01-docker-setup/docker-compose.yaml similarity index 100% rename from 01-broken-setup/docker-compose.yaml rename to 01-docker-setup/docker-compose.yaml diff --git a/README.md b/README.md index b4505da..687badf 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,8 @@ learning kafka -# 01-broken-setup ( not actually broken ) +# 01-docker-setup -Take a look at 01-broken-setup. Ideally when you setup, you need to have a meta.properties file in the kafka-data ( /var/lib/kafka/data ) directory. This file is created when Kafka starts for the first time. +Take a look at 01-docker-setup. Ideally when you setup, you need to have a meta.properties file in the kafka-data ( /var/lib/kafka/data ) directory. This file is created when Kafka starts for the first time. ``` # @@ -50,3 +50,5 @@ If you run another producer, messages will be twice as fast and all "just works" If you create more consumers than paritions, the extra consumers will be idle. There is no scaling down of partitions, to decrease partitions, you need to create a new topic with less partitions and migrate data over. + +# 04-keys