egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
519f8ae2f4db46ca4c643a4bba2e4abcbb263130
DashBoard/openspec/changes/archive/2026-02-12-unified-lineage-engine/specs/cache-indexed-query-acceleration/spec.md
egg 519f8ae2f4 feat(lineage): unified LineageEngine, EventFetcher, and progressive trace API 
Introduce a unified Seed→Lineage→Event pipeline replacing per-page Python
BFS with Oracle CONNECT BY NOCYCLE queries, add staged /api/trace/*
endpoints with rate limiting and L2 Redis caching, and wire progressive
frontend loading via useTraceProgress composable.

Key changes:
- Add LineageEngine (split ancestors / merge sources / full genealogy)
  with QueryBuilder bind-param safety and batched IN clauses
- Add EventFetcher with 6-domain support and L2 Redis cache
- Add trace_routes Blueprint (seed-resolve, lineage, events) with
  profile dispatch, rate limiting, and Redis TTL=300s caching
- Refactor query_tool_service to use LineageEngine and QueryBuilder,
  removing raw string interpolation (SQL injection fix)
- Add rate limits and resolve cache to query_tool_routes
- Integrate useTraceProgress into mid-section-defect with skeleton
  placeholders and fade-in transitions
- Add lineageCache and on-demand lot lineage to query-tool
- Add TraceProgressBar shared component
- Remove legacy query-tool.js static script (3k lines)
- Fix MatrixTable package column truncation (.slice(0,15) removed)
- Archive unified-lineage-engine change, add trace-progressive-ui specs

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 16:30:24 +08:00

1.0 KiB
Raw Blame History

ADDED Requirements

Requirement: Mid-section defect genealogy SHALL use CONNECT BY instead of Python BFS

The mid-section-defect genealogy resolution SHALL use LineageEngine.resolve_full_genealogy() (CONNECT BY NOCYCLE) instead of the existing _bfs_split_chain() Python BFS implementation.

Scenario: Genealogy cold query performance

  • WHEN mid-section-defect analysis executes genealogy resolution with cache miss
  • THEN LineageEngine.resolve_split_ancestors() SHALL be called (single CONNECT BY query)
  • THEN response time SHALL be ≤8s (P95) for ≥50 ancestor nodes
  • THEN Python BFS _bfs_split_chain() SHALL NOT be called

Scenario: Genealogy hot query performance

  • WHEN mid-section-defect analysis executes genealogy resolution with L2 Redis cache hit
  • THEN response time SHALL be ≤1s (P95)

Scenario: Golden test result equivalence

  • WHEN golden test runs with ≥5 known LOTs
  • THEN CONNECT BY output (child_to_parent, cid_to_name) SHALL be identical to BFS output for the same inputs