(iggy) 02/04: fix(server): describe max topic size as a topic-wide cap

[hg...@apache.org]

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

hubcio pushed a commit to branch fix/docs-audit-core
in repository https://gitbox.apache.org/repos/asf/iggy.git

commit d6e3cb9ec1c6abec8ab4b15c727a55df4e824a52
Author: Hubert Gruszecki <h....@gmail.com>
AuthorDate: Sat Sep 12 20:04:35 2026 +0200

    fix(server): describe max topic size as a topic-wide cap
    
    The descriptor overstated retention by calling the topic-wide cap
    a per-partition limit. Match the cleaner's partitioned budget.
---
 core/server/src/responses.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/server/src/responses.rs b/core/server/src/responses.rs
index 7bca706e5..d963b0f38 100644
--- a/core/server/src/responses.rs
+++ b/core/server/src/responses.rs
@@ -1046,8 +1046,8 @@ fn topic_option_descriptors() -> Result<Vec<OptionDescriptor>, IggyError> {
             default_value: Bytes::copy_from_slice(
                 &iggy_common::DEFAULT_MAX_TOPIC_SIZE.to_le_bytes(),
             ),
-            description: "Per-partition sealed-segment size cap in bytes, or a byte-size string \
-                              (e.g. 1 GiB); finite values must be at least the segment size"
+            description: "Topic-wide sealed-segment size cap, split across all partitions, in bytes \
+                              or a byte-size string (e.g. 1 GiB); finite values must be at least the segment size"
                 .to_string(),
         },
         OptionDescriptor {