Suspend Apache Beam Provider due to grpcio limitation by gopidesupavan · Pull Request #61926 · apache/airflow

gopidesupavan · 2026-02-14T22:22:12Z

Suspending apache-airflow-providers-apache-beam package.

The current Apache Beam Python SDK pins grpcio restricts it to a range like <1.66.

This old grpcio version conflicts with several other dependencies in the project workspace, especially when using uv sync.

Newer versions of opentelemetry-exporter-otlp / opentelemetry-proto that need updated protobuf / grpcio
pydantic-ai-slim (used in common-ai provider) requiring opentelemetry-api ≥ 1.28.0

This blocks development work (including AIP-99) and prevents bumping other dependencies across the repo. the PR is here #61794 where its failing currently due to the limitation of several dependencies pinned.

The grpcio upper bound issue in Apache Beam has been known for a while, and its raised already @potiuk apache/beam#34081 long ago.

The root cause is being addressed upstream in the gRPC project grpc/grpc#37710
(they have already fixed it, with a possible release in grpcio 1.78.1 or a patch that should lift most of these pins/conflicts)

Following the official guidelines for provider suspension:
https://github.com/apache/airflow/blob/main/PROVIDERS.rst#suspending-releases-for-providers

The Apache beam provider can be removed from suspension by a PR reverting this change once grpcio limitation removed from the apache-beam.

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

Yes (please specify the tool below)

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 or {issue_number}.significant.rst, in airflow-core/newsfragments.

