KAFKA-17322: Document required header versions in Protocol Guide#16867
Merged
jlprat merged 1 commit intoapache:trunkfrom Sep 16, 2024
Merged
KAFKA-17322: Document required header versions in Protocol Guide#16867jlprat merged 1 commit intoapache:trunkfrom
jlprat merged 1 commit intoapache:trunkfrom
Conversation
ivanyu
force-pushed
the
update-doc-request-response-headers
branch
from
af9c58b to
b2831e1
Compare
ivanyu
changed the title
3 tasks
Contributor
|
I ran the tests locally and they ran successfully. |
jlprat
approved these changes
Sep 16, 2024
tedyu
pushed a commit
to tedyu/kafka
that referenced
this pull request
Jan 6, 2025
…che#16867) Reviewers: Josep Prat <josep.prat@aiven.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)