krishvishal opened a new issue, #4408: URL: https://github.com/apache/iggy/issues/4408
### Bug description The REST API cannot name a consumer kind. `Consumer.kind` is `#[serde(skip)]`, and the server builds a plain consumer (`Consumer::new`) from an HTTP request. An HTTP client can pass `Consumer::group(..)` to `store_consumer_offset`, `get_consumer_offset`, `delete_consumer_offset` or `poll_messages`. The call then acts on the plain consumer with the group's id, and no error tells the caller. Join and leave already return `FeatureUnavailable` over HTTP, so a group cannot work there. Expected: the HTTP client refuses every kind except `ConsumerKind::Consumer` with `FeatureUnavailable`, as #4392 does for `ConsumerKind::ExternalGroup` (`refuse_external_group` in `core/sdk/src/http/consumer_offsets.rs`). This changes behavior for an HTTP caller that passes a group today. Raised in the review of #4392. ### Affected area / component Rust SDK, Iggy server ### Reproduction 1. Build an `IggyClient` with the HTTP transport. 2. Send 10 messages to partition 0 of a topic. 3. Store offset 5 with `Consumer::group(Identifier::numeric(1)?)` on partition 0. 4. Read the offset with `Consumer::new(Identifier::numeric(1)?)`. It returns 5. -- 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]