gopidesupavan · 2026-02-14T22:23:05Z

 × No solution found when resolving dependencies for split (markers: python_full_version == '3.12.*'):
  ╰─▶ Because only the following versions of opentelemetry-exporter-otlp are available:
          opentelemetry-exporter-otlp<=1.27.0
          opentelemetry-exporter-otlp==1.28.0
          opentelemetry-exporter-otlp==1.28.1
          opentelemetry-exporter-otlp==1.28.2
          opentelemetry-exporter-otlp==1.29.0
          opentelemetry-exporter-otlp==1.30.0
          opentelemetry-exporter-otlp==1.31.0
          opentelemetry-exporter-otlp==1.31.1
          opentelemetry-exporter-otlp==1.32.0
          opentelemetry-exporter-otlp==1.32.1
          opentelemetry-exporter-otlp==1.33.0
          opentelemetry-exporter-otlp==1.33.1
          opentelemetry-exporter-otlp==1.34.0
          opentelemetry-exporter-otlp==1.34.1
          opentelemetry-exporter-otlp==1.35.0
          opentelemetry-exporter-otlp==1.36.0
          opentelemetry-exporter-otlp==1.37.0
          opentelemetry-exporter-otlp==1.38.0
          opentelemetry-exporter-otlp==1.39.0
          opentelemetry-exporter-otlp==1.39.1
      and opentelemetry-exporter-otlp==1.39.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.39.1, we can conclude that opentelemetry-exporter-otlp>1.39.0 depends on
      opentelemetry-exporter-otlp-proto-grpc==1.39.1.
      And because opentelemetry-exporter-otlp==1.39.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.39.0 and opentelemetry-exporter-otlp-proto-grpc==1.38.0, we can conclude
      that opentelemetry-exporter-otlp>1.37.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.38.0.
      And because opentelemetry-exporter-otlp==1.37.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.37.0 and opentelemetry-exporter-otlp-proto-grpc==1.36.0, we can conclude
      that opentelemetry-exporter-otlp>1.35.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.36.0.
      And because opentelemetry-exporter-otlp==1.35.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.35.0 and opentelemetry-exporter-otlp-proto-grpc==1.34.1, we can conclude
      that opentelemetry-exporter-otlp>1.34.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.34.1.
      And because opentelemetry-exporter-otlp==1.34.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.34.0 and opentelemetry-exporter-otlp-proto-grpc==1.33.1, we can conclude
      that opentelemetry-exporter-otlp>1.33.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.33.1.
      And because opentelemetry-exporter-otlp==1.33.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.33.0 and opentelemetry-exporter-otlp-proto-grpc==1.32.1, we can conclude
      that opentelemetry-exporter-otlp>1.32.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.32.1.
      And because opentelemetry-exporter-otlp==1.32.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.32.0 and opentelemetry-exporter-otlp-proto-grpc==1.31.1, we can conclude
      that opentelemetry-exporter-otlp>1.31.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.31.1.
      And because opentelemetry-exporter-otlp==1.31.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.31.0 and opentelemetry-exporter-otlp-proto-grpc==1.30.0, we can conclude
      that opentelemetry-exporter-otlp>1.29.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.30.0.
      And because opentelemetry-exporter-otlp==1.29.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.29.0 and opentelemetry-exporter-otlp-proto-grpc==1.28.2, we can conclude
      that opentelemetry-exporter-otlp>1.28.1 depends on opentelemetry-exporter-otlp-proto-grpc>=1.28.2.
      And because opentelemetry-exporter-otlp==1.28.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.28.1 and opentelemetry-exporter-otlp-proto-grpc==1.28.0, we can conclude
      that opentelemetry-exporter-otlp>1.27.0 depends on opentelemetry-exporter-otlp-proto-grpc>=1.28.0.
      And because opentelemetry-exporter-otlp-proto-grpc==1.39.1 depends on opentelemetry-proto==1.39.1 and opentelemetry-proto==1.39.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.38.0
      , opentelemetry-proto<1.39.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.38.0 depends on opentelemetry-proto==1.38.0 and opentelemetry-proto==1.37.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.36.0
      , opentelemetry-proto<1.37.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.36.0 depends on opentelemetry-proto==1.36.0 and opentelemetry-proto==1.35.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.34.1
      , opentelemetry-proto<1.35.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.34.1 depends on opentelemetry-proto==1.34.1 and opentelemetry-proto==1.34.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.33.1
      , opentelemetry-proto<1.34.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.33.1 depends on opentelemetry-proto==1.33.1 and opentelemetry-proto==1.33.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.32.1
      , opentelemetry-proto<1.33.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.32.1 depends on opentelemetry-proto==1.32.1 and opentelemetry-proto==1.32.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.31.1
      , opentelemetry-proto<1.32.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.31.1 depends on opentelemetry-proto==1.31.1 and opentelemetry-proto==1.31.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.30.0
      , opentelemetry-proto<1.31.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.30.0 depends on opentelemetry-proto==1.30.0 and opentelemetry-proto==1.29.0, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, all of:
          opentelemetry-exporter-otlp-proto-grpc<1.28.0
          opentelemetry-exporter-otlp-proto-grpc>1.28.2
      , opentelemetry-proto<1.29.0 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.28.2 depends on opentelemetry-proto==1.28.2 and opentelemetry-proto==1.28.1, we can conclude that
      opentelemetry-exporter-otlp>1.27.0, opentelemetry-exporter-otlp-proto-grpc!=1.28.0, opentelemetry-proto<1.28.1 are incompatible.
      And because opentelemetry-exporter-otlp-proto-grpc==1.28.0 depends on opentelemetry-proto==1.28.0 and apache-airflow-core depends on opentelemetry-exporter-otlp>=1.27.0,
      we can conclude that opentelemetry-exporter-otlp!=1.27.0, all versions of opentelemetry-exporter-otlp-proto-grpc, opentelemetry-proto<1.28.0, apache-airflow-core[all] are
      incompatible. (1)

      Because opentelemetry-proto>=1.35.0 depends on protobuf>=5.0 and protobuf>=5.0,<6.0, we can conclude that opentelemetry-proto>=1.28.0 depends on protobuf>=5.0.
      And because yandexcloud==0.328.0 depends on protobuf>=4.25.3,<5, we can conclude that opentelemetry-proto>=1.28.0 and yandexcloud==0.328.0 are incompatible.
      And because we know from (1) that opentelemetry-exporter-otlp!=1.27.0, all versions of opentelemetry-exporter-otlp-proto-grpc, opentelemetry-proto<1.28.0,
      apache-airflow-core[all] are incompatible, we can conclude that opentelemetry-exporter-otlp!=1.27.0, all versions of opentelemetry-exporter-otlp-proto-grpc,
      yandexcloud==0.328.0, apache-airflow-core[all] are incompatible.
      And because only the following versions of yandexcloud{python_full_version < '3.13'} are available:
          yandexcloud{python_full_version < '3.13'}<=0.328.0
          yandexcloud{python_full_version < '3.13'}==0.329.0
          yandexcloud{python_full_version < '3.13'}==0.330.0
          yandexcloud{python_full_version < '3.13'}==0.331.0
          yandexcloud{python_full_version < '3.13'}==0.332.0
          yandexcloud{python_full_version < '3.13'}==0.333.0
          yandexcloud{python_full_version < '3.13'}==0.334.0
          yandexcloud{python_full_version < '3.13'}==0.335.0
          yandexcloud{python_full_version < '3.13'}==0.336.0
          yandexcloud{python_full_version < '3.13'}==0.337.0
          yandexcloud{python_full_version < '3.13'}==0.338.0
          yandexcloud{python_full_version < '3.13'}==0.339.0
          yandexcloud{python_full_version < '3.13'}==0.340.0
          yandexcloud{python_full_version < '3.13'}==0.341.0
          yandexcloud{python_full_version < '3.13'}==0.342.0
          yandexcloud{python_full_version < '3.13'}==0.343.0
          yandexcloud{python_full_version < '3.13'}==0.344.0
          yandexcloud{python_full_version < '3.13'}==0.345.0
          yandexcloud{python_full_version < '3.13'}==0.346.0
          yandexcloud{python_full_version < '3.13'}==0.347.0
          yandexcloud{python_full_version < '3.13'}==0.348.0
          yandexcloud{python_full_version < '3.13'}==0.349.0
          yandexcloud{python_full_version < '3.13'}==0.350.0
          yandexcloud{python_full_version < '3.13'}==0.351.0
          yandexcloud{python_full_version < '3.13'}==0.352.0
          yandexcloud{python_full_version < '3.13'}==0.353.0
          yandexcloud{python_full_version < '3.13'}==0.354.0
          yandexcloud{python_full_version < '3.13'}==0.355.0
          yandexcloud{python_full_version < '3.13'}==0.356.0
          yandexcloud{python_full_version < '3.13'}==0.357.0
          yandexcloud{python_full_version < '3.13'}==0.358.0
          yandexcloud{python_full_version < '3.13'}==0.359.0
          yandexcloud{python_full_version < '3.13'}==0.360.0
          yandexcloud{python_full_version < '3.13'}==0.361.0
          yandexcloud{python_full_version < '3.13'}==0.362.0
          yandexcloud{python_full_version < '3.13'}==0.363.0
          yandexcloud{python_full_version < '3.13'}==0.364.0
          yandexcloud{python_full_version < '3.13'}==0.365.0
          yandexcloud{python_full_version < '3.13'}==0.366.0
          yandexcloud{python_full_version < '3.13'}==0.367.0
          yandexcloud{python_full_version < '3.13'}==0.368.0
          yandexcloud{python_full_version < '3.13'}==0.369.0
          yandexcloud{python_full_version < '3.13'}==0.370.0
          yandexcloud{python_full_version < '3.13'}==0.371.0
          yandexcloud{python_full_version < '3.13'}==0.372.0
          yandexcloud{python_full_version < '3.13'}==0.373.0
          yandexcloud{python_full_version < '3.13'}==0.374.0
          yandexcloud{python_full_version < '3.13'}==0.375.0
          yandexcloud{python_full_version < '3.13'}==0.376.0
          yandexcloud{python_full_version < '3.13'}==0.377.0
      and yandexcloud>=0.334.0 depends on grpcio>=1.68.1, we can conclude that grpcio<1.68.1, opentelemetry-exporter-otlp!=1.27.0, all versions of
      opentelemetry-exporter-otlp-proto-grpc, apache-airflow-core[all], all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible. (2)

      Because only the following versions of apache-beam{python_full_version < '3.13'} are available:
          apache-beam{python_full_version < '3.13'}<=2.60.0
          apache-beam{python_full_version < '3.13'}==2.61.0
          apache-beam{python_full_version < '3.13'}==2.62.0
          apache-beam{python_full_version < '3.13'}==2.63.0
          apache-beam{python_full_version < '3.13'}==2.64.0
          apache-beam{python_full_version < '3.13'}==2.65.0
          apache-beam{python_full_version < '3.13'}==2.66.0
          apache-beam{python_full_version < '3.13'}==2.67.0
          apache-beam{python_full_version < '3.13'}==2.68.0
          apache-beam{python_full_version < '3.13'}==2.69.0
          apache-beam{python_full_version < '3.13'}==2.70.0
          apache-beam{python_full_version < '3.13'}==2.71.0
      and apache-beam{python_full_version < '3.13'}==2.71.0 depends on one of:
          grpcio{python_full_version < '3.13'}>=1.33.1,<1.48.0
          grpcio{python_full_version < '3.13'}>1.48.0,<1.59.dev0
          grpcio{python_full_version < '3.13'}>=1.62.dev0,<1.62.0
          grpcio{python_full_version < '3.13'}>1.62.1,<1.66.0
      we can conclude that all of:
          apache-beam<2.60.0
          apache-beam>2.70.0
      , apache-beam{python_full_version < '3.13'}>=2.60.0, all of:
          grpcio{python_full_version < '3.13'}<1.33.1
          grpcio{python_full_version < '3.13'}==1.48.0
          grpcio{python_full_version < '3.13'}>=1.59.dev0,<1.62.dev0
          grpcio{python_full_version < '3.13'}>=1.62.0,<=1.62.1
          grpcio{python_full_version < '3.13'}>=1.66.0
       are incompatible.
      And because apache-beam>=2.66.0 depends on one of:
          grpcio{python_full_version < '3.13'}>=1.33.1,<1.48.0
          grpcio{python_full_version < '3.13'}>1.48.0,<1.59.dev0
          grpcio{python_full_version < '3.13'}>=1.62.dev0,<1.62.0
          grpcio{python_full_version < '3.13'}>1.62.1,<1.66.0
      and one of:
          grpcio>=1.33.1,<1.48.0
          grpcio>1.48.0,<1.59.dev0
          grpcio>=1.62.dev0,<1.62.0
          grpcio>1.62.1,<1.66.0
      we can conclude that apache-beam{python_full_version < '3.13'}>=2.60.0 depends on one of:
          grpcio>=1.33.1,<1.48.0
          grpcio>1.48.0,<1.59.dev0
          grpcio>=1.62.dev0,<1.62.0
          grpcio>1.62.1,<1.66.0

      And because we know from (2) that grpcio<1.68.1, opentelemetry-exporter-otlp!=1.27.0, all versions of opentelemetry-exporter-otlp-proto-grpc, apache-airflow-core[all], all
      of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible, we can conclude that opentelemetry-exporter-otlp!=1.27.0, all versions of opentelemetry-exporter-otlp-proto-grpc, apache-airflow-core[all],
      apache-beam{python_full_version < '3.13'}>=2.60.0, all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible.
      And because apache-airflow-providers-apache-beam depends on apache-beam{python_full_version < '3.13'}>=2.60.0, we can conclude that apache-airflow-providers-apache-beam,
      opentelemetry-exporter-otlp!=1.27.0, all versions of opentelemetry-exporter-otlp-proto-grpc, apache-airflow-core[all], all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible.
      And because opentelemetry-exporter-otlp==1.27.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.27.0 and opentelemetry-exporter-otlp-proto-grpc==1.27.0 depends on
      opentelemetry-sdk>=1.27.0,<1.28.dev0, we can conclude that all of:
          opentelemetry-sdk<1.27.0
          opentelemetry-sdk>=1.28.dev0
      , apache-airflow-core[all], apache-airflow-providers-apache-beam[google], all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible. (3)

      Because opentelemetry-sdk==1.27.0 depends on opentelemetry-api==1.27.0 and only the following versions of opentelemetry-sdk are available:
          opentelemetry-sdk<=1.27.0
          opentelemetry-sdk>1.28.dev0
      we can conclude that opentelemetry-sdk>=1.27.0,<1.28.dev0 depends on opentelemetry-api==1.27.0.
      And because we know from (3) that all of:
          opentelemetry-sdk<1.27.0
          opentelemetry-sdk>=1.28.dev0
      , apache-airflow-core[all], apache-airflow-providers-apache-beam[google], all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible, we can conclude that opentelemetry-api!=1.27.0, apache-airflow-core[all], apache-airflow-providers-apache-beam[google], all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible. (4)

      Because only the following versions of pydantic-ai-slim[anthropic] are available:
          pydantic-ai-slim[anthropic]<=1.58.0
          pydantic-ai-slim[anthropic]==1.59.0
      and pydantic-ai-slim>=1.58.0 depends on opentelemetry-api>=1.28.0, we can conclude that pydantic-ai-slim[anthropic]>=1.58.0,<1.59.0 depends on opentelemetry-api>=1.28.0.
      And because pydantic-ai-slim==1.59.0 depends on opentelemetry-api>=1.28.0, we can conclude that pydantic-ai-slim[anthropic]>=1.58.0 depends on opentelemetry-api>=1.28.0.
      And because we know from (4) that opentelemetry-api!=1.27.0, apache-airflow-core[all], apache-airflow-providers-apache-beam[google], all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible, we can conclude that apache-airflow-core[all], apache-airflow-providers-apache-beam[google], pydantic-ai-slim[anthropic]>=1.58.0, all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible.
      And because apache-airflow-providers-common-ai depends on pydantic-ai-slim[anthropic]>=1.58.0, we can conclude that apache-airflow-providers-common-ai,
      apache-airflow-core[all], apache-airflow-providers-apache-beam[google], all of:
          yandexcloud{python_full_version < '3.13'}>=0.328.0,<0.329.0
          yandexcloud{python_full_version < '3.13'}>0.333.0
       are incompatible.
      And because yandexcloud{python_full_version < '3.13'}>=0.329.0,<=0.333.0 was yanked (reason: https://github.com/yandex-cloud/python-sdk/issues/138) and
      apache-airflow-providers-yandex depends on yandexcloud{python_full_version < '3.13'}>=0.328.0, we can conclude that apache-airflow-providers-yandex,
      apache-airflow-core[all], apache-airflow-providers-apache-beam[google], apache-airflow-providers-common-ai[common-compat] are incompatible.
      And because your workspace requires apache-airflow-core[all] and apache-airflow-providers-apache-beam[google], we can conclude that your workspace's requirements,
      apache-airflow-providers-yandex, apache-airflow-providers-common-ai[common-compat] are incompatible.
      And because your workspace requires apache-airflow-providers-common-ai[common-compat] and apache-airflow-providers-yandex, we can conclude that your workspace's requirements
      are unsatisfiable.

jscheffl

Hope to resolve this soonish, such that beam can be re-enabled.

eladkal

LGTM but placing temporary block to avoid accidental merge.
it requires also to follow discussion and vote/lazy consensus on mailing list

gopidesupavan · 2026-02-15T09:40:42Z

LGTM but placing temporary block to avoid accidental merge. it requires also to follow discussion and vote/lazy consensus on mailing list

Yes @eladkal , i am planning to follow that , am trying to resolve some build issues. me and @potiuk had quite a long discussion here https://apache-airflow.slack.com/archives/C015SLQF059/p1770972824043689

eladkal · 2026-02-15T09:43:50Z

LGTM but placing temporary block to avoid accidental merge. it requires also to follow discussion and vote/lazy consensus on mailing list

Yes @eladkal , i am planning to follow that , am trying to resolve some build issues. me and @potiuk had quite a long discussion here https://apache-airflow.slack.com/archives/C015SLQF059/p1770972824043689

We can't rely on Slack discussions.
I suggest to start the mailing list discussion as soon as possible. We need to allow time for community to comment

gopidesupavan · 2026-02-15T09:48:36Z

LGTM but placing temporary block to avoid accidental merge. it requires also to follow discussion and vote/lazy consensus on mailing list

Yes @eladkal , i am planning to follow that , am trying to resolve some build issues. me and @potiuk had quite a long discussion here https://apache-airflow.slack.com/archives/C015SLQF059/p1770972824043689

We can't rely on Slack discussions. I suggest to start the mailing list discussion as soon as possible. We need to allow time for community to comment

Yeah correct, sorry for the confusion, am saying will send a email discussion soon, am trying to see after removing beam provider what all impacting.

eladkal · 2026-02-15T09:56:54Z

Yeah correct, sorry for the confusion, am saying will send a email discussion soon, am trying to see after removing beam provider what all impacting.

Nothing is impacted :)
We are not removing we only suspend new releases. Everything released will continue to work as it does.

