ferruzzi opened a new pull request, #74301:
URL: https://github.com/apache/airflow/pull/74301
DuckDB installs extensions under the user's home directory and fails with
"IO Error: Can't find the home directory" when HOME is unset or empty, which is
the default state of an AWS Lambda function. Providing a writable home
directory is part of configuring the environment rather than something the
provider can guess, since any directory it picked would be discarded when the
task exits and so would re-download every extension.
Document the requirement in the DuckDB connection docs, in the Amazon DuckDB
operator docs where the two S3 extensions are installed by default, and in the
Lambda executor docs. Set HOME in the Lambda reference Dockerfile beside the
existing AIRFLOW_HOME, which is the same /tmp constraint.
Checked against duckdb 1.2.0, 1.3.0, 1.3.2, 1.4.0, 1.4.1, 1.5.0 and 1.5.5:
an install fails on every version without a usable HOME, extension_directory
stops covering for a missing HOME at 1.5.0, and loading a pre-populated
extension_directory with autoinstall_extensions disabled works everywhere.
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
https://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ x ] Yes (please specify the tool below)
Version confirmations done by Claude Opus 5
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
