Repository navigation
[feat](job) show first error message for routine load - #65553
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
|
/review |
|
Codex automated review failed and did not complete. Error: You've hit your usage limit. Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at Jul 20th, 2026 12:23 AM. Please inspect the workflow logs and rerun the review after the underlying issue is resolved. |
46cf915 to
9f85868
Compare
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
0f76348 to
43cb1e2
Compare
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 29969 ms |
FE UT Coverage ReportIncrement line coverage |
TPC-DS: Total hot run time: 180463 ms |
ClickBench: Total hot run time: 25 s |
FE UT Coverage ReportIncrement line coverage |
TPC-H: Total hot run time: 29437 ms |
TPC-DS: Total hot run time: 178000 ms |
ClickBench: Total hot run time: 24.76 s |
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
FE Regression Coverage ReportIncrement line coverage |
|
PR approved by at least one committer and no changes requested. |
### What problem does this PR solve? Issue Number: None Related PR: apache#69658, apache#68500, apache#61325, apache#65553 Problem Summary: Release branches have been allocating thrift ids and enum values on their own, and those ids later collide with master. Comparing branch-4.0/4.1/4.2/master shows, for example: - TQueryOptions 237 is paimon_blob_max_size on branch-4.1 (apache#69658, merged directly to branch-4.1) and spill_analytic_sink_mem_limit_bytes on master (apache#68500); both are i64, so a mixed cluster silently reads one as the other. - TRLTaskTxnCommitAttachment 12 is firstErrorMsg on 4.0/4.1/4.2 but kinesisRLTaskProgress on master, because the backport of apache#65553 renumbered firstErrorMsg into the gap left by the unpicked apache#61325. - TSchemaTableType values 62-72 differ between 4.0, 4.1/4.2 and master. The existing rule only says an id must mean the same thing everywhere; it does not say where an id is allocated, so each branch picks the next free number. This adds the rule to gensrc/AGENTS.md (summarized in the root AGENTS.md and the code-review skill): a new id or enum value is added on master first, a release-only feature still reserves its id on master, picks keep master's numbers, enum values are written explicitly, and a release-branch PR that adds an id master does not have is not mergeable. ### Release note None ### Check List (For Author) - Test: No need to test (documentation-only change) - Behavior changed: No - Does this need documentation: No Co-Authored-By: Claude Opus 5.5 <[email protected]>
What problem does this PR solve?
PR #55666 added the first data quality error to load responses, but Routine Load was not covered. Routine Load transaction attachments only propagated the error log URL, so users still had to open the URL to inspect the actual error.
Design
This PR:
first_error_msgthrough the Routine Load Thrift transaction attachment and cloud transaction attachment.first_error_msg_max_lengthwhen constructing the FE transaction attachment.FirstErrorMsgcolumn toSHOW ROUTINE LOAD.FIRST_ERROR_MSGtoinformation_schema.routine_load_jobswithout changing existing column ordinals.ERROR_LOG_URLSunchanged instead of embedding the message in the URL field.Example
first_error_msgoutput:The first error can be queried directly:
or