Roadmap-Hinweis: Vage Bullets ohne Akzeptanzkriterien in Checkbox-Tasks ueberfuehren. Format:
- [ ] <Task> (Target: <Q/Jahr>).
Production-ready multi-model query stack with parser, optimizer, execution, federation, caching, and compatibility layers in active use.
- [~] Query hardening wave for safety, resilience, and predictable performance (Target: Q3 2026)
- Complete remaining performance/regression benchmark gates for vectorized and federated paths (Target: Q3 2026)
- Continue reliability hardening for cancellation, limits, and distributed query failure behavior (Target: Q3 2026)
- [~] AQL LLM Integration Consolidation — Phase 1-4 (2026-06-18 → ongoing)
- Formalize dependency contract between src/query/ (Query Engine) and src/aql/ (LLM Integration)
- Define canonical parser validation pipeline and SLA for LLM-generated AQL
- Phase 1: Define integration boundary (12 hrs) ✅ 2026-06-18
- Created
src/query/AQL_LLM_INTEGRATION_CONTRACT.md(canonical specification) - Updated
src/query/ARCHITECTURE.mdwith LLM integration section - Updated
src/aql/ARCHITECTURE.mdwith dependency documentation
- Created
- Phase 2: Wire parser validation + metrics (20 hrs) ✅ 2026-06-18
- ✅ validateAQLWithParser() implemented in llm_aql_handler.cpp:1553
- ✅ translateNLToAQL() calls validation with retry-on-error logic
- ✅ Created integration test suite: test_aql_llm_integration.cpp (16 test cases)
- ✅ Added Prometheus metrics instrumentation for validation tracking
- ✅ Verified Prometheus counters/histograms bound to LLMMetricsCollector
- Updated src/aql/ROADMAP.md to cross-reference consolidation work
- Phase 3: Consolidate documentation (12 hrs) 📋 PENDING
- Identify and unify duplicate AQL roadmaps across modules
- Create cross-module reference guide
- [~] Phase 4: Validation SLA performance tests (20 hrs) 🔄 IN PROGRESS
- ✅ Created test_aql_validation_performance.cpp (8 performance test cases)
- ✅ Tests verify SLA: ≤500ms per parse, ≥100 q/s throughput, <50ms error enrichment
- ✅ Registered in tests/query/CMakeLists.txt with performance tier/labels
- Pending: Build verification (blocked by pre-existing LLM linker errors)
- Full detailed roadmap: AQL_CONSOLIDATION_AUDIT_2026_06_18.md
- [~] AQL Mutations Language Extension — Phase 1-5 Implementation (Target: v2.0.0, Q3/Q4 2026)
- Implement INSERT, UPDATE, REPLACE, REMOVE, UPSERT statements for data manipulation
- Integrate mutations with transaction blocks (BEGIN...COMMIT) for atomic batching
- Full detailed roadmap: AQL_MUTATIONS_ROADMAP.md
- Phase 1: Parser & Tokenizer Enhancement (Target: Q3 Week 1-2)
- Phase 2: Safety & Semantic Validation (Target: Q3 Week 2-3)
- Phase 3: Translation & Execution Plan (Target: Q3 Week 3-4)
- Phase 4: Transaction Support & Atomicity (Target: Q3 Week 5-6)
- Phase 5: Testing, Performance & Documentation (Target: Q3 Week 7-8)
- AQL Mutations — INSERT/UPDATE/REPLACE/REMOVE/UPSERT for data manipulation (Target: v2.0.0-beta Q3 2026)
- Harden optimizer decision quality under skewed statistics and changing workloads (Target: Q4 2026)
- Expand federated query failure handling with deterministic partial-result policies (Target: Q4 2026)
- Strengthen query resource-limit enforcement diagnostics and operator-facing observability (Target: Q4 2026)
- Advance approximate query processing from baseline implementations to production-suitable coverage (Target: Q1 2027)
- Extend ML-assisted optimization with strict fallback guarantees and reproducibility checks (Target: Q1 2027)
- Expand continuous-query backpressure and persistence hardening for long-lived subscriptions (Target: Q1 2027)
- Keep parser/translation safety checks complete for edge-case query inputs (Target: Q3 2026)
- Ensure collection/access validation paths are enforced consistently across all execute entry points (Target: Q3 2026)
- Improve plan-selection robustness under stale or partial statistics (Target: Q4 2026)
- Add deterministic regression packs for rewrite, cost, and adaptive plan switches (Target: Q4 2026)
- Expand cross-cluster/federated timeout and retry envelopes with bounded memory behavior (Target: Q4 2026)
- Validate shard routing and partial-failure semantics under fault-injection (Target: Q4 2026)
- Re-baseline vectorized execution performance and memory envelopes on representative datasets (Target: Q1 2027)
- Tighten JIT fallback and equivalence checks for hot-query compilation paths (Target: Q1 2027)
- Keep query docs source-aligned with explicit sourcecode verification evidence per update cycle (Target: ongoing)
- Keep completed roadmap items exclusively in changelog (Target: ongoing)
- Status: Tracking in progress
- Nachweise: query focused tests, federation tests, optimizer tests, performance suites
- Hinweis: Abgeschlossene Arbeit wird ausschliesslich in CHANGELOG dokumentiert.
- Some long-horizon performance guarantees for federation/vectorized paths still require broader benchmark evidence.
- Advanced approximate/ML optimizer paths need additional production hardening and fallback verification.
- Continuous-query scale and backpressure behavior needs further validation under sustained load.
- Query public APIs and language compatibility paths remain additive-first in active major lines.
- Any future behavioral change requiring client migration must be versioned and documented in changelog/migration notes.