evaluate plugin operator

Invokes a service-side query extension (plugin).

The evaluate operator is a tabular operator that allows you to invoke query language extensions known as plugins. Unlike other language constructs, plugins can be enabled or disabled. Plugins aren't "bound" by the relational nature of the language. In other words, they may not have a predefined, statically determined, output schema.


  • Syntactically, evaluate behaves similarly to the invoke operator, which invokes tabular functions.
  • Plugins provided through the evaluate operator aren't bound by the regular rules of query execution or argument evaluation.
  • Specific plugins may have specific restrictions. For example, plugins whose output schema depends on the data. For example, bag_unpack plugin and pivot plugin can't be used when performing cross-cluster queries.


[T |] evaluate [ evaluateParameters ] PluginName ([ PluginArgs ])


Name Type Required Description
T string A tabular input to the plugin. Some plugins don't take any input and act as a tabular data source.
evaluateParameters string Zero or more space-separated evaluate parameters in the form of Name = Value that control the behavior of the evaluate operation and execution plan. Each plugin may decide differently how to handle each parameter. Refer to each plugin's documentation for specific behavior.
PluginName string The mandatory name of the plugin being invoked.
PluginArgs string Zero or more comma-separated arguments to the plugin.

Evaluate parameters

The following parameters are supported:

Name Values Description
hint.distribution single, per_node, per_shard Distribution hints
hint.pass_filters true, false Allow evaluate operator to passthrough any matching filters before the plugin. Filter is considered as 'matched' if it refers to a column existing before the evaluate operator. Default: false
hint.pass_filters_column column_name Allow plugin operator to passthrough filters referring to column_name before the plugin. Parameter can be used multiple times with different column names.


The following plugins are supported:

Distribution hints

Distribution hints specify how the plugin execution will be distributed across multiple cluster nodes. Each plugin may implement a different support for the distribution. The plugin's documentation specifies the distribution options supported by the plugin.

Possible values:

  • single: A single instance of the plugin will run over the entire query data.
  • per_node: If the query before the plugin call is distributed across nodes, then an instance of the plugin will run on each node over the data that it contains.
  • per_shard: If the data before the plugin call is distributed across shards, then an instance of the plugin will run over each shard of the data.