[amoghrajesh]

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Each provider repeats a variant of:

if AIRFLOW_V_3_0_PLUS:
    from airflow.triggers.base import BaseEventTrigger, TriggerEvent
else:
    from airflow.triggers.base import (  # type: ignore[assignment]
        BaseTrigger as BaseEventTrigger,
        TriggerEvent,
    )

Several of these also drag TriggerEvent into the version branch even though it exists in both 2.x and 3.x, and pull in an AIRFLOW_V_3_0_PLUS import that isn't used elsewhere.

I am proposing that we add a airflow.providers.common.compat.triggers, which resolves BaseEventTrigger through the existing create_module_getattr rename machinery and falls back to BaseTrigger on Airflow 2.x. Call sites collapse to a single import.

The iceberg trigger is migrated as the first consumer: #71387

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[1fanwang]

Thanks @amoghrajesh LGTM

[jason810496]

Thanks for adding the compat layer.

[jason810496]

Thanks.