HappenLee opened a new pull request, #70073:
URL: https://github.com/apache/doris/pull/70073
### What problem does this PR solve?
Related PR: #70027 (superseded approach)
Problem Summary: branch-4.1 uses TQueryOptions 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 FE sending a 32 MiB blob
limit silently replaces the intended 64 MiB analytic spill threshold.
Align master with the branch-4.1 field contract: retain optional i64
paimon_blob_max_size at 237 with its 10 MiB default, and move the analytic
spill option to the unused field 238 with its 64 MiB default. Existing
analytic option accessors and FE setters continue using the same name.
This change aligns the wire definition; it does not add Paimon BLOB
materialization support to master.
Field 238 was checked against the current branch-3.1, branch-4.0,
branch-4.1, branch-4.2 and master definitions and the available local
history. The existing 4.1 field contract is unchanged.
### Release note
Correct Paimon blob query-option decoding between branch-4.1 and master.
Master builds using the previous analytic spill field 237 are not wire
compatible with this correction: deploy matching FE/BE builds when
replacing those master builds. This is not a guarantee of general
cross-version query-plan compatibility.
### Check List (For Author)
- Test: Java/C++/Python Thrift code generation for baseline and modified
definitions; Binary/Compact protocol checks using real generated types:
reproduce the branch-4.1 collision, preserve a non-default 32 MiB blob
limit in both directions, preserve the 64 MiB spill default, round-trip
a separate 128 MiB spill limit at field 238, and verify the old-master
compatibility boundary; git diff --check; SelectDB revert tree equality.
Full FE/BE builds and SQL regression were not run for this IDL-only change.
- Behavior changed: Yes. Master field 237 now represents the Paimon blob
limit; the analytic spill limit uses 238. Both defaults 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]
