feat: add millisecond precision support for planner and query engine#437
Conversation
milindsrivastava1997
commented
Jun 24, 2026
- feat(planner): added millisecond precision support
- feat: added millisecond-level precision support in planner and query engine
…review - StoreQueryParams/QueryTimestamps: doc start/end fields as ms since epoch - frequency.rs step_ms: inline comment that LogEntry.step is seconds (Prometheus log format), explaining the *1000 - sql.rs SQLPatternMatcher boundary and config.py dual-key transform: confirmed intentional, already documented; no change needed - SQLPatternMatcher ms migration partially tracked by #427; prometheus_client ms migration tracked by #442 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
PR #343 removed do_profiling from EngineConfig (deny_unknown_fields) but missed updating benchmarks/config/engine_config.yaml and examples/engine_config.yaml. The field causes the query engine to fail at startup, which broke the full-stack CI. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Asymmetric Python public API (judgement call)
|
|
Constant names no longer match their values (judgement call) In |
|
Legacy
|
…e to the freshly built SHA tag but doesn't override the command, so the new binary (which uses _ms arg names) received the old arg names from asap-quickstart/docker-compose.yml