pub fn native_promql_resolved(
query_ctx: &QueryContextRef,
engine_default: bool,
) -> Result<bool>Expand description
Whether one query asks for the native fused-series route, resolved the way planning resolves
it: a stated value wins (request over session SET``), otherwise the engine default answers.
This exists for the callers that have to act before a plan is built - the frontend bounds
metric discovery by the caller’s grants only when this route will read it - and it resolves
from the same two sources planning reads: [QueryContext::query_option_snapshot] for what the
query states, and the engine-wide option for what it inherits. Nothing here re-derives the
option from a third place, so the two readers cannot disagree.