From f9b31ae9a3be6b9d8a3e6b9df98e58c046d3c672 Mon Sep 17 00:00:00 2001
From: Shih-Yuan Lin <shmily7829@gmail.com>
Date: Wed, 30 Apr 2025 00:46:03 +0800
Subject: [PATCH 1/2] docs: Clarify that index.interval.bytes affects both
 offset and time index entries

---
 40/generated/topic_config.html | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/40/generated/topic_config.html b/40/generated/topic_config.html
index 6de2732c4..aa9ca659f 100644
--- a/40/generated/topic_config.html
+++ b/40/generated/topic_config.html
@@ -111,7 +111,12 @@ <h4><a id="follower.replication.throttled.replicas"></a><a id="topicconfigs_foll
 </li>
 <li>
 <h4><a id="index.interval.bytes"></a><a id="topicconfigs_index.interval.bytes" href="#topicconfigs_index.interval.bytes">index.interval.bytes</a></h4>
-<p>This setting controls how frequently Kafka adds an index entry to its offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.</p>
+<p>This setting controls how frequently Kafka adds entries to its offset index and, conditionally, to its time index. After appending a batch of messages, if the total bytes written since the last index entry exceed this value, Kafka will:</p>
+<ul>
+<li>Add an entry to the offset index for the batch's last offset.</li>
+<li>Attempt to add an entry to the time index if the batch's maximum timestamp is greater than the last indexed timestamp.</li>
+</ul>
+<p>The default setting ensures that we index a message roughly every 4096 bytes. More frequent indexing allows reads to jump closer to the exact position in the log but results in larger index files. You probably don't need to change this.</p>
 <table><tbody>
 <tr><th>Type:</th><td>int</td></tr>
 <tr><th>Default:</th><td>4096 (4 kibibytes)</td></tr>

From 46ea94175992aa594477a170d7589b922d1b7db7 Mon Sep 17 00:00:00 2001
From: Shih-Yuan Lin <shmily7829@gmail.com>
Date: Thu, 8 May 2025 23:29:57 +0800
Subject: [PATCH 2/2] KAFKA-19209: Improve clarity and readability of
 index.interval.bytes description

---
 40/generated/topic_config.html | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/40/generated/topic_config.html b/40/generated/topic_config.html
index aa9ca659f..eeeef1776 100644
--- a/40/generated/topic_config.html
+++ b/40/generated/topic_config.html
@@ -111,12 +111,7 @@ <h4><a id="follower.replication.throttled.replicas"></a><a id="topicconfigs_foll
 </li>
 <li>
 <h4><a id="index.interval.bytes"></a><a id="topicconfigs_index.interval.bytes" href="#topicconfigs_index.interval.bytes">index.interval.bytes</a></h4>
-<p>This setting controls how frequently Kafka adds entries to its offset index and, conditionally, to its time index. After appending a batch of messages, if the total bytes written since the last index entry exceed this value, Kafka will:</p>
-<ul>
-<li>Add an entry to the offset index for the batch's last offset.</li>
-<li>Attempt to add an entry to the time index if the batch's maximum timestamp is greater than the last indexed timestamp.</li>
-</ul>
-<p>The default setting ensures that we index a message roughly every 4096 bytes. More frequent indexing allows reads to jump closer to the exact position in the log but results in larger index files. You probably don't need to change this.</p>
+<p>This setting controls how frequently Kafka adds entries to its offset index and, conditionally, to its time index. The default setting ensures that we index a message roughly every 4096 bytes. More frequent indexing allows reads to jump closer to the exact position in the log but results in larger index files. You probably don't need to change this.<p> Note: the time index will be inserted only when the timestamp is greater than the last indexed timestamp.</p></p>
 <table><tbody>
 <tr><th>Type:</th><td>int</td></tr>
 <tr><th>Default:</th><td>4096 (4 kibibytes)</td></tr>