root
/
kafka
mirror of https://github.com/apache/kafka.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity

MINOR: Addressed minor typos in READMEs. (#10905) 

Reviewers: Chia-Ping Tsai <chia7712@gmail.com>
This commit is contained in:
Satish Duggana 2021-06-19 21:28:57 +05:30 committed by GitHub
parent 01c2345658
commit d3709dafbe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
clients/src/main/resources/common/message/README.md
View File

@ -135,7 +135,7 @@ version.
You can remove support for a tagged field from a specific version of a message,
but you can't reuse a tag once it has been used for something else. Once tags
have been used for something, they can't be used for anything else, without
breaking compatibilty.
breaking compatibility.
Note that tagged fields can only be added to "flexible" message versions.
@ -145,7 +145,7 @@ Kafka serialization has been improved over time to be more flexible and
efficient. Message versions that contain these improvements are referred to as
"flexible versions."
In flexible verisons, variable-length fields such as strings, arrays, and bytes
In flexible versions, variable-length fields such as strings, arrays, and bytes
fields are serialized in a more efficient way that saves space. The new
serialization types start with compact. For example COMPACT_STRING is a more
efficient form of STRING.
@ -190,7 +190,7 @@ been set:
* Array fields default to empty.
You can specify "null" as a default value for a string field by specifing the
You can specify "null" as a default value for a string field by specifying the
literal string "null". Note that you can only specify null as a default if all
versions of the field are nullable.

4
core/src/test/java/kafka/test/junit/README.md
View File

@ -135,5 +135,5 @@ class SomeTestClass(helper: IntegrationTestHelper) {
# Gotchas
* Test methods annotated with JUnit's `@Test` will still be run, but no cluster will be started and no dependency
injection will happen. This is generally not what you want
* Even though ClusterConfig is accessible and mutable inside the test method, changing it will have no affect on the cluster
injection will happen. This is generally not what you want.
* Even though ClusterConfig is accessible and mutable inside the test method, changing it will have no effect on the cluster.