redpanda-data / redpanda-data/redpanda
cloud_storage: topic based status/usage API
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/redpanda-data/redpanda/issues/7920 introduced a partition based API cloud storage status API: v1/cloud_storage/status/{topic}/{partition}. We should that with a topic based API that does the same thing.
The challenge is keeping the number of internal RPCs reasonable (think of topics with thousands of partitions). Some caching may have to be introduced for this.
JIRA Link: CORE-1335
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 by reviewing issue #7920 and the existing partition-based endpoint, v1/cloud_storage/status/{topic}/{partition}. Define the corresponding topic-based status/usage API and determine how to keep internal RPCs reasonable for topics with thousands of partitions, potentially using caching; done means the topic-level API provides the same status information without excessive RPCs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100