You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8d79801
Browse filesBrowse the repository at this point in the historyBrowse files
fix(planner): consistent latency_sla_ms defaults and stricter config parsing
- SQL experiment planner input no longer defaults `latency_sla_ms`;
omitted means no limit, as on the PromQL path and in the planner.
- asap-tools rejects non-numeric, boolean, non-finite or non-positive
`latency_sla_ms` when generating SQL planner input.
- Leave `query_groups` out of the planner input when the experiment has
none, so the planner reports it missing instead of planning nothing.
- SQL and Elastic DSL configs and query groups deny unknown fields, like
PromQL ones.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- **Description**: Maximum modeled query latency in milliseconds
518
-
- **Default**: `1000` for SQL experiments (`DEFAULT_LATENCY_SLA_MS` in `experiment_utils/config.py`); for PromQL experiments, omitted means no latency limit
518
+
- **Default**: omitted (no latency limit)
519
519
- **Range**: finite and > 0
520
520
- **Example**: `250`
521
521
- **Usage**: Intended as a hard ceiling on query latency for the planner. Not yet enforced: plans are not rejected for exceeding it.
0 commit comments