[kafka] branch trunk updated: Minor: replace .kafka with .log in implementation documentation (#12401)

[sh...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

showuon pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 74a18bafae Minor: replace .kafka with .log in implementation documentation (#12401)
74a18bafae is described below

commit 74a18bafaebbe9ccf81b2bacade442cdd3728537
Author: Federico Valeri <fe...@gmail.com>
AuthorDate: Wed Jul 20 12:11:51 2022 +0200

    Minor: replace .kafka with .log in implementation documentation (#12401)
    
    replace .kafka with .log in implementation documentation
    
    Reviewers: Luke Chen <sh...@gmail.com>, Liam Clarke-Hutchinson <li...@steelsky.co.nz>
---
 docs/images/kafka_log.png | Bin 134321 -> 114789 bytes
 docs/implementation.html  |   2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/images/kafka_log.png b/docs/images/kafka_log.png
index 75abd96bab..6658b3f43c 100644
Binary files a/docs/images/kafka_log.png and b/docs/images/kafka_log.png differ
diff --git a/docs/implementation.html b/docs/implementation.html
index 773d510680..11cf365750 100644
--- a/docs/implementation.html
+++ b/docs/implementation.html
@@ -164,7 +164,7 @@ message => crc magic_byte attributes timestamp key value
 
     <h3 class="anchor-heading"><a id="log" class="anchor-link"></a><a href="#log">5.4 Log</a></h3>
     <p>
-    A log for a topic named "my_topic" with two partitions consists of two directories (namely <code>my_topic_0</code> and <code>my_topic_1</code>) populated with data files containing the messages for that topic. The format of the log files is a sequence of "log entries""; each log entry is a 4 byte integer <i>N</i> storing the message length which is followed by the <i>N</i> message bytes. Each message is uniquely identified by a 64-bit integer <i>offset</i> giving the byte position of [...]
+    A log for a topic named "my-topic" with two partitions consists of two directories (namely <code>my-topic-0</code> and <code>my-topic-1</code>) populated with data files containing the messages for that topic. The format of the log files is a sequence of "log entries"; each log entry is a 4 byte integer <i>N</i> storing the message length which is followed by the <i>N</i> message bytes. Each message is uniquely identified by a 64-bit integer <i>offset</i> giving the byte position of  [...]
     </p>
     <p>
     The exact binary format for records is versioned and maintained as a standard interface so record batches can be transferred between producer, broker, and client without recopying or conversion when desirable. The previous section included details about the on-disk format of records.