Get rid of pyarrow-hotfix for CVE-2023-47248#36697
Merged
potiuk merged 1 commit intoapache:mainfrom Jan 9, 2024
Merged
Conversation
The apache#35650 introduced a hotfix for Pyarrow CVE-2023-47248. So far we have been blocked from removing it by Apache Beam that limited Airflow from bumping pyarrow to a version that was not vulnerable. This is now possible since Apache Beam relesed 2.53.0 version on 4th of January 2023 that allows to use non-vulnerable pyarrow. We are now bumping both Pyarrow and Beam minimum versions to reflect that and remove pyarrow hotfix.
hussein-awala
approved these changes
Jan 9, 2024
aritra24
approved these changes
Jan 9, 2024
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 11, 2024
The #35650 introduced a hotfix for Pyarrow CVE-2023-47248. So far we have been blocked from removing it by Apache Beam that limited Airflow from bumping pyarrow to a version that was not vulnerable. This is now possible since Apache Beam relesed 2.53.0 version on 4th of January 2023 that allows to use non-vulnerable pyarrow. We are now bumping both Pyarrow and Beam minimum versions to reflect that and remove pyarrow hotfix. (cherry picked from commit d105c71)
potiuk
added a commit
that referenced
this pull request
Jan 13, 2024
The #35650 introduced a hotfix for Pyarrow CVE-2023-47248. So far we have been blocked from removing it by Apache Beam that limited Airflow from bumping pyarrow to a version that was not vulnerable. This is now possible since Apache Beam relesed 2.53.0 version on 4th of January 2023 that allows to use non-vulnerable pyarrow. We are now bumping both Pyarrow and Beam minimum versions to reflect that and remove pyarrow hotfix. (cherry picked from commit d105c71)
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 15, 2024
The #35650 introduced a hotfix for Pyarrow CVE-2023-47248. So far we have been blocked from removing it by Apache Beam that limited Airflow from bumping pyarrow to a version that was not vulnerable. This is now possible since Apache Beam relesed 2.53.0 version on 4th of January 2023 that allows to use non-vulnerable pyarrow. We are now bumping both Pyarrow and Beam minimum versions to reflect that and remove pyarrow hotfix. (cherry picked from commit d105c71)
68 tasks
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
4 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 #35650 introduced a hotfix for Pyarrow CVE-2023-47248. So far we have been blocked from removing it by Apache Beam that limited Airflow from bumping pyarrow to a version that was not vulnerable.
This is now possible since Apache Beam relesed 2.53.0 version on 4th of January 2023 that allows to use non-vulnerable pyarrow.
We are now bumping both Pyarrow and Beam minimum versions to reflect that and remove pyarrow hotfix.
^ 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.