mirror of
https://github.com/GreptimeTeam/greptimedb.git
synced 2026-11-18 00:34:11 +00:00
The unified query option mechanism is already in this branch's base, so what is left is the native route reading it: the switch resolves once in apply_query_options as request over session SET over the engine default, and both the planner and SHOW read that resolved value instead of combining the engine option with the request extension themselves. The engine-wide option therefore stops being a gate a request also has to pass and becomes the default a request or a session states over, which is what the other query options in this crate already do. What that costs is stated rather than implied: an operator can no longer switch the experimental route off for clients that set query options, and none of the entry points (HTTP hints, gRPC context, SET) carries an authorization check of its own. Data permissions are unaffected - the statement still plans through the same scanners and the same per-table checks. #10459 asserted the old gate; its test is rewritten here to pin the new contract in both directions instead of being dropped. Metric discovery stops keying off the request extension for the same reason: a session SET or the engine default can turn the route on without one. It reads the switch through the same resolver planning reads, so a query that leaves the route off is not bounded for discovery and pays no per-table grant for it. Signed-off-by: discord9 <discord9@163.com>