hubcio opened a new issue, #2722:
URL: https://github.com/apache/iggy/issues/2722
The `delete_segments` operation exists in the binary protocol, CLI, and MCP
but has no server-side HTTP handler. The HTTP SDK client
(`core/sdk/src/http/segments.rs`) already sends the request — it gets a 404.
`core/server/src/http/segments.rs` - an HTTP handler + route registration in
`http_server.rs`, following the same pattern as `partitions.rs`.
All building blocks exist: shard logic (`delete_segments_base`), permission
check (`perm_delete_segments`), command (`DeleteSegments`).
As for testing, just enhance `system_scenario.rs` - it's already called for
http - delete segments at the end and check the segments count before and after.
Update `api.http` for server.
```
### Delete segments
DELETE {{url}}/streams/1/topics/1/partitions/1?segments_count=3
Authorization: Bearer {{access_token}}
Path params: stream_id, topic_id, partition_id. Query param:
segments_count.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
