Skip to content

KAFKA-3361: Initial protocol documentation page and generation#970

Closed
granthenke wants to merge 2 commits into
apache:trunkfrom
granthenke:protocol-doc-wip
Closed

KAFKA-3361: Initial protocol documentation page and generation#970
granthenke wants to merge 2 commits into
apache:trunkfrom
granthenke:protocol-doc-wip

Conversation

@granthenke
Copy link
Copy Markdown
Member

  • Moves all generated docs under /docs/generated
  • Generates docs for Protocol, Errors, and ApiKeys
  • Adds new protocol.html page

@jkreps
Copy link
Copy Markdown
Contributor

jkreps commented Feb 25, 2016

This is a super cool idea.

@christian-posta
Copy link
Copy Markdown
Contributor

This is great. Where's the tool you used to generate this? Can it do markdown?

Would love to work on converting the Kafka main-page docs to gitbook.com format https://www.gitbook.com

@granthenke
Copy link
Copy Markdown
Member Author

@christian-posta No tool was used. All the code used to generate this is in this pull request. Just some hacked together code to build the output.

- Moves all generated docs under /docs/generated
- Generates docs for Protocol, Errors, and ApiKeys
- Adds new protocol.html page
@granthenke
Copy link
Copy Markdown
Member Author

Below was my original WIP message:

Please see the email with the subject "Protocol Documentation WIP" in the Kafka dev mailing list for context on this PR. Do not review this for merge in its current state.

Here are links for the generated output:

I have updated the patch to be a "real" patch. The protocol docs still need some work. But that work is tracked by the umbrella jira here: KAFKA-3360.

@granthenke granthenke changed the title WIP: Protocol Documentation Generation KAFKA-3361: Initial protocol documentation page and generation Mar 9, 2016
@granthenke
Copy link
Copy Markdown
Member Author

@ewencp Ping for review. Thoughts on how this should link into the main docs?

@gwenshap
Copy link
Copy Markdown
Contributor

I agree that this should be a separate page (until we break down our documentation).

How about: Add a link to the side-bar (top.html) that will point to this page directly?

Comment thread docs/protocol.html Outdated
@@ -0,0 +1,163 @@
<h3><a id="protocol" href="#protocol">Kafka Wire Protocol</a></h3>

<p>This document covers the protocol implemented in Kafka 0.8 and beyond. It is meant to give a readable guide to the protocol that covers the available requests, their binary format, and the proper way to make use of them to implement a client. This document assumes you understand the basic design and terminology described <a href="https://kafka.apache.org/documentation.html#design">here</a></p>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Since this page is now in the version control and generated, I'm not sure this makes sense... we'll have a separate generated doc with each release, documenting the protocol for current version.

@granthenke
Copy link
Copy Markdown
Member Author

@gwenshap Good idea. The side-bar is probably the best place. I can send a PR to the site repo after this gets in.

I updated the PR to remove the version.

@gwenshap
Copy link
Copy Markdown
Contributor

LGTM (both the code and the plan).

Also, we want to publish the protocol for 0.9 too, right? So we'll want to cherrypick this to the 0.9 branch.

@asfgit asfgit closed this in f0a4125 Mar 10, 2016
@gwenshap
Copy link
Copy Markdown
Contributor

Sorry, this doesn't cherrypick cleanly.
So, either we do this for 0.10.0 and up (in which case your site-repo PR will have the honor of creating the 0.10 docs directory), or you can do a separate PR for 0.9.0. Either way is fine.

@granthenke
Copy link
Copy Markdown
Member Author

@gwenshap I noticed a copy/paste bug while backporting. That fix for trunk is PR #1037. The backport PR for the 0.9 branch contains the fix already. Its PR #1038.

efeg added a commit to efeg/kafka that referenced this pull request Jan 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants