-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add log_start_offset
to message protocol parsing
#2020
Add log_start_offset
to message protocol parsing
#2020
Conversation
…all but the zstd related stuff)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few things...
log_start_offset
to message protocol parsing
I'd like @dpkp and @tvoinarovskyi to take a look as well, particularly at the error handling bit. |
@gabriel-tincu Great job on this, really appreciate your contribution. |
32840cb
to
aaf61ff
Compare
Nice! LGTM |
@jeffwidman Code looks good, but the current CI does not actually run 2.1 tests as API version checks are not up to date with the latest brokers. I will do a fix in separate PR, don't think it's a blocker. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great other than can you please add one inline comment for the _
... once that's done I'll happily merge.
…nse for future reference
Thanks! |
This is in preparation for adding `zstd` support.
As mentioned in the commit, these need to come all together, as the future code also implements logic that will unpack depending on version. The other PR would then be the ZSTD code itself
This change is