Query Priorities

Kloudfuse uses query priorities and per-call timeouts to govern how much of the underlying analytics engine (Apache Pinot) any given query is allowed to consume. Operators set cluster-wide defaults and override them for individual users, teams, and service accounts; Kloudfuse resolves the right value for each request through a precedence chain.

The High / Medium / Low scheduler priorities take effect only when Query Interleaving is enabled, which it is not by default starting in Kloudfuse 4.2.4. The Blocked priority is enforced before the query reaches Pinot, so it works regardless of which scheduler is active.