github-actions · 2026-02-27T13:27:21Z

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 917abea v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

…#61926)" This reverts commit 917abea. - Remove hacks regarding the beam provider suspension, as they are not relevant anymore.

…#61926)" This reverts commit 917abea. - Remove hacks regarding the beam provider suspension, as they are not relevant anymore. ISSUE: apache#66551

gopidesupavan requested review from amoghrajesh, ashb, bugraoz93, ephraimbuddy, jason810496, jedcunningham, jscheffl, kaxil, potiuk and shahar1 as code owners February 14, 2026 22:22

boring-cyborg Bot added area:dev-tools area:providers backport-to-v3-1-test provider:apache-beam provider:google Google (including GCP) related issues labels Feb 14, 2026

gopidesupavan marked this pull request as draft February 14, 2026 22:23

gopidesupavan force-pushed the suspend-apache-beam-provider branch from af4f6ef to 6e70de6 Compare February 14, 2026 22:51

gopidesupavan marked this pull request as ready for review February 14, 2026 22:52

gopidesupavan force-pushed the suspend-apache-beam-provider branch 2 times, most recently from d772897 to b348d38 Compare February 14, 2026 23:09

jscheffl approved these changes Feb 15, 2026

View reviewed changes

eladkal requested changes Feb 15, 2026

