hubgeter opened a new pull request, #69132:
URL: https://github.com/apache/doris/pull/69132
### What problem does this PR solve?
Problem Summary:
MaxCompute regression cases take too long because many of them repeat the
same queries, and the MC write cases occasionally fail with `Unknown database`
when `USE` runs right after `CREATE DATABASE` (the remote catalog may not list
the just-created database yet).
This PR trims the repeated cases and stabilizes the write cases, in three
commits:
1. `test_max_compute_partition_prune`: 12 parameter combinations -> 1
(default profile, batch mode off, `split_cross_partition` default), 25 -> 18
queries.
2. `test_max_compute_all_type` / `test_max_compute_timestamp` /
`test_max_compute_schema`: 161 -> 65, 109 -> 39 and 68 -> 49 queries. Removed
queries are a subset of the previous ones; the type decoding and the
predicate/operator coverage are kept, and the `.out` files are reduced to the
matching blocks.
3. MC write cases: retry `USE` after `CREATE DATABASE` instead of failing on
the transient `Unknown database`.
### Release note
None
### Check List (For Author)
- Test
- [x] Regression test
- [ ] Unit Test
- [x] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason
Manual test: ran the trimmed `test_max_compute_schema` and
`test_max_compute_all_type` suites against a real MaxCompute project on a local
single-BE cluster, both pass (1 suite, 0 failed); every kept query of
`test_max_compute_timestamp` returns byte-identical results to the untrimmed
suite.
- Behavior changed:
- [x] No.
- [ ] Yes.
- Does this need documentation?
- [x] No.
- [ ] Yes.
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
--
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]
