Uh oh!
There was an error while loading. Please reload this page.
[fix](cloud) preserve rowset inverted index format in recycler - #66793
Conversation
hello-stephen
commented
Aug 14, 2026
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
gavinchou
commented
Aug 14, 2026
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
hello-stephen
commented
Aug 14, 2026
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Aug 14, 2026
TPC-H: Total hot run time: 17830 ms |
hello-stephen
commented
Aug 14, 2026
TPC-DS: Total hot run time: 86088 ms |
hello-stephen
commented
Aug 14, 2026
ClickBench: Total hot run time: 14.85 s |
### What problem does this PR solve? Issue Number: None Related PR: apache#66475 Problem Summary: This change separately submits the Meta Service portion of apache#66475. During a partition-level inverted-index format rollout, a rowset can use a format that differs from its shared schema metadata. The recycler and checker previously selected index paths from shared schema metadata or its cache, which could target V1 paths for a rowset whose files use V3. Persist the actual inverted-index storage format in rowset and tablet metadata. Make the recycler and checker prefer the rowset format, while retaining schema and schema-KV fallback for metadata written before the field existed. Add a Cloud unit test where the shared schema is V1 and the rowset is V3, verifying that recycler deletes the V3 index file. ### Release note None ### Check List (For Author) - Test: Unit Test - `./run-cloud-ut.sh --run --filter=recycler_test:RecyclerTest.delete_tmp_rowset_data_with_rowset_idx_v3` - Behavior changed: Yes. Meta Service recycler and checker use each rowset\047s persisted inverted-index format when selecting index files. - Does this need documentation: No
hoshinojyunn
commented
Aug 15, 2026
run buildall |
hello-stephen
commented
Aug 15, 2026
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Aug 15, 2026
FE UT Coverage ReportIncrement line coverage `` 🎉 |
PR approved by at least one committer and no changes requested. |
hello-stephen
commented
Aug 15, 2026
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Aug 15, 2026
FE Regression Coverage ReportIncrement line coverage |
hello-stephen
commented
Aug 15, 2026
TPC-H: Total hot run time: 17787 ms |
hello-stephen
commented
Aug 15, 2026
TPC-DS: Total hot run time: 86850 ms |
hello-stephen
commented
Aug 15, 2026
ClickBench: Total hot run time: 14.78 s |
Uh oh!
There was an error while loading. Please reload this page.
What problem does this PR solve?
Issue Number: None
Related PR: #66475
Problem Summary:
This PR separately submits the Meta Service changes from #66475. When the shared schema format differs from the physical format used by an existing rowset, recycler and checker must use the rowset format to select the correct inverted-index files.
The change persists the physical inverted-index format in metadata and makes recycler/checker prefer the rowset value, with the existing schema and schema-KV fallback retained for old metadata.
Release note
None
Check List (For Author)
Test
./run-cloud-ut.sh --run --filter=recycler_test:RecyclerTest.delete_tmp_rowset_data_with_rowset_idx_v3Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)