[fix](case) Relax show data compaction size check

[shuke987]

Summary

• Relax test_show_data_with_compaction so it no longer requires exact SHOW DATA equality after full compaction.
• Check the large documents table against observed mode-specific ranges: 170-200 KB for non-cloud and 55-70 KB for cloud/S3-style runs.
• Keep the small insert table assertion as a relative closeness check to catch gross size regressions.

Testing

• git diff --check -- regression-test/suites/inverted_index_p2/test_show_data.groovy
• Same logical fix passed the branch-4.1 single-suite remote run before the final range-only assertion adjustment: ./run-regression-test.sh --run -d inverted_index_p2 -s test_show_data_with_compaction -parallel 1

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[shuke987]

run buildall

[shuke987]

/review

[github-actions]

Automated review found one blocking test-coverage issue.

Critical checkpoint conclusions:

• Goal/test proof: the PR aims to relax a brittle SHOW DATA size equality, but the large-documents part now drops the comparison between the enabled and disabled inverted-index compaction paths, so the test no longer proves the intended equivalence.
• Scope/focus: the change is small and test-only.
• Concurrency/lifecycle: no new runtime concurrency, locking, lifecycle, persistence, or transaction behavior is introduced.
• Config/session: the test still toggles the existing BE config and restores it in finally; the issue is that the two config paths are no longer compared for the documents table.
• Parallel paths: the inverted_index_compaction_enable=true and false compaction implementations are parallel paths and should remain compared; see the inline comment.
• Test standards: no .out update is involved, no expected-error case is involved, and git diff --check -- regression-test/suites/inverted_index_p2/test_show_data.groovy passed locally. I did not run the regression suite because this checkout is missing .worktree_initialized, thirdparty/installed, and thirdparty/installed/bin/protoc.
• User focus: .code-review.LlcWw9/review_focus.txt said there was no additional user-provided focus.

Subagent conclusions: optimizer-rewrite found no optimizer/rewrite candidate because the patch only changes a regression assertion around DDL, stream load, SHOW DATA, sync, and compaction helpers. tests-session-config proposed TSC-1; I independently verified it and accepted it as MAIN-1. Convergence round 1 ended with both live subagents replying NO_NEW_VALUABLE_FINDINGS for the same final ledger/comment set.

[github-actions]

This still needs to compare the two config paths. The old assertion checked that the table compacted with inverted_index_compaction_enable=true reported the same SHOW DATA size as the table compacted with the config disabled. After this change, each value is only checked against an independent range, so a regression like 170 KB vs 200 KB in non-cloud mode, or 55 KB vs 70 KB in cloud mode, would pass even though the two implementations disagree materially. Please keep the absolute sanity range if it is needed for cloud/non-cloud variance, but also compare with_index_size and another_with_index_size with a relative tolerance, for example by reusing assert_show_data_size_close for the documents table.

[shuke987]

/review

[shuke987]

Address review feedback by keeping the relative size comparison between the documents table paths while preserving the cloud/non-cloud sanity ranges.\n\nrun buildall

[github-actions]

Automated review completed for PR #65391 at head e4755e5.

I did not find any new non-duplicate issue to raise. The existing inline thread about preserving the documents-table comparison between inverted_index_compaction_enable=true and false was checked against the current head; the PR now adds assert_show_data_size_close.call(with_index_size, another_with_index_size, "documents table") after the mode-specific range checks, so I did not duplicate that thread.

Critical checkpoint conclusions:

• Goal/test coverage: the change is limited to relaxing flaky SHOW DATA size assertions while still checking absolute mode-specific ranges and relative agreement between the two compaction paths.
• Scope: one regression test file changed; the patch is focused.
• Concurrency/lifecycle/transaction/persistence/FE-BE protocol: not applicable to this test-only assertion change.
• Configuration paths: existing BE config toggling is still restored in finally; both enabled and disabled compaction paths remain exercised.
• Parallel/special paths: cloud and non-cloud ranges are both covered, and the cross-config comparison remains present.
• Test result files: none added or modified.
• Performance/observability: no production-path impact.

User focus: no additional user-provided review focus was supplied.

Subagent conclusions: optimizer-rewrite and tests-session-config both completed the initial pass with no new valuable findings. After the main ledger recorded the existing-thread duplicate/resolved status and an empty proposed inline comment set, both subagents returned NO_NEW_VALUABLE_FINDINGS in convergence round C-001.

Validation: reviewed GitHub PR metadata/diff and fetched-base diff; ran git diff --check FETCH_HEAD..HEAD -- regression-test/suites/inverted_index_p2/test_show_data.groovy. I did not run the regression suite because this review checkout is missing .worktree_initialized and thirdparty/installed.