HappenLee opened a new pull request, #70027:
URL: https://github.com/apache/doris/pull/70027

   ### What problem does this PR solve?
   
   Problem Summary: TQueryOptions used field 237 for paimon_blob_max_size,
   while master uses the same i64 field for spill_analytic_sink_mem_limit_bytes.
   A branch-4.1 sender with a 32 MiB blob limit can therefore replace the
   intended 64 MiB spill threshold without a decoding error.
   
   Move the optional blob size option to field 1024 and extend the reserved-id
   comment to cover 237. Keep the 10 MiB default and the option type unchanged.
   Generated-type checks confirm that the new payload preserves the 32 MiB
   blob limit and leaves master's 64 MiB spill threshold unchanged.
   
   This does not retrofit old binaries: update FE and BE together, since
   mixed field-237/field-1024 builds do not preserve custom blob limits.
   
   ### Release note
   
   Paimon blob size query options use Thrift field 1024. Deploy matching FE
   and BE builds when replacing builds that used field 237.
   
   ### Check List (For Author)
   
   - Test: Manual binary/compact protocol validation with real generated
     branch-4.1 and master types; baseline collision reproduction; fixed
     non-default 32 MiB round trip and unchanged 64 MiB master spill limit;
     Java/C++/Python Thrift code generation; live branch ID checks and local
     history search; git diff --check.
     Full FE/BE builds and SQL regression were not run for this IDL-only change.
   - Behavior changed: Yes. The wire field id changes from 237 to 1024;
     the option default and single-value limit semantics are unchanged.
   - Does this need documentation: No. The rollout boundary is documented above.
   


-- 
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