Skip to content

Airflow 2.7 is incompatible with SodaCore versions 3.0.24 and beyond #33577

Description

@nathadfield

Apache Airflow version

2.7.0

What happened

When trying to install SodaCore on Airflow 2.7, the following error is received due to a conflict with opentelemetry-api.

ERROR: Cannot install apache-airflow==2.7.0 and soda-core==3.0.48 because these package versions have conflicting dependencies.

The conflict is caused by:
    apache-airflow 2.7.0 depends on opentelemetry-api==1.15.0
    soda-core 3.0.48 depends on opentelemetry-api~=1.16.0

SodaCore has depended on opentelemetry-api~=1.16.0 ever since v3.0.24.

What you think should happen instead

Airflow needs to support versions of opentelemetry-api 1.16.x.

How to reproduce

Simply running the following commands to install the two packages should reproduce the error.

$ python3 -m venv /tmp/soda                                                                                         
$ /tmp/soda/bin/pip install apache-airflow==2.7.0 soda-core-bigquery==3.0.48

Operating System

n/a

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. potiuk commented on Aug 21, 2023

    @potiuk
    Member

    Yeah. We need to relax our requirements there. Agree they are too strict now. Let me take a look.

  2. added this to the Airflow 2.7.1 milestone on Aug 21, 2023
  3. self-assigned this
    on Aug 21, 2023
  4. removed
    needs-triagelabel for new issues that we didn't triage yet
    on Aug 21, 2023
  5. added a commit that references this issue on Aug 21, 2023
    ae25a52
  6. potiuk commented on Aug 21, 2023

    @potiuk
    Member

    Fixed. We will have otel 1.15+ supported for 2.7.1. That was a bit tricky and required celery bump :)

  7. potiuk commented on Aug 21, 2023

    @potiuk
    Member

    Thanks for raising it @nathadfield -> I completely forgot about this one when @ferruzzi added opentelmetry I left it as unsolved issue. Now we got it solved.

  8. nathadfield commented on Aug 21, 2023

    @nathadfield
    ContributorAuthor

    @potiuk Awesome! I'll look forward to 2.7.1 then. :)

  9. potiuk commented on Aug 21, 2023

    @potiuk
    Member

    It's gonna be sooner rather than later :)

  10. ferruzzi commented on Aug 21, 2023

    @ferruzzi
    Contributor

    Thanks for sorting this out! When I added OTel, I wasn't able to get pip to resolve any version other than that one very specific version so I had to pin it. I just saw Jarek's other thread where he explained the fix. That's great.

  11. added a commit that references this issue on Aug 25, 2023
    3fad890
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions