mimaison commented on code in PR #17813:
URL: https://github.com/apache/kafka/pull/17813#discussion_r1842086092
##########
docs/ops.html:
##########
@@ -1213,41 +1213,7 @@ <h4 class="anchor-heading"><a id="multitenancy-more"
class="anchor-link"></a><a
<strong>Data contracts:</strong> You may need to define data contracts
between the producers and the consumers of data in a cluster, using event
schemas. This ensures that events written to Kafka can always be read properly
again, and prevents malformed or corrupt events being written. The best way to
achieve this is to deploy a so-called schema registry alongside the cluster.
(Kafka does not include a schema registry, but there are third-party
implementations available.) A schema registry manages the event schemas and
maps the schemas to topics, so that producers know which topics are accepting
which types (schemas) of events, and consumers know how to read and parse
events in a topic. Some registry implementations provide further functionality,
such as schema evolution, storing a history of all schemas, and schema
compatibility settings.
</p>
-
- <h3 class="anchor-heading"><a id="config" class="anchor-link"></a><a
href="#config">6.5 Kafka Configuration</a></h3>
Review Comment:
This section was pretty much useless, it did not provide the important
configuration names and the "example production server configuration" was
really incomplete.
--
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]
