AI_FILTER¶

Region availability¶

The following table shows the regions where you can use the AI_FILTER function for both text and images:

Syntax¶

Applying AI_FILTER to an input string:

AI_FILTER( <input> )

Applying AI_FILTER to single image:

AI_FILTER( <predicate> , <input> )

Applying AI_FILTER to multiple columns with both text and images, leveraging the PROMPT:

AI_FILTER( PROMPT('<template_string>',  <col_1>, … ) )

Arguments¶

Required:

If you’re specifying an input string:

input

A string containing the text to be classified.

If you’re filtering on one file:

predicate

A string containing the instructions to classify the file input as either TRUE or FALSE.

file

The column that the file is classified by based on the instructions specified in predicate. You can use IMAGE FILE as an input to the AI_FILTER function.

If you’re using the PROMPT() function to format the inputs:

For more complicated prompts, especially with multiple file columns, you can use the PROMPT to help with creating an input.

The PROMPT() function supports formatting across both strings and FILE datatypes. For detailed usage, see Examples.

Returns¶

Returns a Boolean value that indicates whether the statement evaluates to TRUE or FALSE for the specified text.

Access control requirements¶

Users must use a role that has been granted the SNOWFLAKE.CORTEX_USER database role. See Required privileges for more information on this privilege.

Performance and cost optimization¶

By default, AI_FILTER includes a built-in performance optimization on qualifying queries. This optimization can provide 2 to 10 times faster performance and up to 60% lower token usage with a minimal impact on quality.

This optimization is triggered automatically when the query engine detects a suitable pattern. Similar to other query optimizations, Snowflake doesn’t guarantee that this optimization will be applied for every query. The engine leverages adaptive routing and context-aware rewriting to execute more efficient AI operations where possible.

To disable this optimization for your account, contact your account manager.

Usage notes¶

For optimal performance, follow these guidelines:

• Make sure the columns sent into AI_FILTER don’t contain NULL values.

• Use plain text in English for the input string or for PROMPT() arguments.

• Provide details for the input text instruction. For example, instead of a statement like “sounds satisfied”, use “In the following support transcript, the customer sounds satisfied”.

• Consider phrasing the input in the form of a question. For example, “In the following support transcript, does the customer sound satisfied?”

Examples¶

SELECT AI_FILTER('Is Canada in North America?');

TRUE

WITH reviews AS (
            SELECT 'Wow... Loved this place.' AS review
  UNION ALL SELECT 'The pizza is not good.'
)
SELECT * FROM reviews
WHERE AI_FILTER(CONCAT('The reviewer enjoyed the restaurant: ', review));

WITH reviews AS (

SELECT 'Wow... Loved this place.' AS review
UNION ALL SELECT 'The pizza is not good.'
)
SELECT * FROM reviews
WHERE AI_FILTER(PROMPT('The reviewer enjoyed the restaurant: {0}', review));

+--------------------------+
| REVIEW                   |
|--------------------------+
| Wow... Loved this place. |
+--------------------------+

WITH country AS (
          SELECT 'Switzerland' AS country,
UNION ALL SELECT 'Korea'
),
region AS (
            SELECT 'Asia' AS region,
  UNION ALL SELECT 'Europe'
)
SELECT country,
      region,
      AI_FILTER(PROMPT('{0} is in {1}', country, region)) AS result
FROM country CROSS JOIN region ;

+-------------+-------+--------+
| COUNTRY     |REGION | RESULT |
|-------------+-------+--------+
| Switzerland |Europe | TRUE   |
|-------------+-------+--------+
| Switzerland | Asia  | FALSE  |
|-------------+-------+--------+
| Korea       |Europe | FALSE  |
+-------------+-------+--------+
| Korea       | Asia  | TRUE   |
+-------------+-------+--------+

SELECT *
FROM RESUMES
JOIN JOBS
ON AI_FILTER(PROMPT('Evaluate if this resume {0} fits this job description {1}', RESUME.contents, JOBS.jd));

WITH pictures AS (
  SELECT
      TO_FILE(file_url) AS img
  FROM DIRECTORY(@file_stage)
)
SELECT
FL_GET_RELATIVE_PATH(img) AS file_path FROM pictures
WHERE AI_FILTER('Is this a picture of a cat?', img);

WITH pictures AS (
  SELECT
      TO_FILE(file_url) AS img
  FROM DIRECTORY(@file_stage)
)
SELECT
    FL_GET_RELATIVE_PATH(img) AS file_path FROM pictures
WHERE AI_FILTER(PROMPT('{0} is a cat picture', img));

+--------------------------+
|        FILE_PATH         |
|--------------------------+
|        2cats.jpg         |
+--------------------------+
|        cat1.png          |
+--------------------------+
|      orange_cat.jpg      |
+--------------------------+

Limitations¶

• Snowflake AI functions don’t support dynamic table incremental refresh.

• Snowflake AI functions don’t work on FILEs created from stage files from the following stage types:

  • Internal stages with encryption mode TYPE = 'SNOWFLAKE_FULL'

  • External stages with any customer-side encrypted mode:

    • TYPE = 'AWS_CSE'

    • TYPE = 'AZURE_CSE'

  • User stage, table stage

  • Stage with double-quoted names