Skip to content

chore: support V5 ListOffsets#3308

Merged
dnwe merged 1 commit intomainfrom
dnwe/v5-listoffsets
Sep 25, 2025
Merged

chore: support V5 ListOffsets#3308
dnwe merged 1 commit intomainfrom
dnwe/v5-listoffsets

Conversation

@dnwe
Copy link
Copy Markdown
Collaborator

@dnwe dnwe commented Sep 25, 2025

V5 adds a new error code, OFFSET_NOT_AVAILABLE, but is otherwise identical to V4

V5 adds a new error code, OFFSET_NOT_AVAILABLE, but is otherwise identical to V4

Signed-off-by: Dominic Evans <[email protected]>
@dnwe dnwe force-pushed the dnwe/v5-listoffsets branch from df40ff0 to 68e2da0 Compare September 25, 2025 14:19
Base automatically changed from dnwe/request-test to main September 25, 2025 18:15
@dnwe dnwe merged commit 68e2da0 into main Sep 25, 2025
20 of 21 checks passed
@dnwe dnwe deleted the dnwe/v5-listoffsets branch September 25, 2025 18:15
blocks map[string]map[int32]*offsetRequestBlock
}

func NewOffsetRequest(version KafkaVersion) *OffsetRequest {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we want to export this? (I suspect yes, because we export a lot of request constructors).

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah at the moment we export all the protocol, that may change when we move to a v2 api, but for now we keep them the same

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I think mentioned elsewhere, for a v2 we probably want to split up the protocol from the API. That’s what I also did with sftp v2.

Building a transparent shim of the protocol, and then the complex API hiding implementation details really simplified a lot of the exposed API, while keeping the protocol open and standardized as well.

@dnwe dnwe added the feat label Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants