# How Is Type Checks Work

Source: https://userguide.qualytics.io/data-quality-checks/is-type/deep-dive/how-it-works/

## Definition

*Asserts that every value in a text field can be read as the configured data type.*

## Overview

The Is Type rule tests whether the text in a column really represents a typed value. You pick the expected **Field Type**, and each row passes when its value can be read as that type. The check exists because a column typed as text in the source can still be *meant* to hold numbers or dates: a CSV column, a staging table, or an API payload flattened into strings. Is Type is how you find the rows that would break the moment something tries to convert them.

Typical use cases:

- Validate a text column in a staging table before it is cast into a typed column downstream.
- Catch values that would fail a conversion, such as `N/A` in a column meant to hold numbers.
- Check that a date-like column from a flat file really parses as a date.

## Field Scope

**Single:** The rule evaluates exactly one field per check. The field itself must be a text field, or an array of text values.

**Accepted Types**

| Type | Supported |
| --- | --- |
| `String` | Yes |
| `Array` | Yes |

## General Properties

**Tab: Details**

| Name | Supported |
| --- | --- |
| Filter  Allows the targeting of specific data based on conditions | Supported |
| Coverage Customization  Allows adjusting the percentage of records that must meet the rule's conditions | Supported |

**Tab: Filter Guide**

The filter allows you to define a subset of data upon which the rule will operate.

It requires a valid **Spark SQL** expression that determines the criteria rows in the DataFrame should meet. This means the expression specifies which rows the DataFrame should include based on those criteria. Since it's applied directly to the Spark DataFrame, traditional SQL constructs like WHERE clauses **are not** supported.

> **Example: Examples**
>
> **Direct Conditions**
>
> Simply specify the condition you want to be met.
>
> > **Success: Correct usage" collapsible="true**
> >
> > ```sql
> > O_TOTALPRICE > 1000
> > ```
> >
> > ```sql
> > C_MKTSEGMENT = 'BUILDING'
> > ```
>
> > **Failure: Incorrect usage" collapsible="true**
> >
> > ```sql
> > WHERE O_TOTALPRICE > 1000
> > ```
> >
> > ```sql
> > WHERE C_MKTSEGMENT = 'BUILDING'
> > ```
>
> **Combining Conditions**
>
> Combine multiple conditions using logical operators like `AND` and `OR`.
>
> > **Success: Correct usage" collapsible="true**
> >
> > ```sql
> > O_ORDERPRIORITY = '1-URGENT' AND O_ORDERSTATUS = 'O'
> > ```
> >
> > ```sql
> > (L_SHIPDATE = '1998-09-02' OR L_RECEIPTDATE = '1998-09-01') AND L_RETURNFLAG = 'R'
> > ```
>
> > **Failure: Incorrect usage" collapsible="true**
> >
> > ```sql
> > WHERE O_ORDERPRIORITY = '1-URGENT' AND O_ORDERSTATUS = 'O'
> > ```
> >
> > ```sql
> > O_TOTALPRICE > 1000, O_ORDERSTATUS = 'O'
> > ```
>
> **Utilizing Functions**
>
> Leverage Spark SQL functions to refine and enhance your conditions.
>
> > **Success: Correct usage" collapsible="true**
> >
> > ```sql
> > RIGHT(
> >     O_ORDERPRIORITY,
> >     LENGTH(O_ORDERPRIORITY) - INSTR('-', O_ORDERPRIORITY)
> > ) = 'URGENT'
> > ```
> >
> > ```sql
> > LEVENSHTEIN(C_NAME, 'Supplier#000000001') < 7
> > ```
>
> > **Failure: Incorrect usage" collapsible="true**
> >
> > ```sql
> > RIGHT(
> >     O_ORDERPRIORITY,
> >     LENGTH(O_ORDERPRIORITY) - CHARINDEX('-', O_ORDERPRIORITY)
> > ) = 'URGENT'
> > ```
> >
> > ```sql
> > EDITDISTANCE(C_NAME, 'Supplier#000000001') < 7
> > ```
>
> **Using scan-time variables**
>
> To refer to the current dataframe being analyzed, use the reserved dynamic variable `{{_qualytics_self}}`.
>
> > **Success: Correct usage" collapsible="true**
> >
> > ```sql
> > O_ORDERSTATUS IN (
> >     SELECT DISTINCT O_ORDERSTATUS
> >     FROM {{_qualytics_self}}
> >     WHERE O_TOTALPRICE > 1000
> > )
> > ```
>
> > **Failure: Incorrect usage" collapsible="true**
> >
> > ```sql
> > O_ORDERSTATUS IN (
> >     SELECT DISTINCT O_ORDERSTATUS
> >     FROM ORDERS
> >     WHERE O_TOTALPRICE > 1000
> > )
> > ```
>
> While subqueries can be useful, their application within filters in our context has limitations. For example, directly referencing other containers or the broader target container in such subqueries **is not supported**. Attempting to do so will result in an error.
>
> > **Warning: Important Note on {{_qualytics_self}}**
> >
> > The `{{_qualytics_self}}` keyword refers to the dataframe that's currently under examination. In the context of a full scan, this variable represents the entire target container. However, during incremental scans, it only reflects a subset of the target container, capturing just the incremental data. It's crucial to recognize that in such scenarios, using `{{_qualytics_self}}` may not encompass all entries from the target container.

