Query Filters
Query filters are used in conditions to:
narrow down the scope of affected queries
narrow down the scope of queries which can be killed
Example usage:
Filter Arguments
include_user_name (str|Pattern) - include users with names matching patterns
exclude_user_name (str|Pattern) - exclude users with names matching patterns
include_user_login_name (str|Pattern) - include users with login names matching patterns
exclude_user_login_name (str|Pattern) - exclude users with login names matching patterns
include_user_email (str|Pattern) - include users with emails matching patterns
exclude_user_email (str|Pattern) - exclude users with emails matching patterns
include_warehouse_name (str|Pattern) - include queries running on warehouses with names matching patterns
exclude_warehouse_name (str|Pattern) - exclude queries running on warehouses with names matching patterns
include_sql_text (str|Pattern) - include queries with SQL text matching patterns
exclude_sql_text (str|Pattern) - exclude queries with SQL text matching patterns
include_query_tag (str|Pattern) - include queries with Query Tag matching patterns
exclude_query_tag (str|Pattern) - exclude queries with Query Tag matching patterns
Usage notes
Individual patterns in one argument are combined with
OR
-logic. If at least one pattern returns true, the whole argument check returns true.Multiple arguments are combined with
AND
-logic. All specified arguments should return true in order for query to match filter.String patterns are interpreted as basic Unix filename patterns , with
*
matching everything and?
matching single character.For more complex cases, it is allowed to use free-form
Pattern
objects produced byre.compile
function. Such patterns should match the full string.
Last updated