Skip to content

[Subtask] TMS: Bind policy timeTrigger to the expand scheduler #13983

Open

Description

@lasdf1234

Describe the subtask

On top of #13773 (scheduler pools):

  • When a maintenance policy carries non-blank timeTrigger, create / alter / enable keep a matching policy-expand row in scheduled_expand_tasks (task instance id = policy id; due time = next Quartz cron fire)
  • Disable, blank timeTrigger, or successful delete remove the row
  • Ignore non-maintenance policies
  • Expand handler remains a no-op — this subtask only registers / moves / deletes the lease row
  • Ensure writes survive the entity-store pool (db-scheduler auto-commit / explicit commit when auto-commit is off)

Out of scope: expand handler implementation (select tables, enqueue cron/commit work), PolicyExpand Spark submit pipeline.

Design: apache/gravitino#13386. Parent: #13760.

PR: #13897

Parent issue

#13760

Activity

  1. self-assigned this
    on Oct 20, 2026
  2. added 2 commits that reference this issue on Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

2.0.0Release v2.0.0subtaskSubtasks of umbrella issue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions