Skip to content

Conversation

@ephraimbuddy
Copy link
Contributor

This is a temporary measure and we will remove it once Apache Beam allows us to upgrade to pyarrow 14.0.1

This is a temporary measure and we will remove it once
Apache Beam allows us to upgrade to pyarrow 14.0.1
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@ephraimbuddy ephraimbuddy requested a review from potiuk November 15, 2023 10:01
@potiuk potiuk merged commit 2afbb0a into apache:main Nov 15, 2023
@ephraimbuddy ephraimbuddy added the type:misc/internal Changelog: Misc changes that should appear in change log label Nov 20, 2023
@ephraimbuddy ephraimbuddy added this to the Airflow 2.8.0 milestone Nov 20, 2023
potiuk added a commit to potiuk/airflow that referenced this pull request Jan 9, 2024
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.
potiuk added a commit to potiuk/airflow that referenced this pull request Jan 9, 2024
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.
potiuk added a commit that referenced this pull request Jan 9, 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.
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools type:misc/internal Changelog: Misc changes that should appear in change log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants