Gabriel39 opened a new pull request, #69417:
URL: https://github.com/apache/doris/pull/69417
### What problem does this PR solve?
Issue Number: N/A
Related PR: N/A
The Iceberg JDBC catalog suite exercises PostgreSQL basic reads/writes and a
small MySQL smoke test, leaving row-level DML and many metadata commits
untested on JDBC backends.
Run a shared set of scenarios on both PostgreSQL and MySQL:
- UPDATE, partial DELETE, all MERGE actions, partition-key updates, no-match
DML and historical tag reads across Parquet/ORC and Iceberg V2/V3.
- CTAS, table rename, column addition/rename/type promotion/drop, catalog
refresh, static/dynamic overwrite and partition evolution.
- Branch writes and fast-forward, tag/snapshot reads, rollback and explicit
snapshot expiration.
- Manifest and data-file rewrites, checking that work was committed and live
rows are preserved.
- Rejection of row-level DML on V1 and copy-on-write tables without changing
data.
- Metadata isolation when changing and restoring iceberg.jdbc.catalog_name.
Adds 98 ordered result checks, generated by the regression framework, while
preserving existing checks.
### Release note
None
### Check List (For Author)
- Test
- [x] Regression test
- [ ] Unit Test
- [ ] Manual test
- [ ] No need to test or manual test.
Generated the output with `-forceGenOut`, then ran the suite in comparison
mode using PostgreSQL 16, MySQL 8.0 and MinIO with prebuilt Doris development
binaries (reported version `doris-0.0.0-8264f390bd`).
```sh
./run-regression-test.sh --run -d external_table_p0/iceberg -s
test_iceberg_jdbc_catalog -parallel 1 -suiteParallel 1
```
Both backend paths ran; no suite was skipped. `git diff --check` also
passed. CI validation against the PR head remains pending.
- 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]
