wank125 opened a new issue, #4190:
URL: https://github.com/apache/doris-website/issues/4190

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris-website/issues?q=is%3Aissue) and found 
no similar issues.
   
   ### What happened
   
   The STRING type doc page 
(`docs/sql-manual/basic-element/sql-data-types/string-type/STRING.md`, and its 
versioned copies) currently says:
   
   > "A variable length string. Default support is 1048576 bytes (1M), 
adjustable up to 2147483643 bytes (2G) ..."
   
   However the BE default was changed from 1MB to **10MB** in 
apache/doris#51121 (2025-05-26):
   
   ```cpp
   // be/src/common/config.cpp (current master)
   DEFINE_Int32(string_type_length_soft_limit_bytes, "10485760");
   ```
   
   We verified this empirically on a 4.1.3 cluster: STRING values of ~3.3MB are 
accepted, stored and read back byte-identical (md5-checked against the source 
database) without any config override — consistent with a 10MB soft limit, not 
1MB.
   
   ### What you expected to happen
   
   The doc should state the current default (10485760 bytes / 10MB, effective 
since #51121), keeping the note that it is adjustable via 
`string_type_length_soft_limit_bytes` and capped at 2147483643 bytes (2G). The 
versioned docs for releases that still default to 1MB can stay as they are if 
the per-version value is tracked, but the `docs/` (latest) copy should reflect 
10MB.
   
   ### Anything else
   
   - Hard limit constant `ScalarType.MAX_STRING_LENGTH = 0x7fffffff - 4` 
(fe/fe-common/.../ScalarType.java) matches the documented 2G cap — no issue 
there.
   - Happy to submit the one-line doc fix PR if maintainers agree.
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to