View reviewed changes

gopidesupavan force-pushed the suspend-apache-beam-provider branch from 3ea2b92 to 64bc285 Compare February 15, 2026 17:01

gopidesupavan added the all versions If set, the CI build will be forced to use all versions of Python/K8S/DBs label Feb 15, 2026

gopidesupavan force-pushed the suspend-apache-beam-provider branch from e959560 to 85ce6be Compare February 15, 2026 22:33

gopidesupavan added 6 commits February 26, 2026 21:47

Fixup example dags imports

9820da2

Fix serialization tests

05a956e

Fix static checks

5ed7375

Fix static checks

50106db

Fix fix provider yaml file check

87064b4

Fix mypy errors

15e5cf3

gopidesupavan force-pushed the suspend-apache-beam-provider branch from 594cc65 to 15e5cf3 Compare February 26, 2026 21:47

kaxil approved these changes Feb 26, 2026

View reviewed changes

eladkal approved these changes Feb 27, 2026

View reviewed changes

kaxil merged commit 917abea into apache:main Feb 27, 2026
228 of 229 checks passed

AkshayArali pushed a commit to AkshayArali/airflow_630 that referenced this pull request Feb 28, 2026

Suspend Apache Beam Provider due to grpcio limitation (apache#61926)

3ee07d5

This was referenced Mar 3, 2026

Exclude suspended providers from docs-list-as-string #62829

Merged

Exclude suspended providers from selected-providers-list-as-string #62832

Merged

dominikhei pushed a commit to dominikhei/airflow that referenced this pull request Mar 11, 2026

Suspend Apache Beam Provider due to grpcio limitation (apache#61926)

d7e7056

molcay mentioned this pull request Apr 15, 2026

[BLOCKED] Fix log processing for Beam in case of DataflowRunner VladaZakharova/airflow#302

Draft

1 task

nailo2c mentioned this pull request May 4, 2026

Fix Dataflow deferrable trigger handling of transient 503 #66293

Merged

1 task

olegkachur-e mentioned this pull request May 7, 2026

Un-suspend apache-airflow-providers-apache-beam #66551

Open

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Suspend Apache Beam Provider due to grpcio limitation#61926

Suspend Apache Beam Provider due to grpcio limitation#61926
kaxil merged 10 commits into
apache:mainfrom
gopidesupavan:suspend-apache-beam-provider

gopidesupavan commented Feb 14, 2026 •

edited

Loading

Uh oh!

gopidesupavan commented Feb 14, 2026

Uh oh!

jscheffl left a comment

Uh oh!

eladkal left a comment

Uh oh!

gopidesupavan commented Feb 15, 2026

Uh oh!

eladkal commented Feb 15, 2026

Uh oh!

gopidesupavan commented Feb 15, 2026

Uh oh!

eladkal commented Feb 15, 2026

Uh oh!

Uh oh!

github-actions Bot commented Feb 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Conversation

gopidesupavan commented Feb 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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

Uh oh!

gopidesupavan commented Feb 14, 2026

Uh oh!

jscheffl left a comment

Choose a reason for hiding this comment

Uh oh!

eladkal left a comment

Choose a reason for hiding this comment

Uh oh!

gopidesupavan commented Feb 15, 2026

Uh oh!

eladkal commented Feb 15, 2026

Uh oh!

gopidesupavan commented Feb 15, 2026

Uh oh!

eladkal commented Feb 15, 2026

Uh oh!

Uh oh!

github-actions Bot commented Feb 27, 2026

Backport failed to create: v3-1-test. View the failure log Run details

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

gopidesupavan commented Feb 14, 2026 •

edited

Loading