redpanda-data / redpanda-data/redpanda
change default cleanup policy for topic in docker compose
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Who is this for and what problem do they have today?
I am using redpanda in docker compose as mq and schema registry. But I noticed redpanda does log compaction and crash my test cases, I want to disable it.
My team relies on kafka producer and it creates topics automatically by inserting data. I want to change the default behavior for all topics on the broker in the docker compose file.
What are the success criteria?
as described above.
I wonder if you can expose an env variable to change the behavior
Why is solving this problem impactful?
more user friendly
Additional notes
Na
JIRA Link: CORE-1332
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named in the issue. Start by locating the Docker Compose configuration and the broker's topic cleanup-policy settings, then determine how an environment variable could set the default for automatically created topics. Done means the Compose setup lets users disable log compaction for those topics through the configurable default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, kafka
- Domain
- devops, stream-processing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100