Skip to content

ADR-0005 — Snowflake* class names for upstream contribution

Status: accepted Date: 2026-05-31

Context

The package is named pinky-airflow but the goal is to eventually contribute SnowflakeTaskOperator and SnowflakeTaskSensor to the official apache-airflow-providers-snowflake package. The upstream provider already uses Snowflake* naming (SnowflakeOperator, SnowflakeHook, SnowflakeCheckOperator…).

Two naming options: - Pinky* — consistent with the suite, but requires a rename before upstreaming - Snowflake* — consistent with the upstream convention, ready to contribute as-is

Decision

All Airflow-side classes use Snowflake* naming: - SnowflakeTaskOperator - SnowflakeTaskSensor - SnowflakeTaskRunStatus

The Snowpark SP that calls the Airflow REST API uses SnowflakeDagTriggerSP (it lives in Snowflake, not in Airflow, so Snowflake* is still appropriate).

Consequences

Classes are ready to contribute to apache-airflow-providers-snowflake without renaming. In the meantime they are distributed as pinky-airflow — the package name and the class names are intentionally decoupled.