## Specific Properties

Is Type has one rule-specific property:

| Name | Description |
| --- | --- |
| Field Type | The type every value must be readable as: **Integral**, **Fractional**, **Boolean**, **Date**, or **Timestamp**. |

## Anomaly Types

| Type | Supported |
| --- | --- |
| Record Flag inconsistencies at the row level | Supported |
| Shape Flag inconsistencies in the overall patterns and distributions of a field | Supported |

## Evaluation Flow

Every Is Type check follows the same four-step evaluation flow:

1. **Apply the filter clause.** If the check has a `filter` set, only rows matching the filter expression continue to the next step. Rows outside the filter are ignored and cannot contribute to the violation count.
2. **Read the field value as text.** The platform reads the row's value for the selected field.
3. **Test it against the expected type.** The row passes when the text can be read as the configured **Field Type**, and fails when it cannot.
4. **Apply coverage.** At 100% coverage, any failing row causes the check to fail. Below 100% coverage, the check fails only when the passing fraction drops below the threshold (see [Coverage and Tolerance](https://userguide.qualytics.io/data-quality-checks/is-type/deep-dive/how-it-works/#coverage-and-tolerance)).

## The Five Testable Types

The **Field Type** property accepts the types that can be recognized in text:

| Type | What passes |
| --- | --- |
| **Integral** | Whole numbers, with an optional sign. |
| **Fractional** | Decimal numbers, with an optional sign and decimal separator. |
| **Boolean** | The textual forms of true and false. |
| **Date** | Calendar dates in a recognizable form. |
| **Timestamp** | Dates carrying a time component. |

Text itself is not in the list: every value is already text, so `String` would pass unconditionally. Structured types (arrays of structs, maps) are not testable this way either.

## The Column Stays Text

Is Type reports which values *could* be converted; it does not convert anything. The column keeps its text type, and downstream consumers still have to cast it. Use the check as the gate that makes a later cast safe, and pair it with a Computed Field when you want the typed value available in the platform.

## NULL Handling

The check **passes NULL values**: a row with `NULL` in the evaluated field is not counted as a violation. Is Type only asserts that *present* values are readable as the chosen type.

An empty string is a present value that cannot be read as any of the testable types, so it is reported. If the field must also be populated, pair the check with [Not Null](https://userguide.qualytics.io/data-quality-checks/not-null/introduction/).

## Array Fields

On an array of text values, every element is tested against the expected type and the row fails as soon as one element cannot be read as that type. Empty arrays and NULL arrays pass, since there is nothing to evaluate.

## The Filter Clause

The filter clause is a SQL `WHERE` expression applied **before** the evaluation. Filtered-out rows are ignored entirely (they cannot trigger a violation and are not counted in the totals).

When a filter is set, the message names it at the end of its first sentence, as `(applied to records where <expression>)`. Record and Shape Anomaly messages both carry it.

## Coverage and Tolerance

Coverage is a fractional value between `0` and `1` that defines the minimum fraction of evaluated rows that must pass:

- **`1.0` (100%, default):** every row in the filtered set must pass. Any failing row causes the check to fail. This is the strictest setting.
- **`< 1.0`:** the check tolerates a fraction of rows failing. The check fails only when the fraction of passing rows drops below the threshold.

Lower coverage values are useful when a small, known fraction of failures is expected. Use coverage carefully: a 0.5% tolerance can mask a real regression that happens to fall just under the threshold.

## See Also

- **Anomaly Reporting**

  The anomaly messages the check produces, what the numbers mean, Source Records highlighting, and Custom Anomaly Description.

  [Anomaly Reporting](https://userguide.qualytics.io/data-quality-checks/is-type/deep-dive/anomaly-reporting/)
- **Examples**

  Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.

  [Examples](https://userguide.qualytics.io/data-quality-checks/is-type/deep-dive/examples/)
- **Best Practices**

  Guidelines for choosing the type, staging text feeds, pairing rules, and keeping the signal clean.

  [Best Practices](https://userguide.qualytics.io/data-quality-checks/is-type/deep-dive/best-practices/)
- **Permissions**

  The team permission each action needs: view, create, edit, archive, restore, and delete.

  [Permissions](https://userguide.qualytics.io/data-quality-checks/is-type/deep-dive/permissions/)

*Last updated: September 22, 2026.*
