String Filter Operators

Supported Operators

Jetstack's string-family filters support:

  • null
  • not_null
  • is
  • is_not
  • contains
  • not_contains
  • in_list
  • not_in_list

Operator Semantics

null and not_null

Use these when you only care whether a value exists.

is and is_not

Use these for direct string equality or inequality checks.

contains and not_contains

Use these when partial match semantics are intended. The platform automatically expands the search string into a wildcard pattern if needed.

in_list and not_in_list

Use these when the candidate set should come from a managed filter list instead of being repeated inside many query definitions.

Translation-Aware Matching

For title-like enumeration values, the platform may resolve translated values before comparing. This is important in multilingual implementations because a filter may operate on the translated display value rather than only on the stored base value.

When To Use This Family

This family is the right fit when the stored meaning is primarily textual and you need:

  • exact label matching
  • substring search
  • list-based allow or deny logic

Example

Use in_list for approved categories maintained by operators in a filter list instead of embedding the allowed values into several query definitions.

Best Practices

  • use contains only when partial match semantics are really intended
  • use filter lists for shared value sets
  • remember that title-like translated values may behave differently in multilingual setups
Previous← Special TypesNextSystem Types →