o-nikolas opened a new pull request, #72845:
URL: https://github.com/apache/airflow/pull/72845
DuckDB is an in-process analytical (OLAP) database. Unlike most SQL
providers there is no server to connect to: queries run inside the task
process, which makes it a cheap way to run an analytical transform that don't
justify standing up a cluster. It reads and writes Parquet, CSV and JSON
directly from object storage, so it fits naturally between an extract and a
load step in a
Dag.
It also fits Airflow's existing shape well: The proposed DuckDB provider
speaks DbAPI, so it plugs into the common-sql ecosystem rather than needing new
machinery, and it fits in the data-processing/ETL space. DuckDB Labs was
acquired by Amazon but DuckDB remains MIT licensed and controlled by the DuckDB
Foundation. It is usable with no account, no signup and no hosted service.
The provider exposes a DuckDBHook extending DbApiHook, so it works with
SQLExecuteQueryOperator and the rest of the common-sql ecosystem, plus a
DuckDBExecuteQueryOperator and a duckdb connection type. The connection is
optional: with none configured the hook opens an in-memory database.
Provider specific integrations would live in their relevant provider package
(e.g. for AWS, an AwsDuckDBHook in apache-airflow-providers-amazon for
credential management).
<!-- 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".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* 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]
