+1 On Thu, 26 Feb 2026 at 22:09, Pavankumar Gopidesu <[email protected]> wrote:
> Hello everyone, > > I would like to call for a lazy consensus to suspend the Apache Beam > provider. This suspension is necessary due to a grpcio limitation that is > currently blocking the development of new providers and other dependencies. > > I prepared a PR to do so: https://github.com/apache/airflow/pull/61926. > and you can read more about consequences of suspension in > > https://github.com/apache/airflow/blob/main/PROVIDERS.rst#suspending-releases-for-providers > > Discussion Thread: > https://lists.apache.org/thread/s0y610cdn2t1hq2mg6y3xws02bskp89w ( > https://lists.apache.org/thread/s0y610cdn2t1hq2mg6y3xws02bskp89w) > > Lazy Consensus Period: > The lazy consensus is open until Monday, March 2nd, at 11 PM GMT. > > In accordance with lazy consensus rules, a formal vote is not required; the > absence of binding dissent will be considered approval. > > Justification: > > ---------------------------------------------------------------------------------------------------------------- > 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. > > Regards, > Pavan >
