Contains Url Check Examples

The situation: The products table stores the canonical image location in image_url. Rows holding a file name, a note, or an internal path break every storefront and feed that reads the column.

Check configuration

Payload

{
    "description": "Product image column must hold a URL.",
    "rule": "containsUrl",
    "fields": ["image_url"],
    "container_id": 520,
    "coverage": 1,
    "filter": null,
    "properties": {},
    "tags": ["catalog", "format"],
    "additional_metadata": {"jira": "DATA-7401"},
    "anomaly_message_field": null,
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 22
}

Sample Data

What gets flagged

Product SKU-002 holds a bare file name instead of a location. SKU-004 is NULL and passes without firing an anomaly. Coverage is 100%, so the failing row is reported as a Record Anomaly.

Flowchart

graph TD
    A["No filter, evaluate all rows"] --> B["Read image_url as text"]
    B --> C{"Is value NULL?"}
    C -->|Yes| D["Row passes"]
    C -->|No| E{"Does it contain<br/>a URL?"}
    E -->|Yes| D
    E -->|No| F["Flag row.<br/>Record Anomaly per failing row."]

Equivalent SQL

-- Rows the Contains Url check would flag.
SELECT p.*
FROM products p
WHERE p.image_url IS NOT NULL
  AND p.image_url NOT RLIKE '<url pattern>';

The situation: The attachments table mixes external links with uploaded files. Only rows of type link must carry a URL in location; uploaded files hold storage keys and are out of scope.

Check configuration

Payload

{
    "description": "Link attachments must carry a URL.",
    "rule": "containsUrl",
    "fields": ["location"],
    "container_id": 521,
    "coverage": 1,
    "filter": "attachment_type = 'link'",
    "properties": {},
    "tags": ["content", "format"],
    "additional_metadata": {"jira": "DATA-7433"},
    "anomaly_message_field": null,
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 22
}

Sample Data (filtered to attachment_type = 'link')

Why the filter matters

The filter runs before the evaluation, so uploaded files are never tested for a URL. Only link attachments are evaluated.

What gets flagged

A-02 holds a note instead of a location, so it is the only row reported. Coverage is 100%, so the failure is reported as a Record Anomaly, and the message ends with the filter that scoped the evaluation.

Flowchart

graph TD
    A["Apply filter: attachment_type = 'link'"] --> B["Read location as text"]
    B --> C{"Does it contain<br/>a URL?"}
    C -->|Yes| D["Row passes"]
    C -->|No| E["Flag row.<br/>Anomaly message ends with<br/>[filter: attachment_type = 'link']"]

Equivalent SQL

-- Rows the check would flag among link attachments.
SELECT a.*
FROM attachments a
WHERE a.attachment_type = 'link'
  AND a.location IS NOT NULL
  AND a.location NOT RLIKE '<url pattern>';

The situation: A legacy reference column mixes links with free-text notes. A cleanup job is rewriting the bad rows, and a small fraction is expected to remain broken until it finishes, so the check tolerates up to 0.5% failures.

Check configuration

Payload

{
    "description": "Legacy reference column must hold a URL.",
    "rule": "containsUrl",
    "fields": ["reference"],
    "container_id": 522,
    "coverage": 0.995,
    "filter": null,
    "properties": {},
    "tags": ["legacy", "format"],
    "additional_metadata": {"jira": "DATA-7488"},
    "anomaly_message_field": null,
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 41
}

Sample Data

What gets flagged

Documents D-02 and D-03 still hold free-text notes. D-04 is NULL, so it passes without firing an anomaly but still counts in the scanned total. Only 50% of the rows pass, which is below the 99.5% coverage threshold, so the check reports a single Shape Anomaly for the dataset with a sample of the offending rows. Coverage below 100% does not produce Record Anomalies.

Flowchart

graph TD
    A["No filter, evaluate all rows"] --> B["Read reference as text"]
    B --> C{"Is value NULL?"}
    C -->|Yes| D["Row passes"]
    C -->|No| E{"Does it contain<br/>a URL?"}
    E -->|Yes| D
    E -->|No| F["Flag row.<br/>Passing rate falls below the 99.5%<br/>coverage, so one Shape Anomaly is reported."]

Equivalent SQL

-- Rows the check would flag.
SELECT d.*
FROM documents d
WHERE d.reference IS NOT NULL
  AND d.reference NOT RLIKE '<url pattern>';