This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/avro.git
The following commit(s) were added to refs/heads/master by this push:
new 66fa34b14 Fix wrong heading level of Single-object encoding in the doc
(#2484)
66fa34b14 is described below
commit 66fa34b141f0c0cf6979b969aca8a114a50bb652
Author: Kousuke Saruta <[email protected]>
AuthorDate: Tue Sep 5 16:07:52 2023 +0900
Fix wrong heading level of Single-object encoding in the doc (#2484)
---
doc/content/en/docs/++version++/Specification/_index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/content/en/docs/++version++/Specification/_index.md
b/doc/content/en/docs/++version++/Specification/_index.md
index 30494e073..7cc5a1754 100755
--- a/doc/content/en/docs/++version++/Specification/_index.md
+++ b/doc/content/en/docs/++version++/Specification/_index.md
@@ -393,12 +393,12 @@ For example, the union schema `["null","string","Foo"]`,
where Foo is a record n
Note that the original schema is still required to correctly process
JSON-encoded data. For example, the JSON encoding does not distinguish between
_int_ and _long_, _float_ and _double_, records and maps, enums and strings,
etc.
-#### Single-object encoding
+### Single-object encoding
In some situations a single Avro serialized object is to be stored for a
longer period of time. One very common example is storing Avro records for
several weeks in an [Apache Kafka](https://kafka.apache.org/) topic.
In the period after a schema change this persistence system will contain
records that have been written with different schemas. So the need arises to
know which schema was used to write a record to support schema evolution
correctly. In most cases the schema itself is too large to include in the
message, so this binary wrapper format supports the use case more effectively.
-##### Single object encoding specification
+#### Single object encoding specification
Single Avro objects are encoded as follows:
1. A two-byte marker, `C3 01`, to show that the message is Avro and uses this
single-record format (version 1).
