lasdf1234 opened a new pull request, #13817:
URL: https://github.com/apache/gravitino/pull/13817
### What changes were proposed in this pull request?
Depends on #13801 (merge first, then rebase). Stacked on that tip for review.
- `MinIntervalMsResolver`: policy content → server config → code default
- `NearestMaintenancePolicyResolver` over effective tag-selected policies
(prefer non-inherited; walk table → schema → catalog)
- `EffectiveTableMaintenancePolicy` as the runtime view (`schedule` +
resolved `minIntervalMs`)
- Per-task `Configs` entries for
`gravitino.maintenance.task.*.minIntervalMs` + docs
**Out of scope:** REST/DTO peers (#13815 / #13814), cluster-static
`gravitinoAuth` / `ircAuth` (#13797 / #13799), live scheduler / `runJob` wiring.
### Why are the changes needed?
Subtask of Epic #13764: schedulers need a single nearest-policy + cooldown
resolution path on top of `TableMaintenanceContent`.
Fix: #13779
### Does this PR introduce _any_ user-facing change?
Yes. Optional server config keys:
- `gravitino.maintenance.task.compaction.minIntervalMs`
- `gravitino.maintenance.task.manifest-rewrite.minIntervalMs`
- `gravitino.maintenance.task.snapshot-expiry.minIntervalMs`
- `gravitino.maintenance.task.orphan-cleanup.minIntervalMs`
No public REST change (policy peer fields land in #13814).
### How was this patch tested?
```bash
./gradlew :api:test --tests
'org.apache.gravitino.maintenance.policy.TestMinIntervalMsResolver' \
:core:test --tests
'org.apache.gravitino.maintenance.policy.TestNearestMaintenancePolicyResolver' \
--tests
'org.apache.gravitino.maintenance.policy.TestMaintenanceMinIntervalConfigs'
-PskipITs
```
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]
