Query context

• For Druid SQL, context parameters are provided either as a JSON object named to the HTTP POST API, or as properties to the JDBC connection.
• For , context parameters are provided as a JSON object named context.

These parameters apply to all query types.

See the list of GroupBy query context parameters available on the groupBy query page.

• All query-level filters must either be able to run on bitmap indexes or must offer vectorized row-matchers. These include “selector”, “bound”, “in”, “like”, “regex”, “search”, “and”, “or”, and “not”.
• All filters in filtered aggregators must offer vectorized row-matchers.
• All aggregators must offer vectorized implementations. These include “count”, “doubleSum”, “floatSum”, “longSum”, “hyperUnique”, and “filtered”.
• For GroupBy: All dimension specs must be “default” (no extraction functions or filtered dimension specs).
• For GroupBy: No multi-value dimensions.
• For Timeseries: No “descending” order.
• Only immutable segments (not real-time).
• Only (not joins, subqueries, lookups, or inline datasources).

Other query types (like TopN, Scan, Select, and Search) ignore the “vectorize” parameter, and will execute without vectorization. These query types will ignore the “vectorize” parameter even if it is set to "force".