morningman opened a new pull request, #64253:
URL: https://github.com/apache/doris/pull/64253
## Proposed changes
P4 of the catalog-SPI migration (base: `branch-catalog-spi`). Migrates the
**MaxCompute**
connector to the catalog SPI and **flips the gate to live** — MaxCompute
metadata / read /
write / DDL now route through the plugin-driven SPI path with no legacy
fallback.
> ⚠️ **User-visible cutover.** Unlike P0–P3 (dormant, behind the gate), this
phase makes the
> plugin-driven MaxCompute path the live path; the legacy
`datasource/maxcompute` route is retired.
### What's included
- **T01–T05** — MaxCompute SPI build-out: metadata/schema, partition
metadata + pruning,
read-session planning, write/transaction SPI wiring, and GSON compat for
the plugin-driven
catalog/db/table registrations.
- **T06a–T06e** — cutover hardening: read-path `TableDescriptor`
(`TMCTable`), partition
visibility + prune recovery, FE dispatch gaps (DROP/CREATE DB,
`partitions()` TVF),
datetime/timezone predicate pushdown, type mapping (VOID→NULL +
unknown-type fail-fast),
agg/unknown-column predicate guards, write block-id cap config.
- **Write path (W1–W7)** — fe-core Transaction generalization +
`ConnectorWritePlanProvider`
(opaque `TDataSink`); `PluginDrivenTransaction` delegates to SPI
`ConnectorTransaction`.
- `plan-doc/` — P4 designs, review rounds, task trackers (consistent with
P0–P3 PRs).
### Verification
Rebased clean onto latest `branch-catalog-spi` (`3dfd72a`); the only
conflicts were two
import/test merges in fe-core, resolved and verified: **fe-core compile +
checkstyle 0 violations**
(incl. test sources) and the affected unit tests green
(`PluginDrivenExternalTableEngineTest` 12/12,
plus partition / TVF tests). Per-task batches landed green during
development per the trackers;
CI re-verifies.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
