egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
71c8102de68cf1f947388b4913fa37f534f93c14
DashBoard/openspec/changes/historical-query-slow-connection/specs/hold-history-page/spec.md
egg 71c8102de6 feat: dataset cache for hold/resource history + slow connection migration 
Two changes combined:

1. historical-query-slow-connection: Migrate all historical query pages
   to read_sql_df_slow with semaphore concurrency control (max 3),
   raise DB slow timeout to 300s, gunicorn timeout to 360s, and
   unify frontend timeouts to 360s for all historical pages.

2. hold-resource-history-dataset-cache: Convert hold-history and
   resource-history from multi-query to single-query + dataset cache
   pattern (L1 ProcessLevelCache + L2 Redis parquet/base64, TTL=900s).
   Replace old GET endpoints with POST /query + GET /view two-phase
   API. Frontend auto-retries on 410 cache_expired.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-25 13:15:02 +08:00

361 B
Raw Blame History

MODIFIED Requirements

Requirement: Frontend API timeout

The hold-history page SHALL use a 360-second API timeout (up from 60 seconds) for all Oracle-backed API calls.

Scenario: Large date range query completes

  • WHEN a user queries hold history for a long date range
  • THEN the frontend does not abort the request for at least 360 seconds