GitHubContribute in GitHub: Edit online

has operator

Filters a record set for data with a case-insensitive string. has searches for indexed terms, where a term is three or more characters. If your term is fewer than three characters, the query scans the values in the column, which is slower than looking up the term in the term index.

The following table provides a comparison of the has operators:

Operator Description Case-Sensitive Example (yields true)
has Right-hand-side (RHS) is a whole term in left-hand-side (LHS) No "Login Failed" has "failed"
!has RHS isn't a full term in LHS No "Login Failed" !has "fail"
has_cs RHS is a whole term in LHS Yes "Login Failed" has_cs "Failed"
!has_cs RHS isn't a full term in LHS Yes "Login Failed" !has_cs "fal"

The following abbreviations are used in the table above:
  • RHS = right hand side of the expression
  • LHS = left hand side of the expression

For further information about other operators and to determine which operator is most appropriate for your query, see datatype string operators.

Case-insensitive operators are currently supported only for ASCII-text. For non-ASCII comparison, use the tolower() function.

Performance tips

Performance depends on the type of search and the structure of the data.

For faster results, use the case-sensitive version of an operator, for example, has_cs, not has.


T | where Column has (Expression)


  • T - The tabular input whose records are to be filtered.
  • Column - The column to filter.
  • Expression - Scalar or literal expression.


Rows in T for which the predicate is true.


    | project original_time, data_source_name, name
    //--- Search for the last 5 mins of data and events containg login   
    | where original_time > now(-5m) and name has "login"
    | take 2


original_time data_source_name name
2023-04-08T21:31:24.620Z microsoftWindowsSource2 MSSQL Login failed for user
2023-04-08T21:31:24.620Z microsoftWindowsSource6 MSSQL Login succeeded for user