apache / apache/iggy

Kafka gateway: Kafka DeleteRecords — trim topic to offset via Iggy retention

Open
#3,547 0 comments 0 reactions 0 assignees View on GitHub
gateways
Dominant language
Rust
Stars
4.9k
Forks
432
Avg merge
2d 10h
Merged PRs (30d)
174

Description

Part of #3560.

## Summary

Implement **DeleteRecords (21)** — trim topic/log to a specific offset, mapped to Iggy retention or explicit delete where supported.

## Depends on

- #3546 — DeleteTopics / admin foundation

## Scope

- [ ] Decode DeleteRecords request
- [ ] Map to Iggy retention trim or document limitation
- [ ] Per-partition low watermark in response
- [ ] Test: delete records before offset X; Fetch cannot read deleted range

## Acceptance criteria

- [ ] Behavior documented if Iggy cannot trim arbitrarily (partial support OK with clear errors)

## References

- Rollout plan: https://github.com/apache/iggy/discussions/3253#discussioncomment-17181030

Contributor guide

Open the contributing guide

Research direction

Start with the Kafka gateway's DeleteRecords (21) request handling and the Iggy retention or explicit-delete support, using the DeleteTopics/admin foundation from #3546 as context. Verify per-partition low-watermark responses and the behavior of Fetch after records before offset X are removed; document clear errors where arbitrary trimming is unsupported.

Written by the indexing model from the issue text.

Assessment

Tech stack
kafka, rust
Domain
api, distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.