Problem
Dynamic Table refresh behavior is opaque via CLI. Users cannot easily check:
- Next scheduled refresh time
- Current refresh status (IDLE, RUNNING, FAILED)
- Last refresh duration and mode (FULL/INCREMENTAL)
- Why a table didn't refresh at expected time (e.g.,
scheduleStartTime confusion)
Currently, users must run complex SHOW DYNAMIC TABLE REFRESH HISTORY queries and parse output manually.
Proposed Solution
- Add
cz-cli dt status <table> command:
- Returns: interval, next_trigger_time, last_refresh_state, last_refresh_mode, error_message
- Add
cz-cli dt refresh <table> [--mode full|incremental] command:
- Wraps
REFRESH DYNAMIC TABLE SQL with validation and progress tracking.
- Clarify documentation:
REFRESH INTERVAL calculates from creation/last refresh time, not wall-clock alignment.
Expected Benefit
- Make Dynamic Table scheduling observable and intervenable.
- Reduce troubleshooting time for "why didn't it refresh?" scenarios.
- Provide intuitive CLI interface for common DT operations.
Priority
🔴 P0
Problem
Dynamic Table refresh behavior is opaque via CLI. Users cannot easily check:
scheduleStartTimeconfusion)Currently, users must run complex
SHOW DYNAMIC TABLE REFRESH HISTORYqueries and parse output manually.Proposed Solution
cz-cli dt status <table>command:cz-cli dt refresh <table> [--mode full|incremental]command:REFRESH DYNAMIC TABLESQL with validation and progress tracking.REFRESH INTERVALcalculates from creation/last refresh time, not wall-clock alignment.Expected Benefit
Priority
🔴 P0