redpanda-data / redpanda-data/redpanda
Centralize/unify internal topic checks
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Today, we have a litany of internal topic checks scattered throughout the codebase. Just as an example, see this search: https://github.com/search?q=repo%3Aredpanda-data%2Fredpanda%20(is_internal%20OR%20is_user_topic)&type=code
We should centralize and unify the checks where that makes sense, so if adding new internal topics (or any "special" topics like audit logging) we don't miss updating somewhere.
JIRA Link: CORE-1590
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
Start with the linked repository search for is_internal and is_user_topic, then map the scattered checks and the special-topic cases they cover. Determine which checks can share a central definition and identify the affected call sites; done means internal and special topics are handled consistently without missed updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- stream-processing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100