lasdf1234 opened a new pull request, #14236: URL: https://github.com/apache/gravitino/pull/14236
### What changes were proposed in this pull request? Merge `branch-tms-scheduler` into `main` to land the in-process Table Maintenance Service foundation tracked by epic #13760: - Typed execution peers on Iceberg maintenance policies (`timeTrigger`, `commitTrigger`, `minIntervalMs`, `jobOptions`, `updaterOptions`) with SerDe / REST round-trip - `plugins/maintenance` (renamed from `plugins/tms`): DDL/DAOs, expand/cron/commit db-scheduler pools, OccupancyGate, soft-slot claims - In-job metrics/finish REST, nearest-policy expand → cron enqueue, cron/commit submit pipelines - Built-in Iceberg maintenance Spark job; IRC post-commit → commit-job enqueue - Cluster-static `gravitinoAuth` / `ircAuth` overlay bags Head is `branch-tms-scheduler` after merging current `main` into it (conflict resolution with rewrite-manifests thresholds and the `plugins/tms` → `plugins/maintenance` rename). ### Why are the changes needed? Fix: #13760 Delivers the persistence, scheduler, and in-job Spark path for TMS so maintenance policies can expand, enqueue, submit, and finish soft slots end-to-end. ### Does this PR introduce _any_ user-facing change? Yes: - Maintenance action REST (`metrics/before`, `metrics/after`, `finish`) - Policy content peer fields on Iceberg maintenance types - Built-in Iceberg maintenance job template / `jobConf` shape - Module path `plugins/tms` → `plugins/maintenance` - Related server config keys (`gravitino.maintenance.*`) ### How was this patch tested? Covered by the stacked PRs already merged to `branch-tms-scheduler` (unit tests + plugin BaseITs). After conflict resolution: - `./gradlew :api:compileJava :common:compileJava :plugins:maintenance:compileJava -PskipITs` - `./gradlew :api:test --tests 'org.apache.gravitino.policy.Test*' :common:test --tests 'org.apache.gravitino.dto.policy.Test*' :plugins:maintenance:test -PskipITs -PskipDockerTests=true` Made with [Cursor](https://cursor.com) -- 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]
