Temporarily exclude openlineage from "PyPI" constraints generation#33101
Merged
potiuk merged 1 commit intoapache:mainfrom Aug 4, 2023
Merged
Conversation
The openlineage provider has apache-airflow >= 2.7.0 as dependency, and this is a problem for automated constraint generation. Since there is only one version of the provider released, it's the only one that can be installed from PyPI, but until apache-airflow 2.7.0 is released it cannot be installed because of the dependency missing. This makes calculating of the constraints by PyPI impossible and it loops in continuously trying to find a solution that cannot be found. In order to unblock constraint generation we need to exclude the provider temporarily and regenerate the constraints again when airflow 2.7.0 gets released (which will generally only bring the open-lineage provider as part of the constraints). (cherry picked from commit b08188e24bf7e52a0b700e083caa38347a4fa3fc)
ephraimbuddy
approved these changes
Aug 4, 2023
ephraimbuddy
added
the
changelog:skip
ephraimbuddy
pushed a commit
that referenced
this pull request
Aug 4, 2023
…33101) The openlineage provider has apache-airflow >= 2.7.0 as dependency, and this is a problem for automated constraint generation. Since there is only one version of the provider released, it's the only one that can be installed from PyPI, but until apache-airflow 2.7.0 is released it cannot be installed because of the dependency missing. This makes calculating of the constraints by PyPI impossible and it loops in continuously trying to find a solution that cannot be found. In order to unblock constraint generation we need to exclude the provider temporarily and regenerate the constraints again when airflow 2.7.0 gets released (which will generally only bring the open-lineage provider as part of the constraints). (cherry picked from commit b08188e24bf7e52a0b700e083caa38347a4fa3fc) (cherry picked from commit f14430d)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The openlineage provider has apache-airflow >= 2.7.0 as dependency, and this is a problem for automated constraint generation. Since there is only one version of the provider released, it's the only one that can be installed from PyPI, but until apache-airflow 2.7.0 is released it cannot be installed because of the dependency missing.
This makes calculating of the constraints by PyPI impossible and it loops in continuously trying to find a solution that cannot be found.
In order to unblock constraint generation we need to exclude the provider temporarily and regenerate the constraints again when airflow 2.7.0 gets released (which will generally only bring the open-lineage provider as part of the constraints).
(cherry picked from commit b08188e24bf7e52a0b700e083caa38347a4fa3fc)